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

How should a host deal with a port that is MOMENTARY, but not TOGGLED? What would the UI be? Taybin -----Original Message----- From: Tim Goetze <tim(a)quitte.de> Sent: Mar 8, 2004 1:06 PM To: The Linux Audio Developers' Mailing List <linux-audio-dev(a)music.columbia.edu> Subject: Re: [linux-audio-dev] +momentary, consolidated (ladspa.h.diff) ok, suppose we say only MOMENTARY, and one-shot triggering is always rising edge. now we have another problem: Taybin is pretty adamant in requiring MOMENTARY to imply TOGGLED. this means we'll always need another port to transmit the velocity value for note-on and similar events. fine, no problem? apart from this meaning a waste of resources, how do we transmit two such impulses in successive run() calls? simply split the run() call in two? at what a waste of resources do we arrive then, for the doubtful pleasure of having a 'simple' model. beats the intention of simplicity if you ask me.