W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2017

Re: [webrtc-stats] jitterBufferDelay and concealed samples, DTX/CNG samples

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 26 Oct 2017 23:38:05 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-339830952-1509061084-sysbot+gh@w3.org>
A frame going out of the jitter buffer does not mean it is played out: there could be a decode error, it could get dropped due to missing playout, or other. This means we can't use "framesDecoded" for video, and we can't use "framesDecoded - framesDropped" because they could get dropped before the jitter buffer.

Should we just make the counters specific to coming out of the jitter buffer to avoid all these subtle bugs? "jitterBufferOutput - the number of samples/frames that have gone through the jitter buffer"?

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/246#issuecomment-339830952 using your GitHub account
Received on Thursday, 26 October 2017 23:38:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:14:56 UTC