W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2010

[whatwg] Timestamp from video source in order to sync (e.g. expose OGG timestamp to javascript)

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 18 May 2010 21:28:10 +1200
Message-ID: <AANLkTikPoce2Hh1dAqZbVNiC2qldtUqNE58sIfXs7yOZ@mail.gmail.com>
On Tue, May 18, 2010 at 8:23 PM, Odin Omdal H?rthe <odin.omdal at gmail.com>wrote:

> Justin Dolske's idea looks rather nice:
> > This seems like a somewhat unfortunate thing for the spec, I bet
> everyone's
> > going to get it wrong because it won't be common. :( I can't help but
> wonder if
> > it would be better to have a startTimeOffset property, so that
> .currentTime et
> > al are all still have a timeline starting from 0, and if you want the
> "real"
> > time you'd use .currentTime + .startTimeOffset.
> >
> > I'd also suspect we'll want the default video controls to normalize
> everything
> > to 0 (.currentTime - .startTime), since it would be really confusing
> otherwise.
>

That's exactly what I've advocated before. I lost the argument, but I forget
why, probably because I didn't understand the reasons.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100518/e6a9ed72/attachment.htm>
Received on Tuesday, 18 May 2010 02:28:10 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:23 UTC