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

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: linux-audio-dev <linux-audio-dev@...>
Date: Friday, May 25, 2012 - 7:22 am

--047d7b15b1698ce6eb04c0d73911
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

The LV2 spec says that on a call to activate(), "the plugin instance MUST
reset all state information dependent on the history of the plugin instance
except for any data locations provided by connect_port()"

I am not certain whether MIDI CC parameters are included in this category
of "data locations provided by connect_port()". The CC parameters are sent
through port buffers provided by connect_port(), but because they are *event
* buffers, all information passed through them is necessarily part of the *
history* of the plugin instance.

I could imagine cases where you would want to reset all internal state of
the plugin, but since CC values are very much like port values, they would
be kept. On the other hand, I could also imagine cases where you would
want to reset all internal data including the CC parameters.

I'm assuming MIDI note on/off status certainly should be reset.

Thanks,
Jeremy Salwen

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

Hi all,The LV2 spec says that on a call to activate(), "the pl=
ugin instance MUST reset all state information dependent on the=20
history of the plugin instance except for any data locations provided by
connect_port()"I am not certain whether MIDI CC parameters ar=
e included in this category of "data locations provided by connect_por=
t()".=A0 The CC parameters are sent through port buffers provided by c=
onnect_port(), but because they are event buffers, all information p=
assed through them is necessarily part of the history of the plugin =
instance.

I could imagine cases where you would want to reset all internal state =
of the plugin, but since CC values are very much like port values, they wou=
ld be kept.=A0 On the other hand, I could also imagine cases where you woul=
d want to reset all internal data including the CC parameters.

I'm assuming MIDI note on/off status certainly should be reset.=
Thanks,Jeremy Salwen

--047d7b15b1698ce6eb04c0d73911--

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?, 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)