RE: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur

I'd like to propose a couple more use cases:
*       A developer or content provider would like to know metrics of a user's media experience, including time connected, trick modes used and at what times in the media, quality of the media at different times. (This use case is most important when adaptive streaming is multicast capable.)
*       An application developer would like to be notified by time-coded messages when the temporal reference within the media is corrupted and by how much, so as to enable re-sync of relatively timed components of the user experience external to the temporal reference source. This should include temporal offsets forced by use of trick modes by the user.


Q me

-----Original Message-----
From: Lewis, Jason []
Sent: Tuesday, December 13, 2011 2:45 AM
To: ???; 'Clarke Stevens';
Subject: Re: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur

Hi, in general I agree with the 3 architecture models as well.
For providing content, I think models 1 & 3 are most important:

Model 1:  Reporting & QoS mettrics are critical. When playing HLS in and
HTML5 player, we have no clear view of which bitrates are truly optimal.
Delivering to phones, tablets, and desktops across varying quality wifi or
3G networks can be like throwing darts blindfolded :)

Model 2: Nice to have, but the heuristics of selecting a bitrate based on
bandwidth & client decoding performance are pretty well understood.
Application developers shouldn't have to deal with this in order to
provide content to a customer.

Model 3: Dynamic client-side selection & appending of video segments (or
sources) is critical to present seamless video experiences to viewers.
Application developers capabilities on HTML5 generally lag behind in this

I've also added three new use cases related to these thoughts:

Thoughts?  Thanks, J
Jason Lewis
Disney Technology Solutions and Services

On 12/12/11 6:18 PM, "이현재" <> wrote:

>Hi Clarke,
>I think the 3 architecture models approach on adaptive streaming you
>proposed is very good.
>At first, rather full media control approach will be easy to discuss
>between companies for deciding what functionalities are needed for video
>The utmost goal is surely minimal control approach which video tag object
>will do agreed necessary functions automatically without application
>developers intervention.
>Let's hear content providers' and TV manufacturers' voice on what
>functionalities are necessary.
>Content providers and TV manufacturers, please speak up.
>Best regards,
>HJ / LG Electronics
>-----Original Message-----
>Sent: 없음
>To: Clarke Stevens;
>Subject: RE: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur
>I have a couple of questions on the proposal.
>1. segment definition
>Can a definition of segment be added to the proposal? It will help go over
>the below comments.
>2. maxLevel (input)
>What is the format of the input. Is it a segement identifier or bandwidth?
>If it is agreeable I would recommend to adopt concept of bandwidth that is
>mapped to the manifest bandwidth. Even though the bandwidth is a
>level based on what is reported in the manifest rather than actual it is
>the best form to indicate a max limit. An extra argument could also be
>included indicating what position that this max level should be applied.
>issue for implementers is that simply indicating max level may have
>different effects depending on how the buffer is handled. If this can be
>done at a future position it will make for a smoother transition.
>3. callback change in representation
>I am missing a callback reporting when the representation has changed. It
>might be what is called segment in the proposal but I am not sure. This
>callback is only reported when the "bandwidth" has changed. The "position"
>at which this change occurs should also be included since it may occur in
>future point.
>-----Original Message-----
>From: Clarke Stevens []
>Sent: den 9 december 2011 20:01
>Subject: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur
>Please take a look at the Wiki page for Adaptive Bit Rate.

>I'd like to have a good list of parameters, and errors (for model 1 in
>particular) that we can provide for MPTF folks to review over the next
>days. You can make suggested edits directly, or post your ideas to the
>Also, please make sure we are in agreement on the definitions of the
>architectural models.

Received on Thursday, 15 December 2011 15:51:37 UTC