RE: chunked IMSC1

I consider backwards compatibility to current segment coding standards to be a requirement. In that framework....

Other than the regions being constant over the segment duration just discussed?

Everything in <head> has to be constant.

<set> would have to predict future content to work.

I don't view the above as a real problem.  Live captioning today is already fundamentally constrained.

I'd be delighted if there was a solution that enabled full features that is also backwards compatible with current segment encoding.  But I don't see it, and I don't believe there is a requirement to support everything possible in IMSC1 today, much less TTML2.

 Mike

-----Original Message-----
From: Nigel Megitt <nigel.megitt@bbc.co.uk> 
Sent: Monday, March 21, 2022 9:37 AM
To: Michael Dolan <mike@dolan.tv>; Pierre-Anthony Lemieux <pal@sandflow.com>
Cc: Cyril Concolato <cconcolato@netflix.com>; Glenn Adams <glenn@skynav.com>; public-tt@w3.org
Subject: Re: chunked IMSC1

    There will necessarily be tradeoffs between LL live versus VoD scenarios; and full vocabulary or some subset.

It is not obvious to me why such tradeoffs will be necessary - can you explain more?

Received on Monday, 21 March 2022 16:53:28 UTC