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:24:55 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-535478312-1569500694-sysbot+gh@w3.org>
If the track is sourced from something that is based on an encoded stream, such as a remote WebRTC track, and we want to allow the User Agent avoid re-encoding the stream, then we have to wait for the first encoded frame to arrive before we know what codec is used, and as such we cannot synchronously update the mimeType attribute. We know this before firing "onstart" though.

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

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:48 UTC