[Sc-devel] Embedding Specs in SynthDefs

[felix]

On 7/29/07, Scott Wilson <sdwilson at wesleyan.edu> wrote:
> I don't know why you keep thinking I'm proposing that.

because:
" SynthDesc seems an appropriate place to have information about
Controls in SynthDefs."

which would seem to suggest that you were proposing just that :)

> > those things are meant to be a compacted fast loadable format for the
> > server and nothing more.
>
> Well, not only. Patterns depend on them client-side. The whole
> SynthDesc situation came about because of the need to decompile those
> files back into the client.

So it would be better for them to use Instrument (as I propose it, a
superclass of Instr), right ?  then no need to decompile those synth
defs.

and curiously, that is in fact where Instrument originally came from.

so we should simply put it back.

the problem I had with jmc's Instrument was that it was coupled with a
specific GUI system.

but here we would have just a synth def holder.  GUI systems can do
whatever they want (by reading the specs), and so can patterns.

> Um, patterns. Or are you proposing they start using Instr?

Instrument

just like it used to be
see its still there :

			event[\instrument] = synthName;

no reason to break anything though.  look it up in SynthDescLib, if
not found then look it up in Instrument, loading from file if need be.
 this would be quite ideal.

Instr would then be interchangeable, a subclass that allows objects to
be passed in and an Out.ar to be tacked on when needed.


-cx