This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Audio-ISSUE-13 (jsnode-delay): JavaScriptNode Delays [Web Audio API] http://www.w3.org/2011/audio/track/issues/13 Raised by: Matthew Paradis On product: Web Audio API As raised in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0096.html “We have noticed that a difference between the use of the JSNode and native nodes is an introduction of a delay equal to the block size of the node. While this is not a problem for a linear graph which has no dependance on the phase accuracy of audio channels, it does cause a problem when phase is an issue.”
Comment from Chris Rogers, 9 May 2012: « For synthesis of "notes" using custom DSP in a JavaScriptAudioNode, I believe the .playbackTime attribute is sufficient for synchronization: https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#AudioProcessingEvent In the more general case of processing with effects (not synthesis), we should probably expose a .latency attribute on AudioNode so that appropriate compensation can be done in the use cases where it needs to be done. Mailing list post with quite a bit of detail about latency and compensation strategies: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0066.html »
Changed title of the issue to reflect renaming of JavaScriptAudioNode to ScriptProcessorNode.
Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.