[LV2] Request: Can-Randomize control hint

David Robillard d at drobilla.net
Fri Mar 21 10:27:05 PDT 2014

On Mon, 2014-03-17 at 17:45 +0000, Filipe Coelho wrote:
> On 03/17/2014 05:20 PM, David Robillard wrote:
> > On Sun, 2014-03-16 at 14:57 +0000, Filipe Coelho wrote:
> >> Hi there, I have a request for LV2.
> >>
> >> I'm currently implementing a randomize option for plugin parameters in
> >> my host, and realized some params should never be changed this way (like
> >> volume).
> >> [...]
> >> Something like:
> >> http://lv2plug.in/ns/ext/port-props#canRandomize
> >
> > Bit of a vague situation specific definition, seems to be a level above
> > the underlying meaning, so to speak
> > [...]
> > Would something like affectsLevels be more appropriate?
> Probably, yes.
> On 2nd though "cannotRandomize" would make more sense over "canRandomize".

> > What are the "few others"?  If it's really just levels, then looking for
> > that specific designation actually seems like a better solution to me,
> > since that designation is also very useful in many cases and adding
> > incentive for plugins to use it would be a good thing.
> Perhaps.
> I can't think of other types of parameters that should never be 
> randomized right now, but they might exist.

I'm not actively opposed to a randomize hint, just if there's something
more generically useful and meaningful that'd also work, it would be
better, i.e. it would be better to annotate WHY you wouldn't want to
randomize it, is possible.

> What do you think about "cannotRandomize"?

I think this is better.  The default for controls is to be able to set
to anything.  Some well-designed are specifically designed so that
basically any setting will do something reasonable (much like what Moog
strives for in hardware).

Ports that, for some strange reason, shouldn't be set to a valid value
in their range, are definitely the exception, not the rule.


More information about the Devel mailing list