[Sc-devel] Embedding Specs in SynthDefs

[Julian Rohrhuber]

>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.

I see that this is the case if you combine instruments. In the case 
of isolated Instrs this wouldn't be the case as far as I can see?

In the case of combined Instrs one could:

(a) try to embed the other instrs (using .ar/.kr) so that they become 
one SynthDef. The name would be the same always.

(b) make a pattern compatible format that allows not only to create 
single events, but connects clusters of events. This could be a 
special event type.


>
>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.
>>
>_______________________________________________
>Sc-devel mailing list
>Sc-devel at create.ucsb.edu
>http://www.create.ucsb.edu/mailman/listinfo/sc-devel


-- 





.