- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Mar 2019 09:03:48 +0000
- To: public-webrtc-logs@w3.org
The benefit of overconstrained over "just measure the output directly and react to it" is 1) you don't have to poll frequently, the browser would allow you to react on the very frame that overconstrained it, 2) you don't have to implement application logic for diagnosing whether or not a track is constrained and 3) it reuses the same logic and algorithms that was used to configure the track. Perhaps overconstrained should still exist but it should never mute the track, just set a "bool overconstrained" attribute. Applications that care can react, applications that don't won't. Otherwise you're forced not to use "min" and "max" when selecting your configuration/device or else you risk your track randomly getting muted, which would implicitly advice you to only use ideals. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/573#issuecomment-470856293 using your GitHub account
Received on Friday, 8 March 2019 09:03:49 UTC