- From: <bugzilla@jessica.w3.org>
- Date: Wed, 17 Oct 2012 12:28:29 +0000
- To: public-audio@w3.org
Received on Wednesday, 17 October 2012 12:28:30 UTC
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17389 --- Comment #2 from Srikumar Subramanian (Kumar) <srikumarks@gmail.com> --- I just realized that from a resource perspective, it might be much better for an offline audio context to provide periodic JS callbacks with buffers of a fixed duration rather than provide the whole render via a single oncomplete callback - sort of like a JS audio destination node. This will let us stream the rendered audio to a file using the local file system API instead of holding it all in memory, or send it to a WebRTC encode+transmit pipe. (I confess I haven't used the current prototype in webkit and therefore may have some misunderstandings.) -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 17 October 2012 12:28:30 UTC