Re: DynamicsCompressorNode and latency

On Tue, Jul 10, 2012 at 1:36 AM, olivier Thereaux <
olivier.thereaux@bbc.co.uk> wrote:

> I'm not sure I understand how this look-ahead is any different from (and
> thus more problematic than) the buffering (and thus the delay) created by
> the JavaScriptNodes?
>
> https://en.wikipedia.org/wiki/Dynamic_range_compression#Look-ahead
> «Look-ahead is a misnomer in that the future is not actually observed.
> Instead, the input signal is split, and one side is delayed. The
> non-delayed signal is used to drive the compression of the delayed signal,
> which then appears at the output. This way a smooth-sounding slower attack
> rate can be used to catch transients. The cost of this solution is that the
> signal is delayed.»
>

Ah, so it's not really lookahead. That clarifies things, thanks.

At some point we'll need actual lookahead, and it's going to be difficult
to fit in with Web Audio, but we'll cross that when we come to it I guess.

Rob
-- 
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be children of your Father in heaven. ... If you love those
who love you, what reward will you get? Are not even the tax collectors
doing that? And if you greet only your own people, what are you doing more
than others?" [Matthew 5:43-47]