[LV2] UIs for mono plugins

Johannes Lorenz j.mailing at lorenz-ho.me
Mon Jul 22 13:39:05 PDT 2019

>> * If two UIs make sense, should we allow a user to link controls by
>> using the "touch" feature? I.e.:
>>   1. user presses a host button "link controls"
>>   2. host UI tells user: now touch a plugin control
>>   3. user touches plugin control
>>   4. host UI recognizes touch and next time one mono plugin's control
>> changes it somehow updates the control for the other mono plugin
> Why so complicated? Parameters in LV2 have unique identifiers, so LMMS
> should be able to link each parameter pair without user interaction.
> My suggestion would be to develop a set of controls, which can act
> either as a pair (of sliders, dials, buttons, etc) or as single ones,
> switchable by "link" button below. The second slider, dial, button etc.
> of a pair may or may not be hidden dynamically, when "link" is 
> activated
> or just greyed out (deactivated).

If I'm not mistaken LMMS should not develop controls for external 
("plugin") UIs. Why providing controls in LMMS when they are already in 
the plugin UI?

My question was based on UIs the plugin brings: How many such UIs should 
we show and how should we sync the controls between two such UIs.

Apologies if this wasn't written clear, or if I got you completely wrong 

More information about the Devel mailing list