[linux-audio-dev] +momentary, consolidated (ladspa.h.diff)
tim at quitte.de
Mon Mar 8 11:19:47 EST 2004
>Please make MOMENTARY imply TOGGLED. This lets older hosts degrade
a recommendation, yes i think that would be very sensible indeed.
please consider that implying TOGGLED makes MOMENTARY a '1 or 0'
valued control for all time, which is an unnecessary limitation.
>The presence of both MOMENTARY and TRIGGER seems redundent. TRIGGER
>means that it's reset to 0 after one call to run() or run_adding()?
>That'll happen so fast, the user won't even notice the UI change.
>If TRIGGER is for scale values, how will it scale if it's set to 0
>after every call? The distinction between them is overlapping and
TRIGGER is meant to accommodate MIDI and other mechanical trigger
sources, it's not exclusively tailored for display user interface
elements. there are a number of convenient ways to represent it
on-screen though, like the good old peak meter.
in fact there already are plugins implementing the TRIGGER behaviour.
it needs official status.
more opinions please?
More information about the linux-audio-dev