W3C home > Mailing lists > Public > public-html-media@w3.org > November 2014

[Bug 27242] New: Clarify how track buffer ranges are updated.

From: <bugzilla@jessica.w3.org>
Date: Tue, 04 Nov 2014 22:45:27 +0000
To: public-html-media@w3.org
Message-ID: <bug-27242-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27242

            Bug ID: 27242
           Summary: Clarify how track buffer ranges are updated.
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: acolwell@google.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

The track buffer ranges variable is currently underspecified especially when it
comes to content that contains B-frames. For example in a I P B B B coded frame
sequence where each coded frame has a duration of 1 second, one could argue
that if only the I and P coded frames were appended, the track buffer ranges
should be [0, 1) [4,5). Another interpretation of this situation is that track
buffered ranges should be [0,5) since the B-frames are technicaly optional and
decoding could proceed just fine through this region of the timeline even if
the B-frames were never appended.

Steps that explicitly update the track buffer ranges variable should be added
to the coded frame processing algorithm and the coded frame removal algorithm
to avoid this potential source of interoperability problems.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 4 November 2014 22:45:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:05 UTC