relevant plugins). However, what should be done for the case of plugins
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Aug 9, 2012 at 10:39 AM, David Robillard wrote:
> On Wed, 2012-08-08 at 05:59 -0400, Jeremy Salwen wrote:
Content-Type: text/html; charset=ISO-8859-1
On Thu, Aug 9, 2012 at 10:39 AM, David R=
obillard <email@example.com> wrote:
On Wed, 2012-08-08 at 05:59 -0400,=
Jeremy Salwen wrote:
I have added the property midi:binding, i.e.
lv2plug.in/ns/ext/midi#binding , to the MIDI extension. =A0As far
as specs go, this is all that is required.
It is not documented online yet because the docs are not uploaded until
release, but it is in svn and you can build those docs if you want, but
essentially they boil down to the example:
port midi:binding [
=A0 =A0 a midi:Controller ;
=A0 =A0 midi:controllerNumber 17
Thanks, that's all I wanted.=A0 I'=
m going to add support to my host (and relevant plugins).=A0 However, what =
should be done for the case of plugins with multiple MIDI inputs?=A0 Is thi=
s beyond the use-case of midi binding, or should the extension be expanded =
to specify which event port it is referring to?