- From: sole via GitHub <sysbot+gh@w3.org>
- Date: Tue, 31 May 2016 13:15:08 +0000
- To: public-media-capture@w3.org
sole has just created a new issue for https://github.com/w3c/mediacapture-record: == Provide a way to specify custom encoder (to generate other types of formats) == Right now `MediaRecorder` can only encode in whatever format the browser can. This is at odds with building any kind of application with reproducible and expectable results - running the same code in different browsers might in some cases generate webm and in some other cases, mp4. Some users might be able to take the encoded media and use it immediately elsewhere but some others won't be able to do that. Non tech savvy users are going to be put off by this. It would be great if instead of specifying the desired `mimeType` there was a way to provide the code for a custom encoder during `MediaRecorder` instantiation, and have the browser call that code periodically as it needs to encode more data. How the code would look like or work like, I don't know. Perhaps a worker? A `MediaRecorderWorker`? A `MediaRecorderEncoderWorker`? But this would be in line with the Extensible Web Manifesto, in which browsers expose low-ish level APIs that let users build more advanced use cases on top. Right now the MediaRecorder API falls slightly short in that side. This is the absolute **number one** feature that developers ask me about when I talk about `MediaRecorder`. Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/60 using your GitHub account
Received on Tuesday, 31 May 2016 13:15:15 UTC