@@ -61,13 +61,11 @@ <h3>Demo details</h3>
61
61
you have a single stream with multiple layers, which makes it more efficient,
62
62
especially because it consumes much less bandwidth.</ p >
63
63
< p > Notice that this only works if the publishers joining the room will use a recent
64
- Chrome version that has been started either with the following flag:</ p >
65
- < p > < div class ="alert alert-info "> < code > --force-fieldtrials=WebRTC-SupportVP9SVC/EnabledByFlag_2SL3TL/</ code > </ div > </ p >
66
- < p > to configure VP9 SVC to only use two spatial layers, or:</ p >
67
- < p > < div class ="alert alert-info "> < code > --force-fieldtrials=WebRTC-SupportVP9SVC/EnabledByFlag_3SL3TL/</ code > </ div > </ p >
68
- < p > to test three spatial layers instead.
69
- If you join with a Chrome that doesn't have one of those options set, or with
70
- another browser, you'll be able to select a layer, but all request to set
64
+ browser that supports the < code > scalabilityMode</ code > property in < code > sendEncodings</ code > ,
65
+ e.g., recent Chrome versions (please refer to the
66
+ < a target ="_blank " href ="https://www.w3.org/TR/webrtc-svc/ "> SVC Extension for WebRTC</ a >
67
+ documentation for more details). If you join with a browser that doesn't support
68
+ those properties, or with you'll be able to select a layer, but all request to set
71
69
a custom layer on your video will fail, meaning you'll act as a plain VP9 client.
72
70
If you ask for a layer from a publisher that doesn't support VP9 SVC either,
73
71
then your request will be ignored as well.</ p >
0 commit comments