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

Re: memory footprint of AudioBuffer data copies

From: Joe Berkovitz <joe@noteflight.com>
Date: Wed, 31 Jul 2013 07:47:54 -0400
Message-Id: <21E9A1C2-542C-42F8-A49E-5B84761544BF@noteflight.com>
Cc: Jer Noble <jer.noble@apple.com>, WG WG <public-audio@w3.org>
To: "robert@ocallahan.org" <robert@ocallahan.org>
I think both scenarios are realistic. Chris W originally asked about creating a large AudioBuffer from scratch in a low memory environment, which one might want to cook up for later playback. But the multiple AudioBuffer approach is the only one that allows continuing chunked synthesis during playback without running afoul of Jer's locking scheme. 

.            .       .    .  . ...Joe

Joe Berkovitz
Noteflight LLC
+1 978 314 6271
"Your music, everywhere."

On Jul 30, 2013, at 6:51 PM, "Robert O'Callahan" <robert@ocallahan.org> wrote:

> On Wed, Jul 31, 2013 at 10:49 AM, Jer Noble <jer.noble@apple.com> wrote:
>> I guess I don’t understand your question: you /would/ schedule multiple AudioBufferSourceNodes.  Each with it’s own “chunk” of decoded audio data.
> Good. I think Joseph proposed something else, and you replied "yep", which confused me.
> Thanks,
> 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 Wednesday, 31 July 2013 11:48:23 UTC

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