- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Oct 2022 09:33:27 +0000
- To: public-webrtc-logs@w3.org
Use case is diagnosing why we are not getting the FPS of the settings. - Are they never produced by the camera (actual less than setting, but no drops)? - Are they produced but dropped by the browser pipeline so they never reach their destination? Lastly you have potential frame drops at the destination, but I believe that is covered by other APIs. E.g. the destination could be an RTCPeerConnection (we have getStats) or it could be some application defined processing step. A processing step could know how many frames it received as input, but could not know if it did not receive more frames due to camera not producing them or due to them being dropped somewhere. We've seen several issues of browser buffer pools being exceeded and frames getting dropped which is very different than "the camera isn't producing any frames" -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/826#issuecomment-1271354198 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 October 2022 09:33:29 UTC