Subject: Re: +trigger, Re: [linux-audio-dev] ladspa.h.diff
From: Steve Harris (S.W.Harris_AT_ecs.soton.ac.uk)
Date: Fri Mar 05 2004 - 22:16:58 EET
On Fri, Mar 05, 2004 at 07:14:41 +0100, Tom Szilagyi wrote:
> I like this new LADSPA spec. very much, thanks to Tim Goetze for working
> it out! However, i have one bit of concern:
>
> /* This member indicates the delay, in 1 / (sample rate) time units,
> the plugin imposes upon processed signals. */
> const LADSPA_Data Latency;
>
> Wouldn't this break the possibility of adequate operation of plugins that
> have a latency value dependent on user settings (ie. not constant)?
The problem with non-constant latency is that it requires the host to set
the parameters and call run() once before it will know the value.
Also the semantics of variable latency are very confused - as the value
can vary at any point furing the run() steps the host cant know how to
correctly interpolte between adjcent values. Its just much to hard to do
anythign useful with.
I also /really/ dont think it belongs in the struct - its not an essential
feature and few hosts will support it.
Either design your plugins to do internal lantecy correction and report
the total or live with uncorrected latency :)
- Steve
This archive was generated by hypermail 2b28 : Fri Mar 05 2004 - 22:17:05 EET