[Bug 21333] consequences of requirement in section 8 on initialisation segments

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

--- Comment #4 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to comment #0)
> Adverts are unlikely to have the same video and audio tracks as the main
> content item and may not have the same codec (particularly audio). Hence
> these restrictions would seem to force adverts to be handled as separate
> SourceBuffer objects from the main content items.

How would this work without using a different SourceBuffer? I don't think it's
common for media engines to be able to consume content of a different encoding
mid-stream. MSE only abstracts away the network layer (how data gets to the
media element).

> Is a (relatively) seamless transition between content from different
> SourceBuffers possible with MSE?

This might be an area where we need a proposal from you.

> Secondly all 3 organisations had lengthy and controversial debates last year
> about requirements for a common initialisation segment in DASH. It is
> understood that MPEG are defining new boxes to enable new initialisation
> data to be carried in-band. This language would seem to exclude the use of
> those new boxes and again would force the use of separate SourceBuffers. Is
> this correct?

The specific Byte Stream Format sections of the spec are informative and not
required to be supported. The idea is that if you want to support one of these
formats then you should do it in the way presented to promote interoperability.
If there are new formats created then these would need to be handled according
to the general requirements for byte stream formats at the start of that
section.

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

Received on Tuesday, 19 March 2013 14:40:32 UTC