RTCMediaStreamTrack.stop() from RTCRtpReceiver #498

Closed
robin-raymond opened this Issue Apr 22, 2016 · 1 comment

Projects

None yet

2 participants

@robin-raymond
Contributor

What happens to a receiver if the receiver.mediaStreamTrack.stop() is called (and called on all clones)? Currently the receiver object is still alive but the track that it created is ended.

We don't describe any behaviours about this...

For that matter, the lifecycle of any cloned track to the original track isn't explicit (but leans to suggest they have independent lifecycles).

@robin-raymond robin-raymond added the 1.1 label Apr 22, 2016
@aboba aboba referenced this issue in w3c/webrtc-pc Apr 25, 2016
Closed

Calling RTCRtpReceiver.track.stop() #597

@aboba aboba removed the 1.1 label Apr 26, 2016
@aboba
Contributor
aboba commented May 4, 2016

Calling track.stop() is not reversible, so RtpReceiver cannot provide a renderable track after that. Calling RtpReceiver.stop() has that same effect but it also stops the decoder.

@aboba aboba added a commit that referenced this issue May 4, 2016
@aboba aboba RTCMediaStreamTrack.stop() from RTCRtpReceiver
Fix for Issue #498
da43991
@aboba aboba added the PR exists label May 4, 2016
@aboba aboba closed this Jun 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment