- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Jan 2017 11:04:26 +0000
- To: public-webrtc-logs@w3.org
The information about what's actually being sent seems to be available elsewhere. It seems to me that what makes sense here is the framerate that the track has been configured to try to achieve - that is, either the selected camera framerate or the framerate that the rate adapter in the video pipeline is configured to try to achieve. I think real framerate shouldn't ever go above this number, but may go below it for a number of reasons (CPU starvation, low light, congestion backpressure leading to dynamic reconfiguration...) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/141#issuecomment-275641412 using your GitHub account
Received on Friday, 27 January 2017 11:04:32 UTC