[mediacapture-record] Support producing raw encoded bitstreams via MIMEType option

miguelao has just created a new issue for 
https://github.com/w3c/mediacapture-record:

== Support producing raw encoded bitstreams via MIMEType option ==
MIMETypes for the application(s) at hand are usually in the form 
`video/container;codecs="codec1,codec2"` (respectively, `audio`). This
 format describes a [series of] encoded bitstreams multiplexed into 
the `container` format, e.g. webm, mkv, or mp4. It'd be interesting 
(see #60) to provide ways for the application to request a 
non-multiplexed encoded bitstream. This would allow the application to
 provide more sophisticated container formats (e.g. with seeking). 

I propose allowing the MIMEType to specify the codec as MIME subtype 
to indicate requesting of a raw encoded format. This follows the 
widespread convention `video/mp4` versus `video/h264`, where the 
former implies a multiplexed MPEG4 stream where as the latter is a raw
 H264 encoded bitstream.

For the Chrome implementation, this would also translate, e.g. into 
accepting `video/vp8`, `video/vp9`, `audio/opus`. I wrote a [Chrome 
CL](https://codereview.chromium.org/2234563002/) coupled with a [demo 
page](https://rawgit.com/Miguelao/demos/master/mediarecorder_containerless.html)
 as a POC and seems to work, of course there are a few TBDs, but I'd 
like to ask if this is a correct direction, so WDYT, @foolip, 
@pehrsons, @uysalere, @martinthomson ?

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-record/issues/67 using your GitHub
 account

Received on Wednesday, 10 August 2016 00:45:20 UTC