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

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

From: olivier Thereaux <olivier.thereaux@bbc.co.uk>
Date: Fri, 25 May 2012 11:39:04 +0100
Message-Id: <95A7D17E-7BB3-4332-8493-BF95236068A4@bbc.co.uk>
To: Audio Working Group <public-audio@w3.org>
This issue is now pending review, per https://dvcs.w3.org/hg/audio/rev/5f1f174d7603

Olivier

On 15 May 2012, at 16:09, Audio Working Group Issue Tracker wrote:

> 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 Friday, 25 May 2012 10:40:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 May 2012 10:40:00 GMT