- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 25 Jun 2013 12:46:02 +1200
- To: Chris Rogers <crogers@google.com>
- Cc: "public-audio@w3.org" <public-audio@w3.org>
Received on Tuesday, 25 June 2013 00:46:29 UTC
There's another issue related to "live" Float32Arrays: developers neutering arrays themselves. Developers can pass a Float32Array's ArrayBuffer to postMessage as a Transferable, which neuters the array. What happens if they do that to one of the arrays returned by AudioBuffer.getChannelData() --- while the AudioBuffer is being played? If audio processing is using the same underlying data as the Float32Array, I'm guessing the answer is "something bad". The spec needs to say whether or how neutering a Float32Array affects usage of the ArrayBuffer. With my proposal, I would say that when we do an "acquire AudioBuffer contents" operation, if any of the Float32Arrays are neutered, then the acquired contents are treated as an AudioBuffer of length zero. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * *
Received on Tuesday, 25 June 2013 00:46:29 UTC