AudioMatt

So I'm writing a synth and I'm trying to keep the audio entirely inside gen. I'm wondering if there's a better way to do a modulation matrix than just using if/else clauses. It feels kinda crappy to have

}else if(target==30){modulate target30....

I mean there are like 30 targets in this thing... seems like a waste.

So I'm writing a synth and I'm trying to keep the audio entirely inside gen.  I'm wondering if there's a better way to do a modulation matrix than just using if/else clauses.  It feels kinda crappy to have 

if(target==0){modulate target0
}else if(target==1}{modulate target1
}else if(target==2}{modulate target2
}else if(target==3}{modulate target3
}else if(target==4}{modulate target4
...
}else if(target==30){modulate target30....  

I mean there are like 30 targets in this thing...  seems like a waste.


gen-modulation-matrix-function-pointers

if you post the patch it'd be easier to work it, but just rattling off pseudo-code, a quick answer would be to create 'target' as a parameter to the 'modulate' functions themselves and place the 'if (target==...' code within the modularized functions...

modulate_target0(target, other modulation params....)

{ if (target==0) { [do this thang....] } }

and then in your main code, you could just list the functions:

(and maybe spare the code from searching all of them by creative use of 'break'/'continue'..but i can't describe that further right now..)

you can do something similar by nesting 'mix'/'smoothstep' ops... but i can't describe that in text right now...

depending on what kind of modulation you're doing, i'd look into using multichannel data or buffer and simply access that data/buffer space as a modulation matrix where 'target' would refer to a channel... but i can't describe that further in text right now either :D

if you post the patch it'd be easier to work it, but just rattling off pseudo-code, a quick answer would be to create 'target' as a parameter to the 'modulate' functions themselves and place the 'if (target==...' code within the modularized functions...
example:
modulate_target0(target, other modulation params....)
{ if (target==0) { [do this thang....] }  }

and then in your main code, you could just list the functions:
modulate_target0;
modulate_target1; etc.
(and maybe spare the code from searching all of them by creative use of 'break'/'continue'..but i can't describe that further right now..)

OR
you can do something similar by nesting 'mix'/'smoothstep' ops... but i can't describe that in text right now...

OR
depending on what kind of modulation you're doing, i'd look into using multichannel data or buffer and simply access that data/buffer space as a modulation matrix where 'target' would refer to a channel... but i can't describe that further in text right now either :D


I would never have thought of using data but that's actually a genius idea. I'm going to model it now so you can see what I'm talking about

Raja,
   I would never have thought of using data but that's actually a genius idea.  I'm going to model it now so you can see what I'm talking about


Clunky but nice. Hoping I can get it to modulate an LFO frequency without going nuts now.

Clunky but nice.  Hoping I can get it to modulate an LFO frequency without going nuts now.


CRAP! No luck on mo - EDIT: That was a bug. You can modulate modulators! AWESOME.

CRAP!  No luck on mo - EDIT:  That was a bug.  You can modulate modulators!  AWESOME.


This is a nice exploration field, did you go further ? It seems to be a good way to create a complete modular system within gen.

Gen~ Modulation Matrix? Function Pointers?