W3C home > Mailing lists > Public > public-html-media@w3.org > September 2012

[Bug 18933] New: Segment byte boundaries are not defined

From: <bugzilla@jessica.w3.org>
Date: Thu, 20 Sep 2012 12:37:03 +0000
To: public-html-media@w3.org
Message-ID: <bug-18933-5436@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18933

           Summary: Segment byte boundaries are not defined
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
        AssignedTo: adrianba@microsoft.com
        ReportedBy: haakon.riiser@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org


As far as I can tell, the MSE spec is not clear on how to determine where a
segment ends. Since append() does not necessarily deliver complete segments, we
need to be able to determine the size in bytes of both init and media segments
based on the data provided by append().

With ISO BMFF, we currently assume that the last byte in an init segment is the
last byte in the moov box, implying that an init segment will never have any
other top-level boxes after the moov box.

For media segments, we assume that the last bytes is the last byte in the
segment's last mdat box (we expect that the segment contains exactly as many
mdat boxes as there are traf boxes inside the segment's moof box, one for each
track). 

Since this is just guesswork, I think the spec should explicitly state how to
determine init and media segment boundaries, for all possible container
formats.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 20 September 2012 12:37:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2012 12:37:06 GMT