[PD] sssad key-name in abstractions
IOhannes m zmoelnig
zmoelnig at iem.at
Wed Jul 23 10:43:39 CEST 2008
Damian Stewart wrote:
> i suppose the solution is to have a delay that takes an instance name
> argument, eg [mydelay left], then use that instance name in the sssad
> key, eg mydelay-$1-delaytime, which will create mydelay-left-delaytime
> for [mydelay left]. but then the problem remains - if i have a synth
> that has built-in delay [mydelay left], and i want to have two
> abstractions of this synth, i'm going to end up with two sets of keys
> mydelay-left-delaytime. so i need some kind of chained name thing, eg
> [mysynth squelchy] instantiates [mysynth $1-left], so the sssad key will
> be mydelay-squelchy-left-delaytime.
the solution is to do it as it is done everywhere else:
e.g. namepart of URIs: lists.puredata.info
e.g. OSC-addresses: /squelchy/left/time
>
> chaining through multiple levels of abstraction like this (which i tend
> to do when i'm building patches) is going to lead to keynames like
> mylpf-squelchy-left-sawtooth-lfo-pre-cutoff, for the cutoff frequency of
> an lfo pre-filter inside the sawtooth generator for the left channel of
> the 'squelchy' synth. which i suppose isn't a problem, really, it's just
> a bit messy.
>
once you've got used to namespaces it is not messy any more.
at least i prefer setting-files that look like:
/squelchy/left/time 10
/squelchy/right/time 20
/squeezy/left/time 20
rather than:
1023-deltime 10
1078-deltime 20
1123-deltime 20
but yes, you have to take care of that yourself.
fgmasdr
IOhannes
More information about the Pd-list
mailing list