On Jul 31, 2013, at 6:51 PM, Srikumar Karaikudi Subramanian <srikumarks@gmail.com> wrote: > 1. In the "Memory and Performance Considerations" section, the text - > >> Generating audio directly into an AudioBuffer using the new set() method will still result in 0-additional allocations or copies. > > > is likely dated and ought to be removed? AudioBuffer doesn't have a set() method > Sorry that this still isn't clear. This should refer to AudioBufferChannel. > and the set() method on AudioBufferChannel does require a copy as per its description. You would also need to copy data into a Float32Array, so this referencing that using AudioBufferChannel.set() directly requires no additonal allocations or copies as compared to Float32Array.set(). -Jer
Received on Thursday, 1 August 2013 02:00:16 UTC