W3C home > Mailing lists > Public > public-web-and-tv@w3.org > December 2011

Re: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur

From: Mark Watson <watsonm@netflix.com>
Date: Tue, 13 Dec 2011 04:56:20 +0000
To: "Mays, David" <David_Mays@Comcast.com>
CC: "public-web-and-tv@w3.org WG" <public-web-and-tv@w3.org>
Message-ID: <805CB141-14F0-4E67-B58E-67D344A7A387@netflix.com>

On Dec 12, 2011, at 10:12 AM, Mays, David wrote:


* AdaptationSetChanged - The media has entered a different period where
the set of Representations may differ.

This might be better called PeriodChanged.

I chose the name AdaptationSetChanged because the thing of interest is actually the fact that there is a different set of video quality levels now. The specific name PeriodChanged only makes sense within the narrow framework of DASH. I understand your point, and AdaptationSetChanged isn't perfect, but let's not bikeshed too much on the naming just yet; not until we've nailed down the use cases anyway. ;-)

Just on this point, there can be multiple AdaptationSets in one Period - for example for different media types or media that should not be automatically switched by the player (such as different languages).

The available adaptation sets should map to in-band tracks (AudioTracks and VideoTracks) in HTML5 and changes in the available tracks are exactly the topic of one of the open bugs to which I believe Ian Hickson was going to propose a solution.

...Mark
Received on Tuesday, 13 December 2011 04:56:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:44:06 UTC