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

Re: memory footprint of AudioBuffer data copies

From: Jer Noble <jer.noble@apple.com>
Date: Tue, 30 Jul 2013 10:26:19 -0700
Cc: "K. Gadd" <kg@luminance.org>, Chris Wilson <cwilso@google.com>, WG WG <public-audio@w3.org>
Message-id: <7C14B87F-A7CD-4539-A986-280989F8C04D@apple.com>
To: Joseph Berkovitz <joe@noteflight.com>

On Jul 30, 2013, at 10:22 AM, Joseph Berkovitz <joe@noteflight.com> wrote:

> Since I was also talking about mutexes (my email crossed with kg's) I appreciate the clarification.
> 
> I think the following key clause in your proposal could be refined to more carefully identify what "in use" means:
> 
> 	 An NO_MODIFICATION_ALLOWED_ERR exception must be thrown if the AudioBufferChannel is currently is use by a live AudioNode.
> 
> I missed the import of this statement at first. Now I see that set() confers a sort of temporary immutability on the AudioBuffer. This is a very significant aspect of your proposal (it originally contained the blanket statement "AudioBuffers are immutable", which this behavior descends from as I see it).

Thanks for the feedback. Ill highlight that behavior and clarify the conditions under which set() will throw.

-Jer
Received on Tuesday, 30 July 2013 17:26:50 UTC

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