[Bug 26718] [InbandTracks] Container information vs. Manifest information

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26718

Bob Lund <b.lund@cablelabs.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |b.lund@cablelabs.com

--- Comment #1 from Bob Lund <b.lund@cablelabs.com> ---
(In reply to Cyril Concolato from comment #0)
> The specification defines "Mappings [...] for [MPEGDASH], [ISOBMFF],
> [MPEG2TS], [OGGSKELETON] and [WebM]. " Those standards are partially
> overlapping. For instance an MPEG-DASH manifest may be used to describe a
> streaming session made of ISOBMFF files or MPEG-2 TS files. Unfortunately,
> some information in the DASH Manifest may be redundant (or contradictory)
> with the information in the container file, for example the language. The
> specification should indicate how to resolve those conflicts. Ideally, the
> container file information should prevail, unless it's missing information;
> so that the playback of a file from a manifest or directly in the video
> element produce the same result.

As I understand from our recent email exchange on this very topic, the MPD
should really be viewed only as a hint and all the track attributes should be
sourced from the metadata in the container itself. For instance, there is
insufficient specification in DASH to correlate ContentComponent child
Descriptors, e.g. Role, with a specific media container track.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 2 September 2014 15:12:53 UTC