- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Aug 2021 10:20:11 +0000
- To: public-webrtc-logs@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-stats: == how to describe the relationship of codec and fec mechanisms == when using chrome to make a call on https://webrtc.github.io/samples/src/content/peerconnection/constraints/ the `inbound-rtp` codecId stat is pointing to RTCCodec_1_Inbound_96 which resolves to VP8. However, Chrome actually wraps this in RED (historically, see https://bugs.chromium.org/p/webrtc/issues/detail?id=1467) But this is impossible to detect using stats. What is the proper way to deal with this? Should the codecId point to video/RED which then has an underlying codecId? Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/610 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 August 2021 10:20:12 UTC