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

[MEDIA_PIPELINE_TF] ISSUE-34: Adaptive Bit Rate Delivery

From: Igarashi, Tatsuya <Tatsuya.Igarashi@jp.sony.com>
Date: Thu, 28 Jul 2011 13:37:56 +0900
To: "public-web-and-tv@w3.org" <public-web-and-tv@w3.org>
Message-ID: <DAB1CC3FAB54D3438F667F8E7B7599A201E20CC6887D@JPTKYXMS218.jp.sony.com>
Hi Clarke,

In the last teleconference, I have tried to ask how to realize supporting a new adaptive bitrate delivery protocol not natively support.

By stretching my imagination on the following description of ISSUE-34, is your proposal to define a new format of adaptive streaming, such as Apple’s m3u and MPEG DASH MPD ? The answer to my question is that a JavaScript application converts from an arbitrary format which is not natively supported to the defined new format which is supported by the video element interface natively, is not it?

What needs to be standardized

1.      The user agent must be able to identify adaptive bit rate formats passed by the video element interface.

2.      The video element interface must support specification of maximum bit rate and other bit rate algorithm parameter specification.

3.      The video element interface needs to expose relevant adaptive bit rate delivery events and errors

4.      Streams of undefined length must be supported.

Thank you.

-***---***---***---***---***---***---***---***---***--***---***---***-
Tatsuya Igarashi (Tatsuya.Igarashi@jp.sony.com<mailto:Tatsuya.Igarashi@jp.sony.com>)
NS Development Dept. Technology Development Group
Sony Corporation
(Voice) +81-3-5435-3252 (Fax) +81-3-5435-3274
Received on Thursday, 28 July 2011 04:38:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 28 July 2011 04:38:30 GMT