Closed
Bug 566375
Opened 15 years ago
Closed 15 years ago
Expose OGG timestamp to javascript (for video/slide sync)
Categories
(Core :: Audio/Video, enhancement)
Core
Audio/Video
Tracking
()
RESOLVED
DUPLICATE
of bug 498253
People
(Reporter: odin.omdal, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; nn-NO; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build Identifier:
It's only possible to get relative playtime with html5 in javascript. I want absolute timestamp that's embeded in OGG.
Here's the deal:
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 arbritary files.
Reproducible: Always
Updated•15 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Version: unspecified → Trunk
Comment 1•15 years ago
|
||
The HTML5 spec [http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html#dom-media-currenttime] actually requires the HTMLMediaElement.currentTime attribute to go from the start time of the media to the end time (as opposed to [0..duration]), we just haven't implemented it yet. This work is covered by bug 498253.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Comment 2•15 years ago
|
||
FWIW, there is a proof of concept patch for Kate streams, which can embed slide data inside Ogg, but this is left idle. If it picks up, events would likely be exposed to Javascript.
See https://bugzilla.mozilla.org/show_bug.cgi?id=481529.
You need to log in
before you can comment on or make changes to this bug.
Description
•