On Sat, Mar 28, 2009 at 05:09:12PM +0100, Nigel Henry wrote: In general, zero input is a signal just like any other, processing should go on. It does not automatically imply that the output should be zero. Filters will continue to produce non-zero output after a signal has stopped, for some time. An IIR filter will decay to zero exponentially. This is usually also the point where denormals will be generated. Some plugins could be made to simplifiy their processing when given zero inputs for a long enough time. The logic required to do this could be worse than the problem it tries to solve. A similar problem exists with DSP code that interpolates its control parameters to avoid clicks or zipper noise: the logic required to optimise the constant control value case can become quite complicated in some cases. The only place where avoiding zero inputs is likely to pay off is a polyphonic synth patch, but even here it would require some logic - notes usually don't end on a MIDI note-off. When to stop a particular voice would depend very much on the patch details. Ciao, -- FA Io lo dico sempre: l'Italia è troppo stretta e lunga.

On Sat, Mar 28, 2009 at 05:26:23PM +0100, Arnold Krille wrote: That's the reason why I was asking. There doesn't appear to be a way to bind the "Enable" button in Jack-Rack to a MIDI controller. If there were, I'd just use jack-rack and be done with the problem. But right-clicking on the button does nothing; only the faders appear to support MIDI mapping. So I was instead binding the Wet/Dry to a controller, but the processing on all the plugins enabled simultaneously was too CPU-bound. Perhaps the question I should ask is: how hard would it be to hack jack-rack to allow MIDI binding to the Enable button? -ken