W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Reviewing the Web Audio API (from webrtc)

From: Randell Jesup <randell-ietf@jesup.org>
Date: Tue, 10 Apr 2012 16:38:05 -0400
Message-ID: <4F849A2D.2080901@jesup.org>
To: public-audio@w3.org
On 4/10/2012 4:21 PM, Randell Jesup wrote:
> Another example is an AGC, Dynamic Range Compressor, or Limiter using a look-ahead
> to avoid having to use extreme attack values.  This could induce 5, 10 or more ms
> of delay.  An extreme version of look-ahead is Rob's "ducking" example for doing
> voice-overs, where you might have 1/4, 1/2 or 1 second delay.

And of course the API includes DelayNodes....  Those could really mess 
up AV synchronization.  You could try to add equivalent delay on a 
separate video path, but likely they wouldn't match perfectly.  Perhaps 
well enough, but...  Also, it might be painful to re-combine them, and 
"correct" synchronization may be lost at that point (you might be stuck 
with however close you had it at the recombination point).

Randell Jesup
Received on Tuesday, 10 April 2012 20:42:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:59 UTC