W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2012

[Bug 17094] Define segment formats for MPEG2-TS

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Jul 2012 23:02:08 +0000
Message-Id: <E1SmC6i-0001fK-Vb@jessica.w3.org>
To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17094

--- Comment #10 from Mark Watson <watsonm@netflix.com> 2012-07-03 23:02:07 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > When you say "compatible with HLS" do you mean
> > > (1) Any segments compatible with HLS will also be compatible with the
> > > requirements here, or
> > > (2) Segments compatible with the requirements here are also compatible with
> > > HLS, or
> > > (3) both of the above
> > > 
> > 
> > Ideally (3) if that is reasonable to do. If not then I'd prefer to fall back to
> > (2) so that existing content could be slightly modified to work with existing
> > clients and the Media Source Extensions.
> (2), with (3) happening nearly always.
> 
> The difference is that HLS does not disallow "bad practices" that makes
> switching problematic (e.g. starting a segment in the middle of a picture).

On indeed somewhere that does not have an I-Frame.

(2) is reasonable, but I think if we are not planning to *guarantee* (1) we
should be clear about that, even if you think that in practice a lot of
existing HLS content will work.

 In
> practice, I have never seen an encoder that does this.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 3 July 2012 23:02:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2012 23:02:10 GMT