- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Aug 2019 23:01:48 +0000
- To: public-webrtc-logs@w3.org
@henbos Conceivably and programmatically there is more than one way to achieve the expected result for the use case of recording multiple tracks potentially having differing resolutions. Note, ideally, when the track change occurs, either via replaceStream or addTrack+removeTrack without `MediaRecorder` stopping, it should be specified that the `width` and `height` of the new video track be checked and set as the current encoded width and height (e.g., see https://bugs.chromium.org/p/chromium/issues/detail?id=972470; https://github.com/w3c/mediacapture-record/pull/172; https://bugs.chromium.org/p/webm/issues/detail?id=1642), not to automatically encode the new track frames as the initial input video track width and height, to avoid potential for confusion as to whether or not the replacement track pixel dimensions, resolution, width, height should be constrained to the initial track encoding parameters, which the encoding of the replacement video track should not, unless explicitly set as a constant width and height by the user. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/167#issuecomment-526392796 using your GitHub account
Received on Thursday, 29 August 2019 23:01:49 UTC