- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Tue, 26 May 2009 21:19:22 +1200
On Tue, May 26, 2009 at 8:04 PM, Philip J?genstedt <philipj at opera.com>wrote: > On Tue, 26 May 2009 01:26:38 +0200, Robert O'Callahan < > robert at ocallahan.org> wrote: > > On Tue, May 26, 2009 at 11:25 AM, Robert O'Callahan <robert at ocallahan.org >> >wrote: >> >> I don't think there is a standard way to expose the frame rate. We might >>> even want something more general than the frame rate, since conceivably >>> you >>> could have a video format where the interval between frames is variable. >>> >>> >> It's more than conceivable, actually --- chained Oggs can have the frame >> rate varying between segments. So if you're at the last frame of one >> segment >> the time till the next frame can be different from the time since the >> previous frame. >> >> Rob >> > > Indeed, I don't suggest adding an API for exposing the frame rate, I'm just > saying that if you know the frame rate by some external means then you can > just set currentTime. > OK, sure. Since there are lots of situations where you don't know the frame rate via external means, it seems new API is needed here. 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/20090526/75a493d6/attachment-0001.htm>
Received on Tuesday, 26 May 2009 02:19:22 UTC