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

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

--- Comment #8 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to comment #7)
> i propose removing the constraint that a SourceBuffer can't have its codecs
> or number/type of tracks change, and dispatch events to notify Javascript
> when transitions/track configuration changes are reached and automatically
> handled.  this can guarantee the most seamless transition possible on the
> platform, with simple Javascript and no time-critical JS execution required.

Since MSE attempts to abstract away the network tier from HTML Media Elements,
this suggestion seems equivalent to letting a data being progressively
downloaded for a <source> element change format mid-download. I'm not aware of
anyone building something like this. I don't think SourceBuffers should be
required to support multiple formats.

If you have multiple SourceBuffers then you need to switch tracks, but you have
this situation with HTML Media Elements already. It's not clear to me why the
problem of track switching is specific to MSE. Isn't this actually a HTML5
issue that could be required of any media element including those performing
progressive download over HTTP? As I suggested on the last call, this might be
something solved outside the scope of MSE.

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

Received on Tuesday, 26 March 2013 04:25:51 UTC