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

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

--- Comment #13 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
(In reply to comment #12)
> I think we should stick with the existing restrictions for v1, get some
> implementation experience, and then see if it still makes sense to loosen
> the restrictions to allow this sort of stuff in.

I agree. We want something that is standalone and hits the key use cases.
Implementation experience will inform what we need to do next. This capability
isn't required to make MSE useful.

(In reply to comment #11)
> i think a very common use case will involve ads from ad providers that
> will be multiplexed video and english-only audio (and no captions),
> and primary content with separated video and audio, with audio in
> multiple languages, and caption tracks in multiple languages.  video
> engines would already have to support being reconfigured on the fly
> under Javascript control. having it be automatic solves the problem
> once properly, decreases complexity for the JS programmer, and
> improves the user experience.

If there are API design constraints that you think make it impossible to loosen
this later then I'd be interested in hearing concrete proposals to fix that. I
recommend closing this bug and having people pursue separate bugs for the
sub-issues as appropriate (as I suggested in comment #5).

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

Received on Tuesday, 26 March 2013 22:01:37 UTC