On Tue, Mar 8, 2011 at 10:46 PM, linuxdsp <mike@email-addr-hidden> wrote:
> Paul Davis wrote:
>
>> not that i'm aware of ... could you go into a bit more detail about this?
>> i don't care that someone is using QTractor - its a fine program - but
>> i'm really not sure if the claim you made is correct, and i'd like to
>> understand it.
>> _______________________________________________
>> Linux-audio-user mailing list
>> Linux-audio-user@email-addr-hidden
>> http://lists.linuxaudio.org/listinfo/linux-audio-user
>>
>> Perhaps I can add something to this.. Paul - I think what this is about
> is that there is no way (as far as I'm aware) to assign a MIDI controller to
> a control on an LV2 (if it has its own UI). I think the nicest way to do
> this would be to adopt a scheme similar to assigning other controls, where
> the control is moved and the corresponding MIDI controller is 'learned' and
> associated with the control.
>
> - For example in energyXT, you just choose the MIDI controller, and then
> tell the program to learn a corresponding control (even on a VST plugin) by
> just moving the required control.
>
> From a plugin developers point of view, this would best be handled by
> ardour just listening to or generating the LV2 port events in response to
> the midi control (in the same way that automation can generate port events)
> rather than any fundamental changes to the way the LV2 GUI controls are
> handled. This would mean no changes would be necessary to the LV2 plugins
> (good from my point of view) and it would probably also just work with
> plugins that don't generate their own UI (if that isn't handled already)
>
>
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.
-michael
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Wed, 9 Mar 2011 00:15:43 +0900
This archive was generated by hypermail 2.1.8 : Tue Mar 08 2011 - 20:15:03 EET