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

Re: memory footprint of AudioBuffer data copies

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 31 Jul 2013 10:47:39 +1200
Message-ID: <CAOp6jLa9KrGEw1TJya_RnP458ASU79KPuS7sdd3hzX4CLo7wSA@mail.gmail.com>
To: Jer Noble <jer.noble@apple.com>
Cc: Joseph Berkovitz <joe@noteflight.com>, WG WG <public-audio@w3.org>
On Wed, Jul 31, 2013 at 3:18 AM, Jer Noble <jer.noble@apple.com> wrote:

> What's more, you probably wouldn't want to synthesize the AudioBuffers
> entirely in advance either.  You'd synthesize a few chunks, schedule them
> for their specific times, and as they finished playing, you would
> synthesize additional chunks.  You might even implement a ringbuffer
> structure, so that later chunks imposed no additional memory or GC costs.
>  In that way, both the 2x chunk size would be mitigated, as would the
> overall outstanding buffer size would be limited to the size of your
> ringbuffer.

Why would you do this instead of just scheduling multiple

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, 30 July 2013 22:48:06 UTC

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