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: Thu, 26 Sep 2019 12:31:32 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-535480592-1569501092-sysbot+gh@w3.org>
I suppose the application could ensure the track has already received frames before starting to record (according to spec the track should be muted before the first frame, which means you can listen to onunmute, but Chrome is implemented to fire onunmute even if we have not received RTP packets yet - that's a bug), in which case we can pick the codec synchronously because the track could know which codec is used. But if you start recording prior to having frames, black frames would be recorded with an arbitrary codec, and possibly force re-encoding.

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/139#issuecomment-535480592 using your GitHub account
Received on Thursday, 26 September 2019 12:31:34 UTC

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