ISSUE-49: (Bugzilla 17401) AudioBuffer direct access

AudioBufferDirectAccess

(Bugzilla 17401) AudioBuffer direct access

State:

CLOSED

Product:

Web Audio API

Raised by:

Philip Jägenstedt

Opened on:

2012-05-15

Description:

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.

Related Actions Items:

No related actions

Related emails:

1. [web-audio-api] (AudioBufferDirectAccess): AudioBuffer direct access (#124) (from notifications@github.com on 2013-09-11)
2. Re: third public Working Draft of the Web Audio API available (from tmichel@w3.org on 2012-08-02)
3. Re: State of issues as of 2012-05-30 (from philipj@opera.com on 2012-06-01)
4. Re: Audio-ISSUE-49 (AudioBufferDirectAccess): AudioBuffer direct access [Web Audio API] (from philipj@opera.com on 2012-06-01)
5. State of issues as of 2012-05-30 (from olivier.thereaux@bbc.co.uk on 2012-05-30)
6. Re: [Agenda] W3C Audio WG Teleconference, 30th May 2012 (from olivier.thereaux@bbc.co.uk on 2012-05-30)
7. Re: Audio-ISSUE-49 (AudioBufferDirectAccess): AudioBuffer direct access [Web Audio API] (from olivier.thereaux@bbc.co.uk on 2012-05-25)
8. Re: Summary of issues (from crogers@google.com on 2012-05-22)
9. Summary of issues (from mage@opera.com on 2012-05-22)
10. Audio-ISSUE-49 (AudioBufferDirectAccess): AudioBuffer direct access [Web Audio API] (from sysbot+tracker@w3.org on 2012-05-15)

Related notes:

Display change log