RE: MPEG2-TS activity in Bugzilla

Mark,
If I remember correctly, the complex discussions were mainly about adapting ISO-FF-based indexing to MPEG-2 TS needs. The solution was fairly simple.
Alex.


From: Mark Watson [mailto:watsonm@netflix.com]
Sent: Thursday, June 07, 2012 5:33 PM
To: Glenn Adams; Henri Sivonen; public-html WG
Subject: Re: MPEG2-TS activity in Bugzilla


On Jun 7, 2012, at 8:13 AM, Glenn Adams wrote:

What sort of use case, concretely, does "commercial video" mean in the
above sentence? (I have my guesses, but I'd rather not proceed to
discuss strawmen without confirming first.)

to elaborate, the requirement is based on legacy usage, and not related to distribution agreements


I've made the following point a few times in other contexts, so I will try and restrict myself to making it a single time here.

Existing MPEG2 Transport Stream content will generally need to be re-packaged for use with the Media Source extension (or other adaptive streaming solutions). Specifically, it will need to be segmented at appropriate boundaries and you will need to create appropriate Initialization Segments or ensure that the Media Segments themselves contain the necessary information to initialize playback.

In many cases re-encoding - to create the various bitrates in the first place from original source material - is required.

Given the above, it would simplify things for everyone if the re-packaging were done to a common format that is simpler and more appropriate for this application. Specifically the ISO Base Media File format (or equally, WebM if you were re-encoding anyway). I'd cite the extended and convoluted discussions that were necessary to specify MPEG2 TS for DASH compared to the relative simplicity of the ISO Base Media File approach as evidence this assertion.

Said another way, I'm not convinced there is a massive library of "legacy" MPEG2 TS content out there that just happens to be already suitable for adaptive streaming using the Media Source extension.

...Mark