- From: Glenn Adams <glenn@skynav.com>
- Date: Tue, 15 Feb 2011 11:17:32 -0700
- To: Jean-Claude Dufourd <jean-claude.dufourd@telecom-paristech.fr>
- Cc: Richard Maunder <rmaunder@cisco.com>, public-web-and-tv@w3.org
- Message-ID: <AANLkTimbjOmwBxj_DzB0mrbOv_cDgxitT=CVyjs306RQ@mail.gmail.com>
Of course, there is some support for these functions already defined, e.g., via the following members of the HTMLMediaElement interface: - play() - pause() - currentTime - mutable, therefore supports seeking - playbackRate - mutable, therefore supports FWD and REW - volume - mutable - muted - mutable Subtitles can be referenced via timed text tracks, and the timedTrack.mode attribute can be mutated to enable/disable/hide. However, support is weak for discovering and controlling properties of multiple video/audio tracks, as well as control of other playback parameters (e.g., bitrate). Perhaps the MultiTrack Media proposal will improve this situation. In any case, these are not specifically related to DASH as such, and need to be fixed in general. G. On Tue, Feb 15, 2011 at 10:56 AM, Jean-Claude Dufourd < jean-claude.dufourd@telecom-paristech.fr> wrote: > There is no question of including DASH technology in HTML5, just means to > control DASHed media. > What some participants of the workshop defended was the inclusion of a way > to deal, within HTML5, with various options offered by DASH, such as choice > of bit-rate, audio, subtitles, as well as support for trick modes (a.k.a. > VCR-like controls). > One possible solution is to add element/attribute syntax around the video > object to allow that kind of control. Another solution is to add script > APIs. > Best regards > JC > > > On 15/2/11 18:38 , Glenn Adams wrote: > > Even if it were done today, I doubt very much they would reference it from > the HTML5 spec. There just isn't a strong reason to do so. Besides, they > have chosen a technology neutral position with respect to both stream media > formats and transports. > > Glenn Adams > > On Tue, Feb 15, 2011 at 8:56 AM, Richard Maunder <rmaunder@cisco.com>wrote: > >> Hi, >> >> Interesting session in Berlin last week, thanks to all involved. >> >> While we wait from the IG process & tools to form, I was interested in >> the implications of the HTML5 Last Call for May, especially the window for >> getting any DASH baseline or other adaptive streaming requirement into the >> spec: >> >> http://www.w3.org/2011/02/htmlwg-pr.html >> >> I'm not very familiar with the W3C processes, but my reading of them >> suggests it would be unlikely in this round if not in the spec by May? >> >> Any thoughts on this? >> >> Best wishes >> >> Richard >> >> Legal boilerplate follows..... >> Any views or opinions expressed are solely those of the author and do not >> necessarily represent those of Cisco. >> >> > > > -- > JC Dufourd > Directeur d'Etudes/Professor > Groupe Multimedia/Multimedia Group > Traitement du Signal et Images/Signal and Image Processing > Telecom ParisTech, 46 rue Barrault, 75 013 Paris, France > Tel: +33145817733 - Mob: +33677843843 - Fax: +33145817144 > >
Received on Tuesday, 15 February 2011 18:18:24 UTC