[LV2] Control ports vs lv2:Parameter

[Hermann Meyer]

Am 06.06.24 um 12:05 schrieb Stefano D'Angelo:
> Hi all,
>
> Is there a way to provide "graceful degradation" for hosts that do not
> support lv2:Parameter but still use lv2:ControlPort? Should/could both
> mechanisms be used to refer to the same parameter?

Hi Stefano

Short answer (from my knowledge) is "NO". lv2:parameter is a atom based
control. That could be a Path, a string, a vector, or what ever data
could be shared between the dsp thread and the GUI. May be a simple
float or int value, may be.But if, a plug announce a port as
lv2:parameter it properly wont react on a message via a control port.
And visa verse.


> BTW, are there such hosts around still? Ardour, Reaper, and Qtractor
> seem to support lv2:Parameter, Audacity behaves weirdly with
> https://github.com/x42/property_example.lv2 on my laptop (the
> auto-generated GUI is created and instantly disappears). What about
> e.g. PipeWire? Does anybody know?

Pipewire, ALSA, jackd, ASIO, coreaudio, all that didn't matter for a LV2
plug. It will never interact with a sound server, it interact with the
host loading it.

I just tested some plugs with Audacity after your post, and simply,
Audacity didn't support atom ports, the plugs I tested it present simply
without there atom ports (lv2:parameter). Still you could load presets
to use those plugs in Audacity.

regards

hermann

> Best,
>
> Stefano D'Angelo
> _______________________________________________
> Devel mailing list
> Devel at lists.lv2plug.in
> http://lists.lv2plug.in/listinfo.cgi/devel-lv2plug.in