- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Feb 2023 07:55:18 +0000
- To: public-webrtc-logs@w3.org
My feeling was "yes, we want a go-to place to refer to about finding out whether or not we can expose stuff like this" but that there was no consensus on piggybacking on MC's powerEfficient for now, in particular there was a concern that this is exposing more information since current usage may influence availability. Other browser editors did say that they would find it convincing if we could create a demo for heuristically detecting SW fallback based on other metrics. I imagine we could add an experimental flag to force SW fallback after X number of frames and do a demo where we plot performance metrics. If we see a sharp decline, we might come up with a formula "if such and such goes down by such and such". But since this is being discussed in https://github.com/w3c/webcodecs/issues/604 already, I'd wait for @aboba for the next steps -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/732#issuecomment-1439573711 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 February 2023 07:55:20 UTC