[Bug 22052] Report statistics on errored video frames

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22052

Aaron Colwell <acolwell@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |acolwell@google.com
           Assignee|adrianba@microsoft.com      |acolwell@google.com

--- Comment #3 from Aaron Colwell <acolwell@google.com> ---
I like Silvia's suggestion of using the word corrupt instead of errored.

How about this:

partial interface MediaPlaybackQuality {
   readonly    attribute unsigned long       corruptedVideoFrames;
}

This counter is incremented when a corrupted frame is detected. This may be pre
or post decode. Corrupted frames increment totalVideoFrames just like dropped
frames do. If the corrupted frame is not displayed then it increments the
droppedVideoFrames counter just like it would if the frame was not corrupted. 

I think keeping "dropped" and "corrupted" counters independent allow the
application to determine how exactly the corruption is affecting the user
experience. (ie lower frame rate vs. visible artifacts)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 28 May 2013 23:48:58 UTC