- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 May 2023 15:09:20 +0000
- To: public-webrtc-logs@w3.org
The source stats are the number of frames inputted to WebRTC and frames encoded are the number of frames outputted from the encoder, so in that sense you can calculate the number of frames that disappeared already. What exactly do you want to measure? What you can't tell is _why_ the encoder did not produce more frames, but I guess that would either be because of the adaptation logic purposefully dropping them or the encoder dropping them due to not wanting to overshoot the bitrate? Both of these would be considered adaptation in my opinion. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/761#issuecomment-1570421335 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 May 2023 15:09:22 UTC