Bug 1230184 Comment 31 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
See bug 1863534 comment 3 for the members we actually expose, which is a subset of what's in our WebIDL and does NOT include rtx, fec, or srcc.

The `active` bit is a control surface allowing webapps to temporarily turn off individual simulcast layers to (encode and) send.

But also note Chrome's non-standard ["legacy SVC mode"](https://groups.google.com/g/discuss-webrtc/c/-QQ3pxrl-fw/m/5Rltd6H5AQAJ) in VP9/AV1, where the `active` bit instead controls SVC layers.
Revision 1 by
on 
See bug 1863534 comment 3 for the members we actually expose, which is a subset of what's in our WebIDL and does NOT include rtx, fec, or srcc.

The `active` bit is a control surface allowing webapps to temporarily turn off individual simulcast layers to (encode and) send, using setParameters.

But also note Chrome's non-standard ["legacy SVC mode"](https://groups.google.com/g/discuss-webrtc/c/-QQ3pxrl-fw/m/5Rltd6H5AQAJ) in VP9/AV1, where the `active` bit instead controls SVC layers.
Revision 2 by
on 
See bug 1863534 comment 3 for the members we actually expose, which is a subset of what's in our WebIDL and does NOT include rtx, fec, or srcc.

The `active` bit is a control surface allowing webapps to temporarily turn off individual simulcast layers to (encode and) send, using setParameters.

But also note Chrome's non-standard ["legacy SVC mode"](https://groups.google.com/g/discuss-webrtc/c/-QQ3pxrl-fw/m/5Rltd6H5AQAJ) in VP9/AV1, where the `active` bit instead controls SVC layers (because `encodings` themselves were abused to control SVC instead of simulcast).

Back to Bug 1230184 Comment 31