- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Sep 2020 16:10:30 +0000
- To: public-webrtc-logs@w3.org
> Minimally, there needs to be a way to opt out. resizeMode is probably what you want as opt out, or opt in. Would you like the same for frame rate and if so what gain do you expect? How do you handle this in current browsers supporting frame rate decimation? > I have no objection to opting in to some sort of dynamic resize or frame interpolation For frame rate, we are not really talking about frame interpolation, more something like frame skipping. So you still get the exact output of the camera, except only part of it. > I think having an OverConstrained error is much better. getCapabilities does not tell what the native frame rate values are at the given resolution (since different native resolutions may lead to different native frame rates). I am not sure OverConstrained error is the best way to surface that information if it proves to be useful. OS APIs provide this information in a more straightforward manner. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/723#issuecomment-690419468 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 10 September 2020 16:10:35 UTC