-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VP9 seek problem #1823
Comments
The file you linked has only 1 video key frame (for 42 seconds of video...). The seek index contains only 1 entry pointing to the start of the file. Each audio frame is marked as key frame, though (like it should be). So what the demuxer does is this:
Seeking forward within a file always causes EOF, because it's a forward seek, and a forward seek won't use the same index entry as the previous seek, basically. (This is so that when doing a forward seek close to the end of a file, it will actually end playback, instead of jumping backwards.) This is probably strange, but I'm not sure if this can be avoided without breaking this and other things. All of this can be avoided by doing a precise seek. For example, you can do a single click on the OSC seek bar, or use |
Thanks for the explanation. From the user point of view: what if mpv will detect such cases (there are no other key frames but video hasn't reached the end yet) and fall back to precise seek? I don't know how hard it would be to implement though. Also, little documentation nit:
|
I adjusted the manpage. |
Hi. I have problem with default (non exact) seek in this VP9 video: http://a.pomf.se/ychsdg.webm (mirror: http://dump.bitcheese.net/files/evenaja/neko.webm)
When I press LEFT or RIGHT keys only audio position changes, video freezes till the end. Probably because there are too few keyframes in this video, but is that intended behavior? Exact seek with Shift+LEFT/Shift+RIGHT works as expected.
Video was encoded with:
I also have problems with similar short VP9 videos.
Software versions:
(latest git commits)
The text was updated successfully, but these errors were encountered: