- From: Evan Shrubsole via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Jan 2023 12:42:18 +0000
- To: public-webrtc-logs@w3.org
A counter could be useful, I think that one should be able to detect this using the `powerEfficient` metric; of the previous datapoint was `powerEfficient` and the following on is not then a software fallback could be considered. There are of course some issues with this, for example if the hardware decoder fails initially, or the flip-flop case as @fippo describes. The former case could be detected using media capabilities to check if a hardware decoder was expected to be used. The latter is probably a bug and would generate a lot of keyframes. -- GitHub Notification of comment by eshrubs Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/724#issuecomment-1380282222 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 January 2023 12:42:19 UTC