- From: ilnik via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Feb 2018 12:02:27 +0000
- To: public-webrtc-logs@w3.org
@vr000m, I argue that we don't need to add them. The issue is that the metric is tied to the target bitrate/fps **at the time the frame was encoded**. That fps/bitrate value may be even different to the one, actual at the time getStats is called. Also, most sensible targetFrameRate added to rtcOutboundRtpStreamStats would be aggregated somehow (average value over the window maybe), so, again, it will in no way be tied to the hugeFramesSent. -- GitHub Notification of comment by ilyanikolaevskiy Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/331#issuecomment-367991312 using your GitHub account
Received on Friday, 23 February 2018 12:03:03 UTC