- From: Paul Adenot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Mar 2023 13:09:42 +0000
- To: public-webrtc-logs@w3.org
What other use case is there, playing out on an `HTMLMediaElement` with an `srcObject` ? This is pretty niche, there's no way to perform anything as simple as a mix-down of two remote peers, except by using a bunch of `HTLMMediaElement` and let the OS do the mix-down, which makes this API really awkward, because you have to inspect all the stats for each object, instead of one. It can also be really inefficient (depending on the implementation and platform). I think we should remove this, having statistics about output is the responsibility of the objects responsible for rendering, and the `AudioContext` already provide what's needed, and more. Introducing coupling here is not something that is desirable. Also, the terminology is incorrect and inconsistent with the rest of the Web Platform and audio programming generally. This API isn't capable of representing all use-case, niche or not (which is not a strong argument anyway, we can't assume use-cases as API designers, it just needs to work), not flexible enough for authors to understand quality in common scenario, as previously said. Authors that want to understand quality of the rendering will ask the rendering object if the rendering is going well, it's simpler to do and better in every aspect. -- GitHub Notification of comment by padenot Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/742#issuecomment-1460131905 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 March 2023 13:09:44 UTC