This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Audio-ISSUE-14 (quinnirill): Default value for bufferSize in createJavaScriptNode() [Web Audio API] http://www.w3.org/2011/audio/track/issues/14 Raised by: Jussi Kalliokoski On product: Web Audio API Jussi Kalliokoski suggested that the first argument of AudioContext:createJavasScriptNode, (buffer size) would be made optional. In addition, it could be specified so that an advanced implementation would adjust the default value to be an optimal balance between reliability (avoiding glitches and underruns) and latency on that system and setup.
Comment from Jussi in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0106.html « We discussed with Chris (off-list) the recent change from numberOfOutputs to numberOfChannels in the createJavaScriptNode(), because I noticed my sink.js was broken in the latest Chrome Canary. I suggested that the first parameter (bufferSize) be optional as well, reverting to default when passed undefined. In an advanced implementation, this default could be adjusted to a value that the implementation deems a good tradeoff between safety (avoiding underruns) and latency on that system and setup. I believe Chris thinks this is a good idea, so he suggested I bring this to discussion in the group so we can change the spec if we agree on it. »
The method is currently defined as: ScriptProcessorNode createScriptProcessor(optional unsigned long bufferSize = 0 … Is this issue still valid or is has it been fixed already?
Updating issue title to reflect the change of name from JavaScriptAudioNode to ScriptProcessorNode, and in particular the createScriptProcessor method.
I think it's safe to call this fixed.
Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.