- From: ilnik via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jun 2019 07:59:52 +0000
- To: public-webrtc-logs@w3.org
@vr000m, This could help to detect glitches but this metric must be tuned first. It also should depend on a frame-rate, because 200ms inter-frame delay for 5 fps video is great, yet of 30fps it's terrible. Then the problem arises - the actual frame-rate may be anything other than configured value, because e.g. a capturer is being too slow. So now the threshold value should depend on the measured frame-rate. I think just a maximum inter-frame delay or a list of all delays (<60 of values) is much easier to interpret. The user of the metric may then compute whatever they may need. Also, non-filtered value is useful to see if the video is indeed the intended 30fps or not. -- GitHub Notification of comment by ilyanikolaevskiy Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/443#issuecomment-502576494 using your GitHub account
Received on Monday, 17 June 2019 07:59:58 UTC