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

RE: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur

From: 이현재 <hj08.lee@lge.com>
Date: Tue, 13 Dec 2011 11:18:22 +0900
To: "'Clarke Stevens'" <C.Stevens@cablelabs.com>, <public-web-and-tv@w3.org>
Message-ID: <01af01ccb93d$7d0ba300$7722e900$@lee@lge.com>
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
tag.
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-----
From: 
Sent: 없음
To: Clarke Stevens; public-web-and-tv@w3.org
Subject: RE: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur

Hello,

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 subjective
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. An
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 a
future point.

Regards,
JanL 

-----Original Message-----
From: Clarke Stevens [mailto:C.Stevens@cablelabs.com] 
Sent: den 9 december 2011 20:01
To: public-web-and-tv@w3.org
Subject: [MEDIA_PIPELINE_TF] Adaptive Bit Rate Architectur

Please take a look at the Wiki page for Adaptive Bit Rate.

http://www.w3.org/2011/webtv/wiki/MPTF/ADR_Error_Codes

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 view
days. You can make suggested edits directly, or post your ideas to the
reflector.

Also, please make sure we are in agreement on the definitions of the
architectural models.

Thanks,
-Clarke
Received on Tuesday, 13 December 2011 02:18:55 UTC

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