- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Sep 2023 23:23:32 +0000
- To: public-webrtc-logs@w3.org
@anthmFS this issue will close with #971, so please open a new issue to keep discussing the 640x360 issue. But FWIW, the spec says about [`crop-and-scale`](https://w3c.github.io/mediacapture-main/#idl-def-VideoResizeModeEnum.right): _"This resolution is downscaled and/or cropped from a higher camera resolution by the [User Agent](https://pr-preview.s3.amazonaws.com/jan-ivar/mediacapture-main/pull/971.html#dfn-user-agent), ..."_ — which IMHO already allows any user agent to derive 640x360 from native resolutions higher than 640x480 to produce more desirable results. That's my reading [of](https://w3c.github.io/mediacapture-main/#dfn-selectsettings): _"For every possible [settings dictionary](https://w3c.github.io/mediacapture-main/#dfn-settings-dictionary) of [unconstrained copy of track] compute its [fitness distance](https://w3c.github.io/mediacapture-main/#dfn-fitness-distance)"_, which I think says fitness distance operates on the full set of settings the UA (not the camera) supports. cc @guidou -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/584#issuecomment-1728548157 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 September 2023 23:23:34 UTC