[Ardour-Users] lv2 and midi control
looplog at gmail.com
Thu Dec 10 17:00:25 PST 2009
On Wed, Dec 9, 2009 at 9:22 PM, Paul Davis <paul at linuxaudiosystems.com>wrote:
> On Wed, Dec 9, 2009 at 1:30 AM, Nedko Arnaudov <nedko at arnaudov.name>
> > Other possible solution would be an lv2 extension to enable this
> > functionality in lv2 plugins.
> > Am I right that this will not work for GtkGUI (embedded) too?
> i don't see how it could. it requires either:
> (a) explicit communication between plugin & host regarding binding
> (b) MIDI fed to the plugin and handled entirely by the plugin
> ardour2 doesn't do (b)
I hope you'll bear with me for continuing with this, but as I see it, if LV2
is supposed to become the defacto plugin standard on linux for the future,
and ardour wishes to support it, I don't see how this can not become a
greater issue as time goes on.
>From what I can tell then, ardour is binding midi control not to the
parameter per se, but to the ardour GUI element? Is this correct?
If this is the case, would a possible workaround to the external GUI problem
be to include a parameter slider or similar representative GUI element on
the automation track itself. In this way, automation and midi binding could
be managed from the same place for individual parameters without the need to
load the main plugin GUI at all.
I know this is quite a significant design change; just throwing ideas out to
what, as I said, could become a sticking point for future ardour use under
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ardour-Users