This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17349 - createScriptProcessor bufferSize limits and purpose
Summary: createScriptProcessor bufferSize limits and purpose
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 11:40 UTC by Philip Jägenstedt
Modified: 2014-10-28 17:17 UTC (History)
2 users (show)

See Also:

Attachments

Description Philip Jägenstedt 2012-06-05 11:40:36 UTC 
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?
Comment 1 Olivier Thereaux 2013-07-26 15:00:04 UTC 
Updating issue title to reflect the change of name from JavaScriptAudioNode to ScriptProcessorNode, and in particular the createScriptProcessor method.
Comment 2 Olivier Thereaux 2014-10-28 17:14:49 UTC 
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 3 Olivier Thereaux 2014-10-28 17:17:47 UTC 
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.