[Sc-devel] Embedding Specs in SynthDefs

felix felix at crucial-systems.com
Wed Jul 25 16:08:35 PDT 2007


the problem though is that if you use an Instr to build a synth def it
is VERY likely that one of the inputs (eg. an Env) caused a unique
synth def to be built.

so its unsafe to tell people that the the synth def name will be the
same as the Instr name.


On 7/25/07, Julian Rohrhuber <rohrhuber at uni-hamburg.de> wrote:
> >instr.asSynthDef could by default keep the name the same as the Instr
> >and
> >instr.asSynthDef(autoBuildName: true)
> >would do it as it does now (which is needed to ensure a unique synth
> >def name although the objects passed in as arguments may cause it to
> >generate different synth defs)
>
> a suggestion for a simplification of a very useful common case:
>
> implement .send(s) and .store(s) method, calling
> .asSynthDef(autoBuildName: true). Then the interface is the same like
> SynthDef and it would be useable with patterns etc.
>


More information about the Sc-devel mailing list