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.

Sign up for GitHub

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

Jump to bottom

sender.track.stop() should it mute the outgoing stream? #597

Closed
robin-raymond opened this issue Sep 9, 2016 · 2 comments
Closed

sender.track.stop() should it mute the outgoing stream? #597

robin-raymond opened this issue Sep 9, 2016 · 2 comments
Labels
1.0 compatibility issue PR exists

Comments

@robin-raymond
Copy link
Contributor

I think so...
@aboba
Copy link
Contributor

aboba commented Sep 28, 2016

Equivalent WebRTC 1.0 Issue: w3c/webrtc-pc#764

@aboba
Copy link
Contributor

aboba commented Oct 5, 2016

Conclusion from TPAC 2016: When a track is ended or track.muted is set to "true" the RtpSender sends a black frame (video) or silence (audio). See:
https://www.w3.org/2016/09/23-webrtc-minutes#item09

aboba added a commit that referenced this issue Oct 5, 2016
@aboba
Effect of sender.track "ended" or "muted"
a610ee9 
Fix for Issue #597
Associated WebRTC 1.0 Issue: w3c/webrtc-pc#764
Based on W3C WEBRTC WG TPAC 2016 minutes: https://www.w3.org/2016/09/23-webrtc-minutes#item09
@aboba aboba mentioned this issue Oct 5, 2016
Merged
@aboba aboba added the PR exists label Oct 5, 2016
@aboba aboba closed this as completed Oct 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.0 compatibility issue PR exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aboba @robin-raymond