[linux-audio-dev] +momentary, consolidated (ladspa.h.diff)

[Taybin Rutkin]

Please consider MOMENTARY from a UI point of view.  A MOMENTARY would have to be a button or button like object (ncurses).  In that case, the values its use implies are either hardcoded in the plugin, or previously chosen by the user.  Being boolean is not a limitation on the use of the push button.

Taybin

-----Original Message-----
From: Tim Goetze <tim at quitte.de>
Sent: Mar 8, 2004 11:19 AM
To: Taybin Rutkin <taybin at earthlink.net>, 
	The Linux Audio Developers' Mailing List <linux-audio-dev at music.columbia.edu>
Subject: Re: [linux-audio-dev] +momentary, consolidated (ladspa.h.diff)

[Taybin Rutkin]
>Please make MOMENTARY imply TOGGLED.  This lets older hosts degrade
>gracefully.

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.

[Taybin Rutkin]
>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
>confusing.

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?

amicalement,

tim