Bug 48054 - Implement startOffsetTime (after the new HTML5 media spec update)
Summary: Implement startOffsetTime (after the new HTML5 media spec update)
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media Elements (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC All
: P2 Normal
Assignee: Nobody
URL: http://www.whatwg.org/specs/web-apps/...
Depends on:
Reported: 2010-10-21 03:06 PDT by Odin Hørthe Omdal
Modified: 2014-10-22 10:31 PDT (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Odin Hørthe Omdal 2010-10-21 03:06:35 PDT
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 Odin Hørthe Omdal 2011-05-11 06:17:11 PDT
Can this be confirmed?
Comment 2 Nicholas Shanks 2012-02-01 13:18:43 PST
BBC blog post regarding their implementation of this in Firefox: