-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Seeking broken for some Blu-rays in v0.30.0 #7111
Comments
Feel free to anylyze this and write a patch. If it isn't too intrusive (or, generally, located within the BD/DVD-only code), it will be accepted. |
@wm4 I was aware of mpv dropping menu support but I thought that normal playback was still supported. Especially after you reverted part of the commit dropping some features. I wouldn't report it if it had never worked but I found the culprit by bisecting the code so I thought it was worth sharing. I'm afraid I don't know enough C to fix this myself. @CounterPillow I have updated the report to follow the template. |
Normal playback support was recently "cut down" a bit to remove its influence on the mpv core. Point is, I don't want to maintain the DVD/BD stuff anymore, and I'll raze anything that stands in the way of changes in the core to the ground. |
@wwwamadeus: If possible, could you test #15882? I wasn't able to reproduce the issue you mentioned in the OP on git master so I don't know if it will help you out or not. |
mpv version and platform
Commit a9d83ea (or current git master) on Linux
Reproduction steps
mpv --start=10:00 --bluray-device /path/to/bluray/disc bluray://
Expected behavior
Seeks to 10:00.
Actual behavior
The timestamp increases but the audio and video are still that of the beginning of the disc.
Log file
With a9d83ea, chapters were broken but seeking still worked:
Since it has been partially reverted by 1c63869, seeking doesn't work with some discs:
Sample files
A lot of Blu-Rays are affected (not all) but I'm afraid I can't share one here. It's probably very easy to reproduce.
The text was updated successfully, but these errors were encountered: