Subject: RE: [linux-audio-dev] Lots about latency and disk i/o and JACK...
> -----Original Message-----
This isn't clear - a LADSPA control value can only be changed between calls
Incidentally, an SAOL->LADSPA compiler sounds like an interesting project.
--Richard
This archive was generated by hypermail 2b28
: Thu Oct 04 2001 - 23:29:35 EEST
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Thu Oct 04 2001 - 23:28:52 EEST
> From: owner-linux-audio-dev_AT_music.columbia.edu
> [mailto:owner-linux-audio-dev_AT_music.columbia.edu]On Behalf Of Paul Davis
> Sent: 04 October 2001 02:52
[...]
> a LADSPA control port may have its value
> changed at *any* time. there is no inherent control rate built into or
> implied by the control port. the frequency with which the plugin can
> notice the changes is limited *within the host thread that calls the
> plugin* by the audio block size, but other parts of the plugin (e.g. a
> GUI) can inspect the port at any time.
[...]
to run() on the plugin, so during that call the plugin is guaranteed that
the value will be constant. The term "control rate" becomes meaningful with
LADSPA when run() calls work on a standard block size (kr=sr/ksmps, you know
this stuff) and (implicit) control values are handled at this rate.
My memory of SAOL minutae has faded, and I suspect there might be some
issues with I-time processing and the number of operators that might have to
be coded up - but otherwise I think this is probably straightforward.