Zoom is interested in this as well - it is critical for us to understand where in our audio pipeline that frames have been dropped.
Would this be supported for audio tracks in all MediaStream contexts, or just the stream obtained via `getUserMedia`? In particular, I would love if we could also get these statistics for audio tracks on a stream obtained via WebAudio's `createMediaStreamDestination` (https://developer.mozilla.org/en-US/docs/Web/API/AudioContext/createMediaStreamDestination). On Wednesday, November 15, 2023 at 9:50:19 AM UTC-6 Michael Fröhlich wrote: > We (GoTo) would also be interested in have dropped frame counts as well as > input latency counts. Thanks for adding this. > > philipp...@googlemail.com schrieb am Mittwoch, 15. November 2023 um > 12:14:16 UTC+1: > >> [snip] >> >>> >>> >>> *Web developers*: Positive >>> >>> >>> Any links? >>> >>> >>> I don't have any links but I've been told that web developers have been >>> "asking for input latency metrics for years". >>> On behalf of Google, Google Meet web developers are asking for both >>> dropped frames ratio metrics and input latency metrics, so I am developing >>> these PRs together with the WebRTC audio experts who requested them. >>> >> >> I've asked my Microsoft Teams Web audio folks and they look forward to >> being able to measure capture glitches this way. >> Nobody likes audio glitches and I hope this will help reduce them and/or >> identifying devices which are more prone. >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ac519a57-c567-41ba-9d0a-54285016902cn%40chromium.org.
