W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

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

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:10 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/81@github.com>
> 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
Received on Wednesday, 11 September 2013 14:28:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC