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

Re: Preparing the vote on the data race issue

From: Jer Noble <jer.noble@apple.com>
Date: Tue, 30 Jul 2013 15:51:40 -0700
Cc: Marcus Geelnard <mage@opera.com>, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>, Joseph Berkovitz <joe@noteflight.com>, WG <public-audio@w3.org>
Message-id: <039BA296-4444-45C8-A011-B7D6847D6A04@apple.com>
To: Ehsan Akhgari <ehsan.akhgari@gmail.com>

On Jul 30, 2013, at 3:03 PM, Ehsan Akhgari <ehsan.akhgari@gmail.com> wrote:

> ...and as I've suggested before (http://lists.w3.org/Archives/Public/public-audio/2013JulSep/0199.html) I would really like us to consider replacing AudioBuffers with (ownership transferred) Float32Arrays for the AudioProcessingEvent (short version: AudioBuffers are mostly off-line generated and static, while the data passed to/from an AudioProcessingEvent is purely dynamic and temporary).
> If we do that, then we should also require those typed arrays to be neutered when the event handler fully executes which I believe is what Roc proposed.
> Exactly. I think it's the best solution for the AudioProcessingEvent. Especially with Jer's proposal (which IMO makes it clearer that AudioBuffers belong to the audio engine), it makes even more sense to use typed arrays + neutering for the AudioProcessingEvent (which should be very tightly coupled to the audio engine, IMO).
> I think this would be a good idea.

I think we should hold off on this suggestion until we resolve the “ScriptProcessorNode processing in workers” issue <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415>, as it's possible solutions there would make neutering unnecessary.

Received on Tuesday, 30 July 2013 22:53:10 UTC

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