[Webkit-unassigned] [Bug 52697] Frame accurate seeking isn't always accurate

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jan 19 22:57:35 PST 2011


https://bugs.webkit.org/show_bug.cgi?id=52697





--- Comment #13 from Jer Noble <jer.noble at apple.com>  2011-01-19 22:57:35 PST ---
(In reply to comment #11)
>  You likely have a bug in your secondsToTimecode function.

Indeed, it appears the correct calculation for "frames" in secondsToTimeCode() is the following:

var frames = Math.floor((time%1)*fps);

Because you're rounding your frames calculation to the nearest frame, you're off by a frame half the time.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list