- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Sep 2020 15:24:09 +0000
- To: public-webrtc-logs@w3.org
> frame rate adaption can be rather expensive when it's not an integral frame-drop Agreed, the idea would be to go with something simple enough like integral frame-drop, which is what Safari does (maybe Chrome as well?). Also, even though the setting is 30fps, actual measurements might show that the real fps might be different though hopefully not too far. Idea here is to target good enough interoperability. > the spec has no default for this value, This seems like a common enough interop issue. Is there a way we could agree on an interoperable solution here? Can the spec mandate supporting both resizeMode values? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/723#issuecomment-690363858 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 15:24:11 UTC