W3C home > Mailing lists > Public > public-html-media@w3.org > July 2016

[media-source] Non-interoperable behavior regarding invalid ISOBMFF Init Segment

From: Cyril Concolato via GitHub <sysbot+gh@w3.org>
Date: Tue, 12 Jul 2016 12:44:14 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-165070904-1468327452-sysbot+gh@w3.org>
cconcolato has just created a new issue for 

== Non-interoperable behavior regarding invalid ISOBMFF Init Segment 
This issue is related to the ISOBMFF byte stream format. 

By mistake, I generated ISOBMFF init segment, missing the 'ftyp' box. 
Such content works fine in Chrome and Edge but does not in Safari and 
Firefox (See [Firefox 
Bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1283984#c22) for how
 Firefox processes such content).

Given that it works fine in some browsers and that also some 
standalone players work fine without the ftyp box (GPAC), I wonder if 
the byte stream format spec for ISOBMFF shouldn't be changed to permit
 the absence of the ftyp box. It could be assumed that an ftyp box 
with some default value is present, and the beginning of an init 
segment could be detected by either the ftyp box or the moov box. 

Please view or discuss this issue at 
https://github.com/w3c/media-source/issues/110 using your GitHub 
Received on Tuesday, 12 July 2016 12:44:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 12 July 2016 12:44:24 UTC