W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2022

Re: [webrtc-stats] Clarify media-source frame rates (frames and framesPerSecond) (#708)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Tue, 13 Dec 2022 16:00:28 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1348884628-1670947226-sysbot+gh@w3.org>
Here's another edge case: Chrome has a feature where, to save on performance and bandwidth, screenshare tracks stop capturing new frames when the content is static. But to ensure good QP values and frames not getting lost, the enocoder will repeat frames.

My opinion is that any frame that gets input to the encoder is considered media-source frames, even if it includes repeated frames.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/708#issuecomment-1348884628 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 December 2022 16:00:30 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC