Content-Type: text/plain; charset="UTF-8"
On Wed, 2012-08-08 at 09:28 +1200, Jeff McClintock wrote:
The plugin indicating it's bindings is the *only* thing to do here.
Otherwise, the host can just bind however it wants.
It is a simple idea much older than that thread, just nobody has done it
yet. Doing it statically is trivial: just set properties on ports to
indicate their binding.
Static is not so useful though, and control ports suck for a slew of
other reasons anyway, so this has not been established. To do it right,
and dynamically, the things mentioned in my previous reply need doing
> Cool, I like it. I disagree that synthesisers are 'border cases' though ;=
Indeed. *Global* "bloat" is, by far, the most important consideration.
If there is a One True Software Quality Metric, it is certainly lack of
That said, I don't think there would be any considerable bloat of any
variety related to the issues under discussion.
> The one other reason you want the host handling the MIDI Binding...
I think reality is being slightly misrepresented here: to be clear, it
is not common in LV2 land for plugins to support parameters via MIDI CC
in this way, for all the obvious reasons you have mentioned several
times. Apparently that is common in the VST world, which is why you
want to "argue" for it, but I find that quite strange. Clearly mystery
MIDI parameters in plugins is crap.
Which is to say: Yes, that is stupid; and no, that is not common LV2
practice, nor will it ever be. Preaching to the choir, Jeff :)
LV2 synthesizers typically use MIDI *for notes* for lack of a better
standard at the moment, but not for parameters.
> What if they all happen at once? Only the host is in a position to mediat=
This will be an issue to consider if people want a graceful migration
path to events, i.e. events can be used to control the same parameter as
a control port (which is essentially exactly the same issue, except not
Personally I think it's not worth the effort (and don't really think
backwards compatibility gunk belongs in plugins whatsoever).
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-----