-
-
Notifications
You must be signed in to change notification settings - Fork 981
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
Reuse transceivers to reduce signal size #462
Comments
WebRTC’s Unified Plan never actually removes transceivers from the connection, so they stick around in the session description. There’s no way to remove them. You can reuse transceivers with |
I thought about this some more - it'd be nice to automatically reuse transceivers when calling |
actually it does, this is called "m-line recycling" (and there have been spec changes recently). Implementations may vary though. |
@fippo How would we go about recycling m-lines? I can't seem to find a description of this. Do we set the transceiver's direction to |
This is something the browser would do when you call transceiver.stop() which marks the m-line in the SDP as inactive. - which isn't implemented in Chrome yet. If the problem is caused by using addTrack and removeTrack to start and stop media, using replaceTrack on the same sender might avoid the problem. |
Yep replace track with null and change the direction works
|
I noticed that the signals keep on growing as I add new streams. Seems like removed stream are still referenced in futur signals. After a fewe cycles of adding and removing a stream the signal grows to more than 100ko.
The text was updated successfully, but these errors were encountered: