- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Oct 2020 07:59:42 +0000
- To: public-webrtc-logs@w3.org
Non-orthogonal constraints is why both getUserMedia() and applyConstraints() insist on entering all the constraints at once, rather than allowing you to set one parameter at a time; they featured heavily in the discussions about API shape (the most obvious non-orthogonal constraints are width, height and aspect ratio). The idea of device-generated presets - "this set of constraints will work well together" - is appealing, but of course it's a huge fingerprinting surface, which means that it can only be available after opening the device. WRT reopening: yes, drivers have to reopen for reconfiguration, and for some drivers/cameras, this is an expensive, slow and error-prone operation (which has been one of the major roadblocks to the bug of not turning the indicator light off when a camera only sources muted tracks). Still, I think we'll have to eat that cost at some point. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/739#issuecomment-715120739 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 October 2020 07:59:44 UTC