Subject: Re: [linux-audio-dev] +momentary, consolidated (ladspa.h.diff)
From: Tim Goetze (tim_AT_quitte.de)
Date: Mon Mar 08 2004 - 23:45:26 EET
[Jesse Chappell]
>The problem with an arbitrarily valued MOMENTARY/TRIGGER port
>is specifying the trigger "low" value. Is it 0.0? Is it anything
>out of the hinted range of the port?
the patch states that the 'low' value is always zero, and that zero
needs not be inside the value range.
>BTW, this is exactly why no generic host can use the sooperlooper
>plugin... i had to treat one control port as effectively MOMENTARY
>and arbitrary valued. It expected the host to take the port out of
>range for a run() cycle before being able to retrigger. The trigger
>resolution is limited to 2 run() boundaries, and that problem can
>only be remedied by either splitting the run() or using an audio rate
>control port. But SL shouldn't really be a ladspa plugin anyway....
>someday soon it will be a standalone jack client.
fwiw, i prefer ladspa units if at all possible for less overhead and
greater control. i'm sure others prefer a jack client with a snappy
UI. :)
amicalement,
tim
This archive was generated by hypermail 2b28 : Mon Mar 08 2004 - 23:50:17 EET