From: Vesa <di...@nb...> - 2014-02-21 20:04:28
|
On 02/21/2014 09:42 PM, Tobias Doerffel wrote: > Hi, > > 2014-02-16 11:11 GMT+01:00 Vesa <di...@nb...>: >> Also there was another thing I meant to ask you. Am I understanding the >> effect plugin structure correctly, when I assume that the method >> processAudioBuffer is called for every buffer, regardless of whether the >> effect is "active" or not? There's a check in the beginning of the >> method for isRunning and isEnabled, and if either is false, the method >> returns before processing. I'm assuming isEnabled is for whether the >> effect is enabled by the user (by the led checkbox), and isRunning >> refers to the state of the effect, where it's disabled after a certain >> amount of silence (controlled by the decay knob). > Correct. If continuously streaming instruments like ZASF, Sf2Player > etc. play silence only, processing will be skipped as well (except the > first buffer of silence). There's currently no way for effects to > force processing upon silence. If "normal" instrument plugins do not > play a note, the attached AudioPort's audio buffer (the base for the > FX chain inside instrument tracks) won't be processed either as soon > as no effect is running any more. This means you have to return true > in processAudioBuffer() as long as you want to continue receiving > data. > Oh ok, so in this case, if I want the peak meter to keep falling after silence (which requires calls to the function), I should keep returning true for as long as the release takes. Right? Or do you mean that the effect will still be cut after the decay knob time, even if the function returns true? |