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

Re: [MPTF] ADR_Min_Control and minBandwidth

From: Lewis, Jason <Jason.Lewis@disney.com>
Date: Fri, 16 Dec 2011 00:17:38 -0800
To: "Lewis, Jason" <Jason.Lewis@disney.com>
CC: Jan Lindquist <jan.lindquist@ericsson.com>, "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <0AA9015A-18AC-4376-BEC3-3B56D4EA3231@email.disney.com>
Ignore my second use case. I see that 'startingPlaybackHint(input)' made it into the proposal.

On Dec 16, 2011, at 12:09 AM, "Lewis, Jason" <Jason.Lewis@email.disney.com<mailto:Jason.Lewis@email.disney.com>> wrote:

I think minBandwidth should be kept.

It enables some valuable use cases.

It is useful to manage a single manifest file with bitrate representations across multiple devices (ie phone & tablet). The UA can be hinted to avoid the
lowest bitrates that may look acceptable on an phone, but are not on a tablet.

It could also provide the ability to set a target'starting' bitrate to optimize quality or startup time.
--Jason Lewis


On Dec 15, 2011, at 11:43 PM, "Jan Lindquist" <jan.lindquist@ericsson.com<mailto:jan.lindquist@ericsson.com>> wrote:

Hello,

To have a minimumBandwidth does not make sense from a control of the the stream perspective. If the stream is of type VBR there is going to be some very odd behaviour with increased quality levels at low bandwidth consuming portions of a stream. If comparing to what is described in Silverlight the max and min related to tracks which I interpret as the levels relating to the manifest. The support of maximumBandwidth is makes sense and should be kept but not minimumBandwidth.

Regards,
JanL

Received on Friday, 16 December 2011 08:20:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 16 December 2011 08:20:46 GMT