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:

[MikeSmith]: https://www.w3.org/Bugs/Public/show_bug.cgi?id=17349

5 Jun 2012, 13:49:38

Display change log ATOM feed


Matthew Paradis <matthew.paradis@bbc.co.uk>, Raymond Toy <rtoy@google.com>, Chairs, Chris Lilley <chris@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 58.html,v 1.1 2019/11/12 13:32:30 carcone Exp $