- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Sep 2020 08:09:02 +0000
- To: public-webrtc-logs@w3.org
> where `{}` has no impact on [fitness distance](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-fitness-distance), and may choose your 1080p camera over your low-res PTZ camera.
However we define constraints and distance, the user agent can select any of the devices in finalSet.
As per spec, the fitness distance MAY be used but user agent can use other sources.
Given PTZ is different in nature compared to other cameras in terms of permission, we could try to mandate that, in case the query asks for PTZ, UA is expected to prefer selecting PTZ devices first in finalSet.
> * Remove the `true` overload of `pan`, `tilt` and `zoom` constraints, and replace it with a `ptz` [ConstrainBoolean](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-constrainboolean).
That is my preference obviously. I would tend to leave 'pan', 'tilt' and 'zoom' to applyConstraints solely.
Then we could try getting consensus on whether an ideal deviceId constraint is above a PTZ constraint.
> * Hotfix the fitness distance algorithm to give weight to presence of constraints.
I do not see how this will guarantee to get what we want.
> * Make `true` a first-class value of `pan`, `tilt` and `zoom`, and specify a new `ConstrainULongOrBoolean`.
Isn't it investing in a model we know is too complex?
--
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/256#issuecomment-684538386 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 September 2020 08:09:04 UTC