- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Oct 2011 20:01:06 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12399 --- Comment #20 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-10-13 20:01:03 UTC --- Ah, that's an interesting use case not mentioned on the wiki. If what you're trying to determine is whether the decoding pipeline or the rendering pipeline are suffering, and if either, which one, then it seems like what you'd want is just two numbers: one, the rate of frames dropped by the decoder (which we can expose as two numbers, the number of frames passed to the decode and number of frames actually decoded), and two, the jitter. Why would you need the count of bytes decoded, the number of dropped frames (unless that's defined as dropped by the decoder, rather than by any part of the pipeline? — the wiki isn't clear on this), and the number of presented frames? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 13 October 2011 20:01:08 UTC