W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23169] reconsider the jitter video quality metrics again

From: <bugzilla@jessica.w3.org>
Date: Tue, 08 Oct 2013 15:30:01 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23169-2486-Ahrh3styDf@http.www.w3.org/Bugs/Public/>

--- Comment #4 from Mark Watson <watsonm@netflix.com> ---

What you describe assumes an implementation which drops late frames except the
first. That's one possible implementation. What I understand is that there are
other implementations where there could be a run of late frames.

Specifically, I believe there are implementations where frames are accompanied
through the pipeline not by their absolute rendering time but by the
inter-frame interval. In such an implementation there can be an accumulating
mis-alignment between the correct and actual rendering time. I believe in the
implementation in question such an accumulation is detected after some short
time - possibly multiple frames - and accounted for by eventually dropping

The totalFrameDelay was intended to enable detection of this condition by the
application before or in concert with dropped frames.

At a first look, it seems like a count of late frames would also suffice for
the same purpose. The count does not distinguish between a frame that is a
little bit late and a frame that is a lot late. Conversely, the totalFrameDelay
does not distinguish between a number of frames that are each slightly late and
a single frame which is very late. I assume we do not ever expect an individual
frame to be very late (like 10s of frame intervals), so neither of these is a
problem and we could choose based on implementation complexity / complexity of
definition. The latter favors the late frame count.

I will also check with our implementors.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 8 October 2013 15:30:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:44 UTC