- From: Paul Adenot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 14:05:33 +0000
- To: public-webrtc@w3.org
padenot has just created a new issue for https://github.com/w3c/webrtc-stats: == Assorted comments on `RTCAudioPlayoutStats` == `playoutId` is frequently not implementable, there can be more than one playout path, or none, because a `MediaStreamTrack` can be sent to multiple `AudioContext` and/or `HTMLMediaElement` for rendering. There can also be thing that look like playout paths that are not, e.g., piping a inbound `MediaStreamTrack` to an `AudioContext` and just sending the data to an `AnalyzerNode` or an `AudioWorkletNode` to compute some metrics or simply record the output (e.g. using a Web Worker and Web Codecs, or whatever else). An `AudioContext` can also be connected to another `AudioContext`, that are on different devices. The actual output can be on the first, second or both. This is another case where `playoutId` cannot be implemented. All the other metrics are reimplementations of Web Audio API's [Audio Render Capacity](https://webaudio.github.io/web-audio-api/#audiorendercapacity) and latency metrics. Only application authors know the shape of their audio output path, and therefore they only can determine a quality metric, based on number provided by the object they actually use to render audio. Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/742 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 14:05:35 UTC