This specification defines a [[[MEDIA-SOURCE]]] [[MEDIA-SOURCE]] byte stream format specification based on the ISO Base Media File Format [[ISOBMFF]].
The working group maintains a list of all bug reports that the editors have not yet tried to address; there may also be related open bugs in the GitHub repository of the [[[MEDIA-SOURCE]]] specification.
This specification defines segment formats for implementations of [[[MEDIA-SOURCE]]] [[MEDIA-SOURCE]] that choose to support the ISO Base Media File Format [[ISOBMFF]].
It defines the MIME-type parameters used to signal codecs, and provides the necessary format specific definitions for [=initialization segments=], [=media segments=], and [=random access points=] required by the Byte Stream Formats section of the [[[MEDIA-SOURCE]]] specification.
This section specifies the parameters that can be used in the MIME-type passed to {{MediaSource/isTypeSupported()}} or {{MediaSource/addSourceBuffer()}}.
MIME-types for this specification MUST conform to the rules outlined for "audio/mp4" and "video/mp4" in [[RFC6381]].
An ISO BMFF [=initialization segment=] is defined in this specification as a single File Type Box (ftyp) followed by a single Movie Box (moov).
The user agent MUST run the [=append error=] algorithm if any of the following conditions are met:
The user agent MUST support setting the offset from media composition time to movie presentation time by handling an Edit Box (edts) containing a single Edit List Box (elst) that contains a single edit with media rate one. This edit MAY have a duration of 0 (indicating that it spans all subsequent media) or MAY have a non-zero duration (indicating the total duration of the movie including fragments).
The user agent MUST support codec configurations stored out-of-band in the sample entry, and for codecs which allow codec configurations stored inband in the samples themselves, the user agent SHOULD support codec configurations stored inband.
For example, for codecs which include SPS and PPS parameter sets, for maximum content interoperability, user agents are strongly advised to support both inband (e.g., as defined for avc3/avc4) and out-of-band (e.g., as defined for avc1/2) storage of the SPS and PPS.
Valid top-level boxes such as pdin, free, and sidx are allowed to appear before the moov box. These boxes MUST be accepted and ignored by the user agent and are not considered part of the [=initialization segment=] in this specification.
The user agent MUST source attribute values for `id`, `kind`, `label` and `language` for {{AudioTrack}}, {{VideoTrack}} and {{TextTrack}} objects as described for MPEG-4 ISOBMFF in the in-band tracks spec [[INBANDTRACKS]].
An ISO BMFF [=media segment=] is defined in this specification as one optional Segment Type Box (styp) followed by a single Movie Fragment Box (moof) followed by one or more Media Data Boxes (mdat). If the Segment Type Box is not present, the segment MUST conform to the brands listed in the File Type Box (ftyp) in the [=initialization segment=].
Valid top-level boxes defined in [[ISOBMFF]] other than ftyp, moov, styp, moof, and mdat are allowed to appear between the end of an [=initialization segment=] or [=media segment=] and before the beginning of a new [=media segment=]. These boxes MUST be accepted and ignored by the user agent and are not considered part of the [=media segment=] in this specification.
The user agent MUST run the [=append error=] algorithm if any of the following conditions are met:
A Movie Fragment Box uses movie-fragment relative addressing when the first Track Fragment Run(trun) box in each Track Fragment Box has the data-offset-present flag set and either of the following conditions are met:
This implies that the base-data-offset-present flag is not set.
A [=random access point=] as defined in this specification corresponds to a Stream Access Point of type 1 or 2 as defined in Annex I of [[ISOBMFF]].