- From: <bugzilla@jessica.w3.org>
- Date: Wed, 07 Dec 2011 21:42:01 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14970 --- Comment #8 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> 2011-12-07 21:42:01 UTC --- This is going in the right direction. The idea of the metrics listed at http://wiki.whatwg.org/wiki/Video_Metrics#Proposal is to provide the measurements to calculate for each of the individual components what fraction of the media stream they were handling per unit time: The network component would report how many bytes of video it received and since when and how much of that time was waiting time. This allows calculating the bitrate at which the video is being received. The decoding component would report per video and audio track how many bytes it was given to decode and how many it was actually able to decode. The rendering component would report how many frames it was given from the decoder and how many of these it presented and how many had to be dropped because they were too late. I think these components are not UA specific, but generic. Also, these measures are not UA specific nor are they encoding format specific. There are two ways of approaching these measurements: you can measure from the start of video download, or you can measure over a certain time frame (e.g. 100ms). The latter gives a rate that can be plotted, but the earlier provides more accurate information that can be polled by JS at a resolution as required and the rate can be calculated from differences between polling. -- Configure bugmail: https://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 Wednesday, 7 December 2011 21:42:07 UTC