- From: Cullen Jennings via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Aug 2017 19:02:35 +0000
- To: public-media-capture-logs@w3.org
I think this native mode things is pretty confusing and would try to avoid it will change on many devices. Most CMOS sensors support only a *single* native resolutions but multiple frame rate. Some have multiple native resolutions. This often feeds to a chip in the camera which may support many resolutions across USB bus even though none of them are the native of the sensor. This then goes to OS driver which may change the resolutions it exposes to browser. I think it gets very confusing what "native" would even mean or how a browser would mange it across multiple OS and different cameras. What a USB camera might report over typical USB profiles is very different than what would be known about a MIPI camera on a raspberry pi. A Firewire camera would be different again. I think it is reasonable to give the browsers latitude to do something reasonable as long as it gives an error if outside allowed constrain range and never creates fake data. -- GitHub Notification of comment by fluffy Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/466#issuecomment-321050942 using your GitHub account
Received on Tuesday, 8 August 2017 19:02:36 UTC