W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[Bug 22723] OfflineAudioContext and ScriptProcessorNodes

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Jul 2013 02:18:39 +0000
To: public-audio@w3.org
Message-ID: <bug-22723-5429-7kCgd5zSR2@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723

Ehsan Akhgari [:ehsan] <ehsan@mozilla.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ehsan@mozilla.com

--- Comment #2 from Ehsan Akhgari [:ehsan] <ehsan@mozilla.com> ---
We can also specify that when used with OfflineAudioContext, the implementation
must eliminate the latency and provide a zero latency non-glitching buffer in
the rendered buffer on the context.  I think doing that makes sense since the
latency added by ScriptProcessorNode is almost never desirable.  And also any
application that needs an initial latency can code that into the event handler
on the node, or route the output through a DelayNode.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 July 2013 02:18:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:10 UTC