8 Mar
2011
8 Mar
'11
4:18 p.m.
On Tue, Mar 8, 2011 at 10:15 AM, michael noble <looplog(a)gmail.com> wrote:
Yes, the conversation was in regards to midi control
of parameters, hence my
statement. I raised the question on the ardour-users list on Dec 8, 2009, if
you wish to reference the conversation.
Paul, your response was:
ah, thanks for that. yes, indeed the binding system in a3 will fix
that issue, at least in the sense that MIDI binding maps can reference
any parameter in any plugin.
it doesn't address a "MIDI learn" style of binding, which i still
can't see how to implement since the action that would start it occurs
(presumably) with some user action in the plugin GUI, and the host
doesn't know about it.
they do not work. Ardour does not own or control
the windows that they
create (this includes LV2 ext GUI) and so there is no reasonably sane
way to interpose between the user's input devices and the GUIs in
order to initiate MIDI binding, etc.
There was some discussion of possible ways to get around this issue. At the
time, however, you regarded the issue as "just not very high on my list of
priorities." I believe you stated that the overhauled binding system in A3
would potentially fix the issue.