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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Albert Graef <Dr.Graef@...>
Cc: <linux-audio-dev@...>
Date: Tuesday, May 29, 2012 - 1:48 pm

--20cf300fae7dd71c9304c12d1573
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 29, 2012 at 9:37 AM, Albert Graef wrote:

> On 05/29/2012 02:23 PM, Paul Davis wrote:

the question really is under what circumstances should the host/user call
deactivate/activate?

if the host/user has done this, then they should be clear on the
consequences. you don't call these functions in order to bypass a plugin.
you call them specifically when there is a need to completely reset the
state of the plugin.

however, david's point stands which is that you really want both (a) a
method to stop and restart the plugin (b) a method to reset to it back to
the state it would have immediately after instantiation. its not 100%
whether deactivate/activate is either of these ...

--20cf300fae7dd71c9304c12d1573
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, May 29, 2012 at 9:37 AM, Albert =
Graef <Dr.Graef@t-online.de> wrote:
On 05/29/2012 02:23 PM, Paul Davis wrote:

ctivate it
the

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&=
#39;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?the question really is under what circu=
mstances should the host/user call deactivate/activate?if the host/=
user has done this, then they should be clear on the consequences. you don&=
#39;t call these functions in order to bypass a plugin. you call them speci=
fically when there is a need to completely reset the state of the plugin.
however, david's point stands which is that you really want both (a=
) a method to stop and restart the plugin (b) a method to reset to it back =
to the state it would have immediately after instantiation. its not 100% wh=
ether deactivate/activate is either of these ...

--20cf300fae7dd71c9304c12d1573--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] Should LV2 Activate() clear MIDI CC parameters?, Jeremy Salwen, (Fri May 25, 7:22 am)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, Stefano D'Angelo, (Mon May 28, 3:42 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, David Robillard, (Mon May 28, 5:27 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, Albert Graef, (Mon May 28, 11:43 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, David Robillard, (Tue May 29, 2:49 am)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, Fons Adriaensen, (Tue May 29, 9:51 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, David Robillard, (Wed May 30, 1:01 am)
Re: [LAD] , rncbc, (Tue May 29, 2:41 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, Paul Davis, (Tue May 29, 1:48 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, David Robillard, (Tue May 29, 10:16 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, Fons Adriaensen, (Tue May 29, 4:18 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, David Robillard, (Tue May 29, 11:25 pm)
Re: [LAD] Should LV2 Activate() clear MIDI CC parameters?, David Robillard, (Wed May 30, 5:24 pm)