- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Mar 2017 22:50:15 +0000
- To: public-media-capture-logs@w3.org
>All other OS platform APIs allow to specify POI / area separately. [UVC 1.5](https://tinyurl.com/image-capture) only allows for 1 Region of Interest (see Section 4.2.2.1.20), and the user can only switch the auto-settings on/off in it. This pretty much covers the whole Desktop world and iOS. In Android-land, in my experience the use of separate POIs for any of the 3A algorithms is marginal and just doesn't justify the hassle of extending this API, in other words, how often have you seen anyone configuring different POIs to be used for auto white balance and, say, AE & AF? The vast majority of camera apps wire the three together upon user tapping on the preview viewport (the user still has another layer of control via disabling any of the three "auto" settings). Moreover the support for several POIs in Android (e.g. [here](https://developer.android.com/reference/android/hardware/camera2/CaptureRequest.html#CONTROL_AE_REGIONS)) leaves plenty of latitude to the hardware as to how to implement several POIs / overlapping areas of interest, because the API contract is weak (and the OEMs protect their algorithms). If deemed interesting I could make a note/link in the Spec explaining all this. -- GitHub Notification of comment by miguelao Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/157#issuecomment-290250130 using your GitHub account
Received on Wednesday, 29 March 2017 22:50:21 UTC