-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
New test page with multiple mediastreams/transceivers [Unified plan] #1166
Comments
https://webrtc.github.io/samples/src/content/peerconnection/negotiate-timing/ uses multiple transceivers, you can select how many to negotiate. However it is not a very friendly demo, because the only purpose of it was to measure negotiation speed and whether or not glitches happen, it doesn't do anything with those transceivers, so it's not really illustrating receiving multiple streams etc. |
I think it would be worth making a test page for this, but I don't have time to do it any time soon. |
Unlikely to happen in a reasonable timeframe |
While I don't hear anyone volunteering, I did create a jsfiddle demo which could probably fairly easily be turned into a samples page |
Let's keep it open a while longer, that fiddle is an easy grab if anyone wants to contribute to samples |
Browser affected
71.0.3578.98 [Feature request]
Description
New test page with multiple mediastreams/transceivers [Unified plan]
Steps to reproduce
Create a test page alike https://webrtc.github.io/samples/src/content/peerconnection/pc1/ for multiple peers.
We can enable different plans Plan B/Unified plan for all of them.
Main motive is to test how does Chrome behave when we have multiple mediastreams/transceivers with Unified plan enabled.
Expected results
Not applicable as it is a new request
Actual results
Not applicable as it is a new request
The text was updated successfully, but these errors were encountered: