Bug 48054 - Implement startOffsetTime (after the new HTML5 media spec update)
: Implement startOffsetTime (after the new HTML5 media spec update)
Status: UNCONFIRMED
: WebKit
Media Elements
: 528+ (Nightly build)
: PC All
: P2 Normal
Assigned To:
: http://www.whatwg.org/specs/web-apps/...
:
:
:
  Show dependency treegraph
 
Reported: 2010-10-21 03:06 PST by
Modified: 2012-06-11 22:56 PST (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2010-10-21 03:06:35 PST
The HTML5 spec was updated a while ago, I couldn't find any bug tracking that so this is not connected to a master-bug for it.

Anyway, I'm pushing startOffsetTime because I need it for my webapp :-) You also need to fix your startTime, because now it doesn't conform to spec.


This was my original bug (use case) to the WHATWG and browsers:

I stream conferences using Ogg Theora+Vorbis using Icecast2. I have built a
site that shows the video and then automatically shows the slides (as PNG
files) as well. I use orbited (COMET) to have the server PUSH my «next»
presses on my keyboard.

The problem is that icecast does heavy buffering, and also the client, so
that while I switch the slides, the browser will go from slide 3 to 4 WAY
too early (from 10 second to 1 minute).

If I could get the timestamp OR time-since-started-sending/recording from
the ogg file in javascript, I'd be able to sync everything.

There are multiple way to sync this, may even an stream with the slide-data
INSIDE the ogg file, however, AFAIK there's also no way of getting out such
arbitrary streams.
------- Comment #1 From 2011-05-11 06:17:11 PST -------
Can this be confirmed?
------- Comment #2 From 2012-02-01 13:18:43 PST -------
BBC blog post regarding their implementation of this in Firefox:

http://www.bbc.co.uk/blogs/researchanddevelopment/2012/01/implementing-startoffsettime-f.shtml