17349 2012-06-05 11:40:36 +0000 createScriptProcessor bufferSize limits and purpose 2014-10-28 17:17:47 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED WONTFIX P2 normal TBD 1 philipj dave.null olivier.thereaux public-audio dave.null oldest_to_newest 68660 0 philipj 2012-06-05 11:40:36 +0000 Audio-ISSUE-58 (JavaScriptAudioNodeBufferSize): JavaScriptAudioNode.bufferSize limits and purpose [Web Audio API] http://www.w3.org/2011/audio/track/issues/58 Raised by: Philip Jägenstedt On product: Web Audio API Why is bufferSize limited to 256, 512, 1024, 2048, 4096, 8192, 16384? The numbers look completely arbitrary. How should Web authors arrive at a buffer size that will allow them to achieve glitch-free playback across devices? Why is bufferSize exposed on the JavaScriptAudioNode interface after creation? 91317 1 olivier.thereaux 2013-07-26 15:00:04 +0000 Updating issue title to reflect the change of name from JavaScriptAudioNode to ScriptProcessorNode, and in particular the createScriptProcessor method. 113957 2 olivier.thereaux 2014-10-28 17:14:49 +0000 Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues 114106 3 olivier.thereaux 2014-10-28 17:17:47 +0000 Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.