- From: Rob Manson <roBman@mob-labs.com>
- Date: Fri, 06 Sep 2013 01:51:24 +1000
- To: public-media-capture@w3.org
So is the recommendation that we should use the Media Recording Blob based API? stream -> media recorder -> blob -> file reader -> array buffer As compared to the current de-facto pipeline? stream -> <video> -> <canvas> -> image data -> array buffer And Image Capture? Giri has just published the latest version of that. roBman On 06/09/13 01:21, Harald Alvestrand wrote: > On 09/05/2013 07:37 AM, Rob Manson wrote: >> Hi Adam, >> >> that's true. But Transferable objects avoid the copy overhead so >> there is a real performance benefit in that. >> >> Unless I'm missing something? > That's actually only true for browsers using shared memory between > entities. > >> >> roBman >> >> >> On 05/09/13 15:14, Adam Bergkvist wrote: >>> On 2013-09-05 04:50, Rob Manson wrote: >>>> Also since I don't believe Blob's are Transferable[9] then choosing B >>>> has performance implications for processes that want to shift work off >>>> into a Web Worker too (see comment above about B's secondary pipeline). >>> >>> It's true that Blob's aren't Transferable (since they are immutable and >>> easy to share it doesn't add much), but you can send them as the first >>> (message) argument to postMessage() [1]. >>> >>> /Adam >>> >>> [1] http://dev.w3.org/html5/postmsg/#dom-window-postmessage >>> >> > > >
Received on Thursday, 5 September 2013 15:51:50 UTC