W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

Re: AudioBuffer mutability

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 30 Oct 2012 22:37:47 +1300
Message-ID: <CAOp6jLZfe1X2TC-nSc=WJP5f9+GjY=FVPzTCUkyfXGVF29OVPg@mail.gmail.com>
To: Srikumar Karaikudi Subramanian <srikumarks@gmail.com>
Cc: Chris Rogers <crogers@google.com>, Joseph Berkovitz <joe@noteflight.com>, Ehsan Akhgari <ehsan.akhgari@gmail.com>, public-audio@w3.org
On Tue, Oct 30, 2012 at 9:26 PM, Srikumar Karaikudi Subramanian <
srikumarks@gmail.com> wrote:

> At a small cost, you can keep a copy of the buffer on the main thread to
> satisfy these requirements.
> If a buffer were to be read locked once assigned to a source node, it
> would mean we cannot assign the same buffer to multiple source nodes to
> trigger multiple voices using the same underlying sample (like with
> granular synthesis) ...

An AudioBuffer would always be usable with any number of
AudioBufferSourceNodes. No-one is suggesting changing that.

Jesus called them together and said, “You know that the rulers of the
Gentiles lord it over them, and their high officials exercise authority
over them. Not so with you. Instead, whoever wants to become great among
you must be your servant, and whoever wants to be first must be your
slave — just
as the Son of Man did not come to be served, but to serve, and to give his
life as a ransom for many.” [Matthew 20:25-28]
Received on Tuesday, 30 October 2012 09:38:16 UTC

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