W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2011

[whatwg] HTML5 video: frame accuracy / SMPTE

From: Eric Carlson <eric.carlson@apple.com>
Date: Wed, 12 Jan 2011 05:32:58 -0800
Message-ID: <820ABCF9-AFF4-46EE-B110-E4CE01574430@apple.com>

On Jan 12, 2011, at 12:42 AM, Philip J?genstedt wrote:

> On Wed, 12 Jan 2011 09:16:59 +0100, Glenn Maynard <glenn at zewt.org> wrote:
>> On Wed, Jan 12, 2011 at 2:49 AM, Philip J?genstedt <philipj at opera.com> wrote:
>>> (Also, it might be useful to be able to chose whether seeking should be fast
>>> or exact, as frame-accurate seeking is hardly necessary in most normal
>>> playback situations.)
>> In an audio engine I worked on I had a seek hint like that, to
>> indicate whether the priority was accuracy or speed.  It matters even
>> more with video: when seeking with a seek bar, you may want to snap to
>> keyframes, whereas bookmarks, "jump to chapter" features, etc. will
>> often want to jump precisely.  A fast seek option would be
>> particularly useful for files with infrequent keyframes.
> For the record, this is the solution I've been imagining:
> * add HTMLMediaElement.seek(t, [exact]), where exact defaults to false if missing
> * make setting HTMLMediaElement.currentTime be a non-exact seek, as that seems to be the most common case
  That is a very interesting idea!. Precise seeking in some video files can be quite slow, greater than a second is not unlikely on some devices. FWIW, the media playback framework on iOS has a seek method with parameters for the tolerance allowed before and after the seek time [1] to allow the programmer to choose.


[1] http://developer.apple.com/library/ios/#documentation/AVFoundation/Reference/AVPlayer_Class/Reference/Reference.html%23//apple_ref/occ/instm/AVPlayer/seekToTime:toleranceBefore:toleranceAfter:
Received on Wednesday, 12 January 2011 05:32:58 UTC

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