- From: <bugzilla@jessica.w3.org>
- Date: Sun, 17 Mar 2013 22:57:19 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21311 Robert O'Callahan (Mozilla) <roc@ocallahan.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roc@ocallahan.org --- Comment #2 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> --- (In reply to comment #1) > However, to speculate a bit, another approach for handling long renderings > is to direct the output to a MediaStreamRecorder which will hopefully in the > future allow extracting compressed formats as well. The whole point of MediaStreamRecorder is to support compression so I think that'll be supported as soon as MediaStreamRecorder is implemented. > This would allow the UA > take care of the render/compress cycle and block sizes, and the API would > just hand the developer a readily rendered blob to use however needed. I'm > not quite up to date on MediaStreamRecorder though, perhaps Roc knows more > about whether this is feasible or not. It's feasible but we need to specify how MediaStreamRecorder and OfflineAudioContext interact since currently MediaStreams are real-time-only. I think it's pretty important to have some mechanism whereby OfflineAudioContext can deliver data incrementally. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 17 March 2013 22:57:20 UTC