- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Mar 2025 12:51:28 +0000
- To: public-webrtc@w3.org
henbos has just submitted a new pull request for https://github.com/w3c/webrtc-stats: == Add outbound-rtp.encodingIndex. == Fixes #801. Knowing which outbound-rtp maps to which encoding in the case of simulcast is necessary for analyzing stats, whether this is a pipeline or an external tool. Because the pipeline or tool is often separated from the rest of the app logic, this tool typically does not have access to make calls into other APIs like getParameters(), or even worse, SDP parsing (eek). Even if RID is known you can't sort on it so everyone who cares about order should want encodingIndex, e.g. tools who create graphs in encoding order. Example use cases: 1. The stats pipeline is part of the app but analysis happens after the call has ended. In order for the analysis to work it needs to know encodingIndex. If we don't provide it to them we're forcing getStats users to modify the RTCStatsReport before handoff - why force the app to jump through extra hoops without any benefit? 2. External tools like https://fippo.github.io/webrtc-dump-importer/ (basically external implementations of chrome://webrtc-internals/) just take a stats dump as input. They don't have any knowledge about RID-to-encoding mappings because they don't even know which app produced the stats dump. See https://github.com/w3c/webrtc-stats/pull/803 -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 March 2025 12:51:29 UTC