W3C home > Mailing lists > Public > public-html-media@w3.org > January 2013

[Bug 20714] New: timestampOffset in live case

From: <bugzilla@jessica.w3.org>
Date: Sun, 20 Jan 2013 16:32:10 +0000
To: public-html-media@w3.org
Message-ID: <bug-20714-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20714

            Bug ID: 20714
           Summary: timestampOffset in live case
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: cyril.concolato@telecom-paristech.fr
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

When joining a live session, the timestamp of the first coded frame received is
typically not zero. To have proper playback (not have the player stall), the
web apps needs to set the timestampOffset attribute of the SourceBuffer. In
some cases, such as using MPEG-DASH, an approximate timestamp might be provided
in the manifest. However, in many cases, the web app will have to parse the
media data in JavaScript, which is not optimal. It would be preferable to be
able to force an automatic offset, or to set/force the timestamp to zero.
Alternatively, it could be interesting to have a method to ask the media engine
to parse and return the timestamp range of some data, so that the app can then
transfer the data to the sourcebuffer with the right timestampOffset.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Sunday, 20 January 2013 16:32:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 January 2013 16:32:11 GMT