[LV2] self automating plugins - RFC

Robin Gareus robin at gareus.org
Mon Feb 22 12:35:11 PST 2016

On 02/22/2016 08:34 PM, Hanspeter Portner wrote:

> I was just wondering if one could reuse already existent infrastructure...

yes, that would be desirable. It'd also be nice if existing plugins  and
hosts could support this easily without major changes.

ie. re-use control ports that are already in place (no hard dependence
on Patch:Set).

Patch is not only for plugin DSP <> plugin GUI.
DSP <> UI communication does not need to adhere to any standard. A
protocol is only needed if a 3rd party - e.g Host or other plugin - is

Hosts can parse/generate Patch:Set/Get for setting/querying e.g. MIDI
bindings or filenames or, well, plugin-properties in general.

I only know of two LV2 hosts that have automation lanes.
Ardour (and derivatives) uses Patch:Set/Get for filenames (e.g
convolution IR) and AFAIK QTractor has no internal support for Patch, yet.

I'll respond to the rest of the email later, I'll have to mull this over.


More information about the Devel mailing list