ISSUE-13: (Bugzilla 17391) JavaScriptNode Delays
jsnode-delay
(Bugzilla 17391) JavaScriptNode Delays
- State:
- CLOSED
- Product:
- Web Audio API
- Raised by:
- Matthew Paradis
- Opened on:
- 2012-05-03
- Description:
- 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.» - Related Actions Items:
- No related actions
- Related emails:
- [web-audio-api] ScriptProcessorNode Delays (#99) (from notifications@github.com on 2013-09-11)
- Minutes of audio WG Teleconference, 2012-05-09 (from olivier.thereaux@bbc.co.uk on 2012-05-10)
- Audio-ISSUE-13 (jsnode-delay): JavaScriptNode Delays [Web Audio API] (from sysbot+tracker@w3.org on 2012-05-03)
Related notes:
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
Setting as OPEN.
Olivier Thereaux, 30 May 2012, 20:23:00[MikeSmith]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17391
5 Jun 2012, 13:30:44Display change log
