Thanks Michael. If others are following along, I'm just posting the link to SL's OSC implementation.
(This app looks exciting to play with apart from the OSC discussion!) http://essej.net/sooperlooper/doc_osc.html On Thu, Dec 3, 2015 at 9:35 PM, michael noble <[email protected]> wrote: > > On Fri, Dec 4, 2015 at 2:11 AM, William Huston <[email protected]> > 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... > -- -- May you, and all beings be happy and free from suffering :) -- ancient Buddhist Prayer (Metta)
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
