Fix playback of complex BluRay ISOs #6166
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bond-009
approved these changes
Jun 10, 2021
cvium
reviewed
Jun 10, 2021
Co-authored-by: Claus Vium <cvium@users.noreply.github.com>
cvium
approved these changes
Jun 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ffmpegis able to play some simple (BluRay) ISO disc images via thefile:protocol. Other, more complex discs, with multiple playlists, may causebluray.iso: Invalid data found when processing input. Using thebluray:protocol andffmpegcompiled withlibbluray, the disc will properly play the main playlist.To ensure that there's no regression with DVD playback. The
bluray:protocol will be used only forVideoType.BluRayorIsoType.BluRay. To have the ISO file tagged asIsoType.BluRay, the file has to be named as e.g.:NAME.bluray.isoChanges
bluray:protocol for ISO files tagged as BluRay disc.Issues
Fixes the issue described in #5617 (comment)