[web-audio-api] createScriptProcessor bufferSize limits and purpose (#81)

> Originally reported on W3C Bugzilla [ISSUE-17349](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17349) Tue, 05 Jun 2012 11:40:36 GMT
> Reported by Philip Jägenstedt
> Assigned to 

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?

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/81