Re: [mediacapture-image] Clarify meaning of PTZ constraints presence (#256)

> Having to deal with the weird combos, is part of the extra complexity. Having to deal with a range that is the union of all floating point numbers, true and false, where true and false have specific meanings that are not translations to a floating-point range is probably going to be harder in terms of implementation than dealing with just the set of floating numbers or just {true,false}.

Agreed, this seems a recipe for bad interop.
I haven't seen any convincing use case for this level of expressiveness.
The only justification so far is that the current constraint model allows that but we know we already have bad interop there and I think this is one reason we haven't been able to to tighten the selection algorithm.

Let's take { video : { pan : 10, width : 1920 } } as an example with a 720p PTZ camera and a 1080p non PTZ camera. 
Which camera will be used? Say PTZ camera current pan value is 3600? or current pan value is 0?

We should drive the design with what the developer might want to express as part of the getUserMedia call and what the user might want to do in terms of selection.
The question we know of is: 'Give me a camera, with PTZ capabilities if possible'.
I think we can address that with a ptz boolean constraint and make it so that pan/tilt/zoom numerical constraints are considered for applyConstraints only.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/256#issuecomment-689435761 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 9 September 2020 09:11:12 UTC