On Wed, Nov 12, 2008 at 6:36 PM, Biju [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > toKeyFrame - optional, boolean, default false. if true indicates goto > the nearest keyframe of the value provided in secondsToSeek. > this is to improve performance while avoiding bug > https://bugzilla.mozilla.org/show_bug.cgi?id=463358
Good question. Should seeks go to the previous keyframe to the requested time, the next keyframe after the time, the closest keyframe, or the exact frame requested? Regarding that bug, I think it should be going to the last keyframe then decoding up to the point of the requested frame so it can display non-garbage data. But is there a requirement to be able to identify keyframes from JavaScript? I suspect not but don't know. > .seek() will return the time to which it is seek-ed to. What time is that exactly? Is that the time of the actual frame the seek ended on? Seek can take some time if it requires multiple http byte range requests to find the right location, and to search for the keyframe. You wouldn't want this to be a blocking call but it would need to be if you want to return the time. Chris. -- http://www.bluishcoder.co.nz
