- From: Doreapp via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Jul 2021 06:28:06 +0000
- To: public-webrtc@w3.org
Doreapp has just created a new issue for https://github.com/w3c/webrtc-provisional-stats: == Add track metrics to JavaScript getStats function == The idea would be - without talking of standardization yet - to have the possibility to get those track metrics* using the **JavaScript WebRTC API**, through the `getStats()` function. *When I say *track metrics*, I mostly think about `freezeCount`, `totalFreezeDuration`, `pauseCount` and `totalPauseDuration` ______________ *My use case, and why I would need those statistics :* I am creating a live-streaming program using WebRTC that will provide a video from a remote drone (flying) to a distant client. Currently, I face several issues, including a lot of video freezes. While creating a tool to debug and understand the origin of the freezes (network congestion, drone's CPU...), I need a programmatic way to detect those freezes. I already am using `muted` state of a track and an FPS measurement using `webkitDecodedFrameCount` but both are slow and measure the *consequence* (video frames are stopped) rather than the *cause* (packet loss...). Therefore, I would love being able to include those track metrics in my debug workflow. Please view or discuss this issue at https://github.com/w3c/webrtc-provisional-stats/issues/21 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 July 2021 06:28:08 UTC