W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 23525] New: Require mvex in moov for ISO BMFF content

From: <bugzilla@jessica.w3.org>
Date: Tue, 15 Oct 2013 16:43:04 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-23525-2486@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23525

            Bug ID: 23525
           Summary: Require mvex in moov for ISO BMFF content
           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: jdsmith@microsoft.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

The current MSE draft returns an error if a Movie Extends (mvex) box is
contained in the Movie Header Box (mvhd), but doesn't explicitly state that an
mvex is required.  There are two issues with this:

1.  MSE should require an mvex box to indicate fragmented content and doesn't
now.  An mvex is not required in the base format documents, so it makes sense
for MSE to spec this.
2.  The base format specs don't allow an mvex in the Movie Header Box, so it's
not necessary for this to be explicitly listed in the MSE spec.

Changing the spec to require an mvex in the moov can address both issues.

Detail is to change the error condition in line 2 of 12.2.1 from:

2.  A Movie Extends (mvex) box is contained in the Movie Header Box to indicate
that Movie Fragments are to be expected.

To:

2.  A Movie Extends (mvex) box is not contained in the Movie (moov) box to
indicate that Movie Fragments are to be expected.

Section link: 
https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html#iso-init-segments

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 15 October 2013 16:43:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC