ISSUE-58: (Bugzilla 17349) JavaScriptAudioNode.bufferSize limits and purpose

JavaScriptAudioNodeBufferSize

(Bugzilla 17349) JavaScriptAudioNode.bufferSize limits and purpose

State:

CLOSED

Product:

Web Audio API

Raised by:

Philip Jägenstedt

Opened on:

2012-05-15

Description:

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?

Related Actions Items:

No related actions

Related emails:

1. [web-audio-api] createScriptProcessor bufferSize limits and purpose (#81) (from notifications@github.com on 2013-09-11)
2. Re: Summary of issues (from crogers@google.com on 2012-05-22)
3. Summary of issues (from mage@opera.com on 2012-05-22)
4. Audio-ISSUE-58 (JavaScriptAudioNodeBufferSize): JavaScriptAudioNode.bufferSize limits and purpose [Web Audio API] (from sysbot+tracker@w3.org on 2012-05-15)

Related notes:

Display change log