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

[whatwg] HTML5 video: frame accuracy / SMPTE

From: Glenn Maynard <glenn@zewt.org>
Date: Fri, 21 Jan 2011 20:58:20 -0500
Message-ID: <AANLkTikOM58KYEGcVMN44OL1eqrZMDL5m_r_7TEdoDDU@mail.gmail.com>
Regarding whether to use "fast" or "accurate" seeks by default, it
seems like a balance between the frequency of use cases for each, the
likelihood of either default being wrong, principle of least surprise,
and consistency with other APIs.  Looking at various seek use cases:

Seek bars should use "fast", particularly for longer videos and videos
with keyframes spaced far apart.  Videos encoded to allow quick
seeking by using frequent keyframes, on the other hand, might use
"accurate" even for seek bars.

Chapter seeking should use "accurate".  If a chapter is at 1h45m12.2s,
a fast seek would end up seeking into the previous scene, or into the
middle of a fade-out.

User-specified seeks, like YouTube's "tm" URL parameter, should be
"accurate", for the same reason as chapters.

A "seek ahead by N seconds" button should use "accurate".

Even in the primary use case of a seek bar, it's not always wanted.

The consequences of using "fast" as the default, when people forget to
explicitly specify "accurate", seem worse than the other way around.
I recommend "accurate" as the default.

-- 
Glenn Maynard
Received on Friday, 21 January 2011 17:58:20 UTC

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