some people opined that it could as well be done in LV2 using an
You might want to talk to Richard Furse as well about this, who is the
author of LADSPA and IIRC he told me he wasn't reading LAD mails lately. Yo=
u
can find his email at the bottom of the main www.ladspa.org page.
> but the host has no way of knowing that the upper bound is next to the=
> lower bound, so that it can chose the shortest path to the next value<=
br>
ve
t
> the image to jump in weird ways, because it doesn't know that 180 =
=3D=3D -180.
br>
to summarize: there seem to be no objections to adding such a hint
(stefano's initial critique was about just using it without adding it t=
o
the standard LADSPA header, iiuc, which has never been intended).
Yeah, I just misread your original post, sorry.
some people opined that it could as well be done in LV2 using an
extension. there is no consensus yet about whether this belongs in the
existing units extension, but this is orthogonal to the LADSPA issue.
during the discussion, fons brought up the issue of adding an enum type
to integer ports, to enable hosts to display meaningful string values
for radio-button-type controls. the general usefulness of this was
undebated.
an RFC for a LADSPA 1.2 revision including both the "periodic" an=
d the
"enum" hints will be posted in a new thread.You might want to talk to Richard Furse as well about this, who is the aut=
hor of LADSPA and IIRC he told me he wasn't reading LAD mails lately. Y=
ou can find his email at the bottom of the main www.ladspa.org page.
Stefano