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

[web-audio-api] (AudioBufferDirectAccess): AudioBuffer direct access (#124)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:28 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/124@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17401](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17401) Tue, 05 Jun 2012 12:27:00 GMT
> Reported by Michael[tm] Smith
> Assigned to 

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/124
Received on Wednesday, 11 September 2013 14:28:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC