- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2017 09:51:13 +0000
- To: public-webrtc-logs@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-stats: == Stat for how much time it takes to encode video == The non-standardized Chromium getStats contains the following stats: ``` // The average encode time in ms (video). ssrc.googAvgEncodeMs ssrc.googEncodeUsagePercent ``` These can be used to estimate "how fast the fan is spinning" and be used as an indicator that you might want to to lower capture resolution. Is this useful? Should we standardize it or something similar? Averages are discouraged, and time is typically expressed as double seconds. How about a `double totalEncodingTime` in RTCMediaStreamTrackStats that is the total time, in seconds, that has been spent on encoding video for that track? Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/150 using your GitHub account
Received on Wednesday, 1 February 2017 09:51:20 UTC