Paul Davis wrote:
On Tue, Mar 8, 2011 at 10:15 AM, michael noble <looplog@xxxxxxxxx> 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:
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.
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.
Normally, (in some other DAWs), the MIDI learn style of binding is
initiated with some action by the user on the host e.g. the user clicks
on an option in one of the hosts standard menus (not a plugin specific
menu) e.g. just a generic 'Options->MIDI Learn' kind of thing, or
activates a general purpose host key binding, then the user is prompted
through a sequence of operations along the lines of 'Operate control on
MIDI device' followed by 'Operate Control on GUI' and the two events are
then bound together. This doesn't require any special menus or options
on the plugin since its not specific to plugins, it just allows anything
the user can generate events from (MIDI controllers, LV2 ports via
plugin UIs, normal host controls etc.. to be bound together). That said
it sounds like A3s method of setting bindings to LV2 ports is a
perfectly good way of achieving the same result, so perhaps its not
really an issue.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
