W3C home > Mailing lists > Public > public-media-fragment@w3.org > August 2009

Fwd: [whatwg] Remove addCueRange/removeCueRanges

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Fri, 14 Aug 2009 10:32:23 +1000
Message-ID: <2c0e02830908131732j5d0bd9d9yc815b2cf335b17c9@mail.gmail.com>
To: Media Fragment <public-media-fragment@w3.org>
Hi all,

As you can see in the below email thread, in the WHATWG/HTML5
discussions, the need for temporal fragment addessing has been voiced
multiple times.

Can I suggest we do a concerted effort over the next few weeks to make
the temporal fragment specifications solid and have some demos that
show how they should work? This would be either using the existing
annodex technology, or a set of javascript libraries, or whatever
other approach we can use (ffmpeg?, gstreamer?) to make concrete
demos. Then we can encourage the browser vendors to actually implement
support for our addressing methods into the browsers. It would be a
break-through already if we only sorted out the time dimension!

I am concretely thinking here about:
* sorting out what the difference between the # and the ? approach
should be - use cases, protocol, user interface
* implement a demo using HTML5 video tag

This whole issue is getting urgent because HTML5 is going for a last
call in October. If we don't have anything sorted by then, it would be
a rather poor state of affairs for video on the Web.

Cheers,
Silvia.


---------- Forwarded message ----------
From: Philip Jägenstedt <philipj@opera.com>
Date: Thu, Aug 13, 2009 at 11:14 PM
Subject: Re: [whatwg] Remove addCueRange/removeCueRanges
To: "Dr. Markus Walther" <walther@svox.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>


On Thu, 13 Aug 2009 14:34:55 +0200, Dr. Markus Walther <walther@svox.com> wrote:

> Hi,
>
> please note that with cue ranges removed, the last HTML 5 method to
> perform audio subinterval selection is gone.
>
> AFAIK, when dropping support for 'start' and 'end' attributes it was
> noted on this list that cue ranges would provide a replacement to
> dynamically select, say, a 3-second range from a 1-hour audio source.
>
> So, if cue ranges will indeed be dropped, could browser vendors and
> standards people consider putting 'start' and 'end' back in, just like
> Safari had it for a while (albeit buggy)?

The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for. It
will be something like http://www.example.com/movie.mov#t=12.33,21.16

See http://www.w3.org/2008/01/media-fragments-wg.html and
http://www.w3.org/2008/WebVideo/Fragments/wiki/Syntax#Examples

> Actually, out of curiousity: could gapless concatenation of several
> audio objects be added as well, e.g.
>
> audioObject1.append(audioObject2)
>
> or even
>
> audioObject.join([audioObject1,audioObject2,...,audioObjectN)

There has been much discussion about audio "canvas" API:s and I trust
this could fit into that scope. View source at
http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#video
and search for "v2" and you'll find some of these ideas.

--
Philip Jägenstedt
Opera Software
Received on Friday, 14 August 2009 00:33:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:34 GMT