- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Sep 2022 07:45:32 +0000
- To: public-webrtc-logs@w3.org
MediaCapabilities tells you about capabilities and what you can expect, which is good for deciding which codec to use, but it does not tell you in actual fact if you're currently achieving HW. Trying to call MC with values obtained from RTCCodecStats is not good enough, that's guesswork. There are reasons why the two might not align. HW capabilities can be limited to a number of instances, so you may not get HW if multiple encoders or decoders are used. Decoding errors can and do cause SW fallback in real world scenarios. Or there may be other tradeoffs that the implementation does that results in HW or SW. MC also does not take FMTP parameters into account. This metric is still needed and people still abuse encoderImplementation/decoderImplementation despite MC having shipped. Shipping this metric is just exposing a readily available boolean, Evan already has a CL for it. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/666#issuecomment-1240350655 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 September 2022 07:45:33 UTC