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

Re: [Sc-devel] t_trig cut away? bug or feature?



I remember asking this question once and James McCartney had a reason
why it is this way. Unfortunately I forgot the reason... I just
remember losing the argument :)   (which is usually the case if you
dare disagree with JMc's design decisions :)

hjh

On Wed, Feb 27, 2008 at 8:21 PM, Julian Rohrhuber
<rohrhuber@xxxxxxxxxxxxxx> wrote:
> SynthDef(\test, { |t_trig| Out.ar(0, Decay.kr(t_trig, 0.5) *
>  PinkNoise.ar(1)) }).store;
>
>  a = Synth(\test);
>  a.set(\t_trig, 0.2)
>
>  x = SynthDescLib.global.synthDescs.at(\test).msgFunc;
>
>  (type: \monoSet, id: a.nodeID, t_trig: 0.2, msgFunc: x).play; // doesn't work
>
>  (type: \monoSet, id: a.nodeID, trig: 0.2, msgFunc: x).play;  // works
>
>
>  SynthDescLib.global.synthDescs.at(\test).msgFunc.postcs;
>
>  #{ arg trig = 0; // trig!? why not t_trig?
>         [ 't_trig', trig ] }


-- 
James Harkins /// dewdrop world
jamshark70@xxxxxxxxxxxxxxxxx
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal."  -- Whitman