Changes between Version 6 and Version 7 of 104hackathon/webrtc

Mar 23, 2019, 1:58:25 AM (9 months ago)



  • 104hackathon/webrtc

    v6 v7  
    3535One test, "KITE-Simulcast-Test", was specifically developed to test browser compliance. An app which sends simulcast to a special SFU based on meedoze, and receives back a given stream back depending on interaction with the UI is provided. It allows to test in loopback mode with a single browser (since simulcast is only sender side anyway), and all stream selection logic is made through UI button which makes it easily instrumented through KITE. The different simulcast features are not tested directly but indirectly (if I can select and receive a stream at a specific configuration it means the SFU receives them well and can differentiate them). The medooze simulcast loopback page, used by e.g. Apple for testing  is hosted here:
     37To test Janus, a couple of servers are available:
     38* (deployed in the NOC)
     39* (on my laptop)
     40The easier way to test simulcasting is the EchoTest, which will allow you to choose which layers to send back. A couple of query strings are available to enable simulcast and force a specific codec: simulcast=true will enable old-style simulcasting (SDP munging for Chrome and Safari, rid-based for Firefox), while simulcast2=true will enable the new rid-based simulcasting on Chrome M74 and M75; vcodec=X forces a specific codec (e.g., vcodec=h264). Here's a couple of examples:
     44The videoconferencing demo can be used as well: visit the videoroomtest.html page instead. The same query strings for simulcast apply; there's no changing the video codec though (defaults to VP8, we can add a new room for other codecs).
    3746We plan to extend and complete this document over the hackathon with each and every new tests the SFU vendors will propose, or modified browsers the browsers vendor will provide: