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.
-
-
the computer on the left is 500 times more powerful just in CPU than the computer on the right
1 reply 0 retweets 3 likes -
And h.264 is probably over 20 times more complex to decode than the older codec. Times 30 you're at 600. And nobody is putting exact seek into browser players because it's not going to work for HD video which multiplies the CPU usage again.
1 reply 0 retweets 5 likes -
i don't understand what the times 30 is here
1 reply 0 retweets 0 likes -
h.264 frames can depend on an infinite number of frames before them. A more common setting is 30. That means decoding frame 30 requires decoding frames 1-29 too. So you need 30 times the CPU power to decode any *random* arbitrary frame in the time it normally takes to decode one.
2 replies 0 retweets 8 likes -
Try encoding your video on the left with GOP size 1 and I bet it'll seek as smoothly as the video on the right.
1 reply 0 retweets 2 likes -
(It will also be much larger, but still smaller than the video on the right since h.264 is still going to be a better codec even in intra only mode)
2 replies 0 retweets 1 like -
ok but here's a non-defective video player doing it just fine despite you saying it's impossible (same video as on the left in my original) this is running on 8 year old hardware on mac os 10.12pic.twitter.com/GApgFA82Oe
5 replies 6 retweets 57 likes -
No idea what Quicktime is doing here, but I’d be impressed if it worked on typical HD content. Still, I don’t get what the point is necessarily. Even if h264 scrubbing could be “fixed,” it’s always going to be horridly inefficient. There’s better encodings for that...
3 replies 0 retweets 3 likes -
Replying to @let_mut_john @tumult and
...In a modern context, I’d imagine battery life/CPU usage is a much bigger concern than smooth scrubbing. I do think forward scrubbing should not be so bad, but I can’t blame anyone for not optimizing this case.
1 reply 0 retweets 1 like
I get about 5FPS doing random decodes on 1080p GOP 60 content on a 7 year old PC. On a video that small you could get decent scrubbing by just naively decoding as fast as you can from the previous keyframe on every mouse event. But it doesn't scale.
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.