Event for when stream is removed?
See original GitHub issueWe can call peer.removeStream()
, and this appears to work fine. I’m curious though if on the receiving end, the peer has some sort of event for when this happens? Or, is there some sort of event on the stream where we know that it’s totally done? (Or, is this just looping through tracks and removing them one-by-one under the hood, in which case we should use the removetrack
event on the MediaStream?)
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
RTCPeerConnection: removestream event - Web APIs | MDN
The obsolete removestream event was sent to an RTCPeerConnection to inform it that a MediaStream had been removed from the connection. You can ......
Read more >WebRTC: how to detect when a stream or track gets removed ...
On this happening, our receiver.track would be unmuted again and reinserted into the stream(s), firing the addtrack events on the stream(s).
Read more >Event streams - EventStoreDB Documentation
When you delete a stream, you can use either a soft delete or hard delete. When a stream is soft-deleted, all events from...
Read more >MediaStream: removetrack event - Web APIs
object has been removed from a MediaStream ... Event handler property, onremovetrack ... let stream = new MediaStream(); stream.onremovetrack = (event) ...
Read more >Stream | Node.js v19.3.0 Documentation
Once all currently buffered chunks are drained (accepted for delivery by the operating system), the 'drain' event will be emitted. Once write() returns...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing since the
mute
event is the spec-compliant way to detect track removal. We support this in simple-peer already.@kishorenc This used to work, but you’re right it’s not in the specification. It seems browsers have fixed this behaviour.
It looks like the
removetrack
event has also been removed from the spec. The new behaviour is to fire amute
event on the remote track.