[Bug 12399] New: Expose statistics for media elements

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12399

           Summary: Expose statistics for media elements
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: silviapfeiffer1@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


For several reasons, we need to expose the performance of media elements to
JavaScript.

One concrete use case is that content publishers want to understand the quality
of their content as being played back by their users and how much a user is
actually playing back. For example, if a video always goes into buffering mode
after 1 min for all users - maybe there is a problem in the encoding, or the
video is too big for the typical bandwidth/CPU combination. Also, publishers
want to track the metrics of how much of their video and audio files is
actually being watched.

A further use case is HTTP adaptive streaming, where an author wants to
manually implement an algorithm for switching between different resources of
different bandwidth or screen size. For example, if the user goes full screen
and the user's machine and bandwidth allow for it, the author might want to
switch to a higher resolution video.

Note that recent discussions on issue-147 [1] at least included a need to
report on the actual playback rate achieved after trying to set it via
playbackRate.

Note also that Mozilla is implementing player metrics [2].


[1] http://lists.w3.org/Archives/Public/public-html/2011Mar/0699.html
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=580531

-- 
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 Wednesday, 30 March 2011 02:27:27 UTC