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

[webrtc-stats] jitterBufferDelay vs playoutDelay

From: Varun Singh via GitHub <sysbot+gh@w3.org>
Date: Wed, 07 Jun 2017 08:49:19 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-234136259-1496825357-sysbot+gh@w3.org>
vr000m has just created a new issue for https://github.com/w3c/webrtc-stats:

== jitterBufferDelay vs playoutDelay ==
In #217, we defined jitterBufferDelay based on the discussion in https://github.com/w3c/webrtc-stats/issues/151.

it currently defined as: 

 It is the total time each audio sample or video frame takes from the time it
is received to the time it is rendered. The delay is measured from the time
the first packet belonging to an audio/video frame enters the jitter buffer
to the time the complete frame is sent for rendering after decoding. The average 
jitter buffer delay can be calculated by dividing the <code>jitterBufferDelay</code>
with the <code>framesDecoded</code> (for video) or <code>totalSamplesReceived</code> (for audio).

There was some feedback on renaming this as `playoutDelay`. 

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/223 using your GitHub account
Received on Wednesday, 7 June 2017 08:49:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:39 UTC