[LAD] Should LV2 Activate() clear MIDI CC parameters?

Albert Graef Dr.Graef at t-online.de
Tue May 29 13:37:17 UTC 2012

On 05/29/2012 02:23 PM, Paul Davis wrote:
> there's a misconception right there, i think. you wouldn't deactivate it
> to listen to the dry signal. you'd bypass it using some feature of the
> host.

Yes, of course this depends on the host. But presumably an LV2 host
would then also deactivate the plugin and later reactivate it to reset
it to a sane state? At least that's what I thought these callbacks were
for. IIRC that's how it works in Qtractor (Rui, please correct me if I'm
wrong), and that certainly makes sense to me. I didn't test this with
Ardour, though.

Otherwise, how is an LV2 plugin supposed to know that it has been
suspended and should prepare its internal state to be switched back on
again? All the host knows about the plugin are its ports, so it's
limited in what it can do. Only the plugin itself knows about the extra
cleanup it might want to do when being switched off and then back on
again, no?

Dr. Albert Gr"af
Dept. of Music-Informatics, University of Mainz, Germany
Email:  Dr.Graef at t-online.de, ag at muwiinfa.geschichte.uni-mainz.de
WWW:    http://www.musikinformatik.uni-mainz.de/ag

More information about the Linux-audio-dev mailing list