This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29008 - [MSE] Media Segment Header is not defined
Summary: [MSE] Media Segment Header is not defined
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Matt Wolenetz
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-30 18:17 UTC by Ralph Giles
Modified: 2015-10-16 01:18 UTC (History)
3 users (show)

See Also:


Attachments

Description Ralph Giles 2015-07-30 18:17:26 UTC
"If the input buffer does not contain a complete media segment header yet,"

In section 3.5.1, step 6.2, the spec refers to a "media segment header" but never defines this term. None of the Byte Stream Format drafts define it either.

I know it's supposed to be the moof box for mp4, but it's unclear how to implement this for other formats, especially those without second-level headers like mp3 and ADTS.

Is it possible to just remove this step, and clarify that the 'coded frame processing algorithm' should only run if there's enough segment data to determine that there is a decodeable frame?
Comment 1 Matt Wolenetz 2015-08-11 15:04:52 UTC
This is a great point.

In particular, I think this was meant to allow for incremental partial parsing of a large media segment, as you've indicated. For instance, a WebM cluster could be significantly large, and coded frames could be successfully parsed out of the beginning of a cluster without having the entire cluster appended.

Your suggested replacement text sounds reasonable to me; I'll make the change shortly, with review of co-editors.
Comment 2 Matt Wolenetz 2015-10-13 23:18:49 UTC
This bug has been migrated to the GitHub issue tracker. Please follow/update progress using the GitHub issue:
https://github.com/w3c/media-source/issues/30
Comment 3 Matt Wolenetz 2015-10-16 01:18:00 UTC
fyi (Though this bug is moved to https://github.com/w3c/media-source/issues/30, I'm double-posting here to include the original bug reporter on this update.)
Pull request is out for review at https://github.com/w3c/media-source/pull/32 for the