- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Jun 2023 08:16:54 +0000
- To: public-webrtc-logs@w3.org
Frames dropped prior to delivery to WebRTC, e.g. something in the camera pipeline, should be available by [the new track stats API](https://w3c.github.io/mediacapture-extensions/#the-mediatrackframestats-dictionary) (the shape and name of it is still up for debate) but ultimately the track should report its own frame rate. The new API is proposed on the MediaStreamTrack rather than on WebRTC because the consumer of the track may be something else than WebRTC. As for getStats, ideally the frame rate of "media-source" stats should match the output of the track if no frames are dropped by the capture pipeline. However there is currently a bug in the implementation of media-source stats where we report frame rate and resolution _after adaptation_, not _before adaptation_, so you're getting input to encoder rather than input to adaptation module. https://crbug.com/webrtc/13528 And lastly you have output from encoder. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/761#issuecomment-1571578581 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 June 2023 08:16:57 UTC