Being able to use [active](https://w3c.github.io/webrtc-pc/#dom-rtcrtpencodingparameters-active) to turn on/off specific simulcast layers has been an oft requested feature from application developers, is in the [spec]() and is supported in Chrome. #### Workaround: set `maxBitrate: 1` (use at least 1 since 0 appears to be ignored). The downside of the workaround is it still signals the SFU that the browser tries to send data on that layer. 😕 Lack of support complicates [web compat](https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpEncodingParameters#Browser_compatibility) in the already complicated area of simulcast.
Bug 1676855 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Being able to use [active](https://w3c.github.io/webrtc-pc/#dom-rtcrtpencodingparameters-active) to turn on/off specific simulcast layers has been an oft requested feature from application developers, is in the [spec]() and is supported in Chrome. #### Workaround: * set `maxBitrate: 1` (use at least 1 since 0 appears to be ignored) * and `scaleResolutionDownBy: 240` for good measure (seems needed in [single-layer case](https://blog.mozilla.org/webrtc/fiddle-week-downscale-video-peerconnection/) at least). The downside of the workaround is it still signals the SFU that the browser tries to send data on that layer. 😕 Lack of support complicates [web compat](https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpEncodingParameters#Browser_compatibility) in the already complicated area of simulcast.