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.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Hmm, you seem to be right. Consider me fooled, I thought it looked more granular than that at first.
Keep in mind that some videos have fixed GOPs so keyframes are at exact intervals, and some don't, so you can't necessarily tell just by looking for patterns in the timestamps you can seek to.
-
-
Hm. I can't seem to get frame-accurate scrubbing to work in MPV, *at all*. It already is extremely taxing and rather laggy on my Ryzen 3900X just to do keyframe scrubbing on a typical 4K YouTube video in MPV. When I specify --hr-sync=yes it's clearly still locked to keyframes...
-
You're right, I think --hr-seek=always only works for seeking (e.g. left/right keys), not for scrubbing with the UI... I'm not sure if there's a way to force the latter to use exact seeks.
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.