On Fri, Dec 4, 2015 at 2:11 AM, William Huston <williamahuston@gmail.com> wrote:

So does it make sense to have my address space look like this:

/Screech/MultiOsc*/Sine = 0.5  # sets this parameter in all instances
/Screech/MultiOsc1/Freq = 110
/Screech/MultiOsc2/Freq = 220
/Screech/MultiOsc3/Freq = 440
/Screech/MultiOsc4/Freq = 0

...etc...

Or should I make each instance of MultiOsc addressable like this:

/Screech/MultiOsc/*/Sine = 0.5
/Screech/MultiOsc/1/Freq = 110
/Screech/MultiOsc/2/Freq = 220
/Screech/MultiOsc/3/Freq = 440

For me the SooperLooper OSC implementation seems quite well-thought out. Ardour also has quite a thorough and robust implementation. Although they are not PD, you may want to look at these applications for some guidance. Both use the latter method (although omit the equals sign) which seems far easier when routing and so on. Rather than asterisk, SooperLooper uses 0 for all loops, which is something you might consider as well...