On 2026-08-12 9:06 PM, Fons Adriaensen wrote:
Date: Wed, 12 Aug 2026 21:00:39 +0200
From: Fons Adriaensen <[email protected]>
To: Robin Gareus <[email protected]>
Subject: Re: More LV2 questions

On Wed, Aug 12, 2026 at 08:39:38PM +0200, Robin Gareus wrote:
On 2026-08-12 8:37 PM, Fons Adriaensen wrote:

Ardour could just send updates for automated parameters that
are in play or touch mode and then only while the user is not
'touching' the corresponding control.

That is exactly what Ardour does.

No it isn't. I get portevents for every parameter change sent
from the UI, even when there is no automation at all.


The correct flow is: The Plugin UI asks host to change a parameter. The host then either allows this or not. If the change succeeded, host informs the plugin UI about the new value.


As for telling the Plugin host that the user is touching the control you
need to implement https://lv2plug.in/ns/extensions/ui#touch

Done that a year ago.


good. Is the code available? Would be nice to have something to test.


As for managing windows, Ardour itself behaves in way I find
really annoying. When you close a plugin window it is not just
hidden, it's destroyed. So when the plugin UI is opened again
it has to be reconstructed from scratch. Ardour is just decent
enough to remember its previous position, but that's all.


For AU and VST3 there there is a preference for this. The default is to just hide the window. LV2 does not have this option.

--
robin

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to