Hector Martin

why I re-encoded it. but it's not an excuse for the modern software. there's so much computing power in this machine. it could easily make scrubbing responsive if it wanted to. (and some software can.) the people who made it just don't care enough.

It's not possible to make scrubbing universally responsive in h.264 except post facto by caching the hell out of everything. Keyframe intervals can be arbitrarily long and smooth scrubbing requires being able to decode one whole GOP per screen frame.

i've got 8gb of video memory and hundreds of milliseconds between clicking the mouse button down and moving the playhead. and even updating the player window every 100 milliseconds would be a huge improvement.

if you look at these old players they are actually doing all of these dirty tricks to make things responsive that you may be writing off in your head as not worth it.

Citation needed. Scrubbing is trivial when all your frames are I frames and requires no more memory or CPU than normally playing the video. It's literally zero extra code. That stops working when you introduce interframe compression.

the computer on the left is fast enough and has enough memory to store the entire video decoded as raw framebuffer in free video memory.

And if Chrome attempted to do that, then everyone would complain about how it's crashing their videogames while multitasking. Plus you'd have to cache aggressively to allow smooth seeking. And then it only works for HD videos up to 30 seconds which is what you can fit in there.

you only need as much as you are willing to make instantaneous for the user. even just 50 ms or whatever is good enough. better than the infinity milliseconds (until you stop moving mouse for 250ms) of the player on the left. you're imagining 100% ideal vs what's necessary