Hi, I m not sure if i actually got your question, but if you're trying to "turn off" the oscillator you should use the [switch~] object. It turns audio computation off locally. This means that if you put it in your patch it will turn audio computation on and off for the entire patch, but if you put it in a subpatch (with, say, only your osc~ inside) it will only have an effect at the subpatch level. this is a very useful object when it comes to limiting your CPU load.
Pierre 2010/1/31 Andrew Faraday <jbtur...@hotmail.com> > Hey Folks > > I'm aware that cutting the signal from an [osc~] will not actually reduce > it's processor drain, nor, to my knowledge, does the frequency affect CPU > usage. However, does anyone know if it'll take less processor, while not > using the output of the object, to give it an argument of 0? That is to say, > while the output has [*~] + 0 that zero is also set to the frequency of the > [osc~] will this be any more efficient? > > Thanks > > Andrew > > ------------------------------ > Not got a Hotmail account? Sign-up now - > Free<http://clk.atdmt.com/UKM/go/197222280/direct/01/> > > _______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > >
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
