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

Re: [mediacapture-main] MediaStreamTrack frame rate: configured versus actual? (#826)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Wed, 12 Oct 2022 07:23:23 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1275707269-1665559401-sysbot+gh@w3.org>
RVFC is useful for render FPS of a tag. Capture FPS != render FPS != encoder FPS.
The track should be able to speak for itself, we shouldn't need to attach it to a video tag or attach it to a peer connection to try to measure what FPS is later in the pipeline in order to guesstimate what the camera is capturing at (which would be inaccurate if drops occur).

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/826#issuecomment-1275707269 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 October 2022 07:23:24 UTC

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