- From: Andreas Pehrson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Sep 2019 08:56:02 +0000
- To: public-webrtc-logs@w3.org
> @jan-ivar > > > Also, with `replaceTrack` there's inherently no way to add additional tracks to a recording, whereas with `replaceStream` you'd be forgiven for not knowing that this limitation exists (it's in the prose). > > If gather the statement context correctly, yes there is. I think with "Add additional tracks" he means going from recording two tracks to three, or from 20 to 25, or the like. That would seem possible from just looking at the `replaceStream` API, even though it's not. > The original issue proposing using the same or similar language to WebRTC `RTCRtpSender.replaceTrack()`. Ideally, neither a track not currently having data, nor the source `<video>` pausing, nor the track or `MediaStreamTrack` ending should be the cause of `MediaRecorder` stopping. `#000000` video frames and audio silence can be recorded by default until the user explicitly executes `stop()`. The spec says to end the recording when all tracks have ended. Changing that would break existing applications that depend on this feature so it's not really an option. -- GitHub Notification of comment by Pehrsons Please view or discuss this issue at https://github.com/w3c/mediacapture-record/pull/186#issuecomment-532128379 using your GitHub account
Received on Tuesday, 17 September 2019 08:56:03 UTC