TPEPlatform/MediaRecorder

Summary

We already have mozCamera for take photo or video recording. mozCamera itself is not part of any standard web spec, which means

1. It works on Firefox platform only.
2. Totally isolate in media world. There is no way to connect data stream from mozCamera with media processing module, such as WebAudio, or recording module, such as MediaRecorder.

MediaRecorder takes media stream, which may come from web audio or media source or user media, as input. User may process all these media streams before recording. In mozCamera, there is nothing that user can do between capturerer and recorder, except canned video effect.

To totally replace mozCamera, we need to support these three WebAPI

1. MediaRecorder: replace video recording function in mozCameraControl
2. ImageCapture: replace takePhoto function in mozCameraControl
3. CameraControl: except the first two function, we still need an API to control camera for 3A/ Zoom/ etc..

On B2G, there are two strategies

1. B2G 1.3 on JerryBean: Base on JB::MediaCodec, we will support OmxVideoTrackEncoder and OmxAudioTrackEncoder to leverage HW encoder.
2. B2G 1.3 on ICS: in this case, we still use VP8 and WebM.

Tracking Issues

META bugs for Encoding framework:

Main tracking issues

Testing Plan

1. Jason Smith: https://etherpad.mozilla.org/media-recording-testing

Schedule

Reference

• Meeting Minutes
• Mail thread
  • https://groups.google.com/forum/#!topic/mozilla.dev.media/y-KoshuUR44
• GetUserMedia Spec
• MediaStream Recording Spec
• Image Capture Spec
• HTML media capture (only supports simple capture functionalities), associated bug bug 741393
• Android JB encoder matrix
• iOS encorder matrix
• Firefox playback format
• VP9 Goolge I/O event
• Why VP8 should be that codec? (rtcweb-vp8-01)
• H.264 as Mandatory to Implement Video Codec for WebRTC
• H.264/AVC as Mandatory-to-Implement Video Codec for RTCweb