Content-Type: text/plain; charset="UTF-8"
On Sun, 2013-02-10 at 01:01 +0000, Harry van Haaren wrote:
Both are possible depending on the details of the plugin. Plugins can
not change their own control inputs, so if you have ControlPorts then
the host must do it. As things move to event-based control this will go
away, but that's perhaps a discussion for another time.
Note that in a plugin that supports CC directly it's not necessarily
true that the CC numbers are hard coded. You could use other events to
configure them dynamically.
With this stuff, unfortunately, the answer is almost always "both", and
then some. Some plugins are dumb, some are pretty clever, and some are
even a full-blown host with its own dynamic MIDI binding implementation.
> I think the "safe option" is number 2, each application sorts this thing
The LV2 midi extension includes a vocabulary that can be used to
describe MIDI bindings in a standard way. For this we may need a new
Bindings class or something, but the guts of describing controllers and
associating ports with bindings are already there.
No particularly deep problems here that I can see if you're just
interested in the MIDI bindings for control ports case, it just needs
establishing, which would indeed be a nice thing to do. An idiot-proof
API in lilv would probably make it much nicer for hosts to implement.
(Interestingly this is very preset-like in many ways)
I'm assuming you mean just for LV2, if you mean broader scope then of
course there are a whole slew of additional questions.
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----