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

Audio-ISSUE-49 (AudioBufferDirectAccess): AudioBuffer direct access [Web Audio API]

From: Audio Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 15 May 2012 15:09:27 +0000
Message-Id: <E1SUJNP-0002Si-Uf@tibor.w3.org>
To: public-audio@w3.org
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.
Received on Tuesday, 15 May 2012 15:09:40 GMT

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