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

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 using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 13 December 2022 16:00:30 UTC