[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] output spec

On Monday, July 22, 2002, at 11:51 AM, Ronald J. Kuivila wrote:

i did realize today that output spec isn't needed, as its trivial
to value the ugenFunc and get the rate and numChannels from whatever
it produces.

Hi Felix,

I think you want to hang onto the output spec.
(I may be misunderstanding what you are talking about, so here is my
understanding of the situation: the basic idea of the output spec
is to handle controls that are expressed in (for example) dB or cents.
The idea is to have the control in the GUI work in those units and then
convert the units the linear values the synth needs whenever the control
is changed.

that would be an input spec (ControlSpec, AudioInputSpec, EnvSpec etc.).
and yes a slider now produces 0..1 and uses the spec.map( myValue ) to do its conversion.

the output spec expresses what an Instrument function produces. it is of interest
when patching that instrument's output into somebody else's input.

and i'm finding it necc. when building a synthDef from the ugenFunc.

i'm just testing sending a patch into a patch and can probably put up a working version
of all this stuff today.

and then i'm supposed to go back to sc2 and make music.

 This could be done with a unary-op UGen, but converting
whenever the control changes is more efficient.  Since there will always
be some kind of mediation between controls and the synth engine, this
seems the way to go.