Re: memory footprint of AudioBuffer data copies

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. I’ll highlight that behavior and clarify the conditions under which set() will throw.

-Jer

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