W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Audio-ISSUE-58 (JavaScriptAudioNodeBufferSize): JavaScriptAudioNode.bufferSize limits and purpose [Web Audio API]

From: Audio Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 15 May 2012 15:52:17 +0000
Message-Id: <E1SUK2r-0002sN-SJ@tibor.w3.org>
To: public-audio@w3.org
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?
Received on Tuesday, 15 May 2012 15:52:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 May 2012 15:52:29 GMT