Hello!
I'm experiencing a problem I haven't encountered before, with a new King Crimson "Islands" Atmos Blu-ray disc.
While the disc (in a Buffalo drive) is physically connected to my Windows laptop, MakeMKV (2.0.0) is able to scan the disk, present all titles, and rip the titles to Matroska container files just fine.
However, when I use the Backup function to remove encryption and create a folder of the BD folder/file structure, MakeMKV is unable to open those files. When I point it at the index.bdmv file, it starts scanning the source and then stops responding, erroring to a "Fatal error occurred, program will now exit" popup. There is no useful information in the debug log file, just this:
003006:0000 Opening files on harddrive at file://C:/Users/tommy/Downloads/backup/KING_CRIMSON_ISLANDS
DISCID=36203454BFFA7B12F804B5FF9063520E0F9F8771
The backup of the BD completed without errors, and I've even tried two different BD drives and two different computers, all resulting in the same outcome.
I've even used DVDFab to both create a clone ISO, and file structure copy, and MakeMKV chokes on both of those in the exact same way. I also tried opening the file structure from the macOS version of MakeMKV on a Mac Mini, and it errors in the same way.
If MakeMKV can open the encrypted structure from the physical disk and process rips, but then can't do the same with the unencrypted structure...that makes no sense to me.
Any ideas on this weirdness?
MakeMKV fatal error when opening a BD backup it created
-
jharle
- Posts: 6
- Joined: Sat Apr 13, 2019 5:24 am
-
jharle
- Posts: 6
- Joined: Sat Apr 13, 2019 5:24 am
Re: MakeMKV fatal error when opening a BD backup it created
Oh my, I just read the previous post talking about the same thing. The suggestion of downgrading MakeMKV to 1.18.4 worked!
I guess it's a bug in the 2.0.0 version then.
Problem solved!
I guess it's a bug in the 2.0.0 version then.
Problem solved!
-
Annihilation
- Posts: 6
- Joined: Mon Apr 14, 2025 3:26 pm
Re: MakeMKV fatal error when opening a BD backup it created
Same here, there appears to be a bug in the v2.0.0. I hope mike takes note.