[LV2] Control ports vs lv2:Parameter

[Stefano D'Angelo]

Il giorno mar 25 giu 2024 alle ore 23:27 David Robillard
<d at drobilla.net> ha scritto:
> On Thu, 2024-06-06 at 12:05 +0200, Stefano D'Angelo wrote:
> > 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?
>
> Both mechanisms can be used to refer to the same "conceptual" parameter
> in a sense, by giving ports an lv2:designation.  This doesn't amount to
> a graceful degradation mechanism for old hosts, though (it could be
> useful for version and/or state migration among other things, but it's
> not a mechanism).
>
> I guess you could invent one - a message to disable actually using the
> value of the control ports or something - but it seems like it would be
> quite a mess.
>
> I'd suggest just being the chicken or the egg instead, so to speak.

Ok, clear. I guess I'll have to support one mechanism per plugin,
perhaps having different versions of the same plugin if I want to
support both.

Maybe in the future we could have something like
"is-an-advanced/better-version-of" predicate in the RDF - like dc:
replaces -, so that hosts might actually hide the "not advanced/worse"
plugin if the better one is supported?

Stefano