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-49 (AudioBufferDirectAccess): AudioBuffer direct access [Web Audio API] http://www.w3.org/2011/audio/track/issues/49 Raised by: Philip Jägenstedt On product: Web Audio API getChannelData is documented as "Gets direct access to the audio data stored in an AudioBuffer" but "direct access" is not defined. For example, if a reference to an AudioBuffer is kept and the data is modified after the audioprocess event handler has finished running, what will happen? One approach would be similar to what happens with postMessage and typed arrays, at least in Opera. There, once the ownership of an array is transferred, it becomes a dummy array of length zero that cannot be modified. This does not require copying the memory to achieve "concurrency safety", it is merely a flag on the ECMAScript host object.
[admin] Assigning items currently being worked on by editor.
Changeset from the editor: https://dvcs.w3.org/hg/audio/rev/5f1f174d7603
More feedback from Philip in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0485.html The suggested change effectively requires the audio data to be copied when the audioprocess callback returns, which isn't necessary to solve the problem. We suggest defining it in terms of ownership transfer,[1] like when a typed array is used with postMessage. In other words, the Float32Array should be neutered, after which reading the length property returns 0.[2] [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#transferable-objects [2] http://www.khronos.org/registry/typedarray/specs/latest/#7
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.