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

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

--- Comment #3 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.

Here is text in the DASH section [1] subsections 3 and 4 to clarify that the
track attributes should first be sourced from data in the media container. If
they cannot be sourced from the media container then they should be sourced
from the MPD. This makes the UA behavior consistent with MSE.

This same clarification is being proposed in the MPEG DASH spec.

What do you think?

[1]
http://rawgit.com/boblund/HTMLSourcingInbandTracks/bug26718/index.html#mpegdash

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

Received on Thursday, 18 September 2014 19:41:55 UTC