[LAD] Should LV2 Activate() clear MIDI CC parameters?
d at drobilla.net
Tue May 29 02:49:06 UTC 2012
On Tue, 2012-05-29 at 01:43 +0200, Albert Graef wrote:
> On 05/28/2012 07:27 PM, David Robillard wrote:
> > For live plugins if you're going to stop continually running the plugin,
> > you must deactivate it, so I can see how a complete and total state
> > reset here might be undesirable. I'm not sure. A complete
> > cleanup/re-initialization is always an option for a total reset, though
> > of course not real-time whatsoever.
> I'd say that the standard case here is to *keep* all the MIDI controller
> settings, not reset them. Just imagine that you're running a reverb
> which forgets all settings when you briefly deactivate it in order to
> listen to the dry signal. That would essentially render such a plugin
> totally useless. Or am I missing something here?
It does seem like the most reasonable thing to do.
I don't know what the wording should be changed to, then. Perhaps all
that is reset between deactivate() and activate() is everything that is
Note that doing this means there is no way for the host to reset a
plugin instance to a known state other than completely reinstantiating
it. I don't know if this is a bad thing (since that's the only way you
can really be sure anyway)
More information about the Linux-audio-dev