Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTCMediaStreamTrack.stop() from RTCRtpReceiver #498

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

RTCMediaStreamTrack.stop() from RTCRtpReceiver #498

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

Comments

@robin-raymond
Copy link
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).

@aboba
Copy link
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants