At a typical GOP interval of 30, you need 30 times the CPU power required to decode a video normally for smooth scrubbing to arbitrary frames. GOPs can be even larger than that.
-
It likely has an index. Without access to the file it is hard to say, and it is not hard to make a file that will choke any player
The index isn't the issue, the keyframe interval is. QuickTime there is actually having to do dozens of times more work than regular decoding to do that. Chrome is either not making an attempt to do that (reasonable), or making an attempt but retrying every time the mouse moves.
-
-
Chrome is trying to be stateless so even with key frames you will have to do a binary search. VLC as well since it is optimized for streaming video and don't make assumptions about the underlying file
-
With VLC it's a bit hard to create optimal seeking since everything is plugins.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.