W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > September 2019

Re: [mediacapture-record] Does recording of remote a/v streams always imply re-encoding? (#139)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Fri, 13 Sep 2019 14:19:38 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-531255477-1568384376-sysbot+gh@w3.org>
My take: MediaRecorder specifies the codec with MediaRecorderOptions.mimeType. The input to the recorder is the frames of the MediaStreamTrack, the recorder is essentially a sink, responsible for encoding. The recorder should ideally not know or care (wrong abstraction layer) if the track originates from a camera, webrtc or something else.

That said - if an implementation want to take advantage of the fact that the recorder is of the same format as a WebRTC stream then it would be free to implement such optimization. But that would be a browser optimization feature, not a spec mandate.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/139#issuecomment-531255477 using your GitHub account
Received on Friday, 13 September 2019 14:19:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:28 UTC