- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Jan 2023 17:55:01 +0000
- To: public-webrtc-logs@w3.org
while we are at it I have a long standing annoyance with the lack of being able to tell *why* fallback happened. WDYT about exposing what Chromium gathers [as reasons](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/peerconnection/rtc_video_decoder_fallback_recorder.h;l=15;bpv=1;bpt=1):
```
enum class RTCVideoDecoderFallbackReason {
kSpatialLayers = 0,
kConsecutivePendingBufferOverflow = 1,
kReinitializationFailed = 2,
kPreviousErrorOnDecode = 3,
kPreviousErrorOnRegisterCallback = 4,
kConsecutivePendingBufferOverflowDuringInit = 5,
kMaxValue = kConsecutivePendingBufferOverflowDuringInit,
};
```
UMA are hard to correlate with a particular encoder on the other end.
With the ability to restrict exposure this should be reasonably safe?
--
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/724#issuecomment-1397385025 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 January 2023 17:55:02 UTC