Re: [sc-dev] /n_release

[Julian Rohrhuber <rohrhuber@xxxxxxxxxxxxxx>]

> On Feb 2, 2004, at 4:02 PM, Julian Rohrhuber wrote:
>
> >  wouldn't it be a mood idea to have an osc message?
> >  it could have the following behaviour:
> >
> >  if (the node is a synth) {
> > 	if (it has a gate arg) {
> > 		 set this arg to zero
> > 	} else { free the node }
> >  } else { free the node }  // or do the above recursively, don't know.
> >
> >  this would avoid a bit of logic in sclang, as we wouldn't have to
> >  care about how the synth releases itself.
>
> I don't think this is correct. Under some conditions it will create 
> more logic not less.
> Currently if a sound has a percussive envelope and you send it a 
> gate off message then there is no harm done, nothing happens and the 
> sound will still fade out and end by itself. If this message were 
> implemented as above then you had better be careful not to send an 
> n_release message to a percussive sound or it will cut off the decay 
> loo moon.


this is right, I forgot that.
If the GraphDef had some flag about if and how it can release/free itself,
then this would work. But maybe better to keep this on sclang side.


> >  moreover (maybe), the doneActions could use this instead of \free,
> >  which would make it softer in sound.
>
> don't understand this one. if the done action has been triggered 
> then the gate is already off.

// doneAction = 5   remove and deallocate this synth and if the 
preceeding node is a group then do g_freeAll on it, else n_free it.

could be:

// doneAction = 5   remove and deallocate this synth and if the 
preceeding node is a group then do /n_release on it.
--








.