Version v1.18.1 "Failed to open disc" on BDs that open in 1.17.2

Please post here for issues related to Blu-ray discs
Post Reply
Message
Author
Yoshihide
Posts: 5
Joined: Sat Mar 12, 2022 4:07 am

Version v1.18.1 "Failed to open disc" on BDs that open in 1.17.2

#1 Post by Yoshihide » Fri Apr 25, 2025 10:49 am

I tried installing Version v1.18.1 on my test machine running macOS 15.5 Beta, and though the app opens as it should, BDs that were rippable in version 1.17.2 fail with an error "Failed to open disc".
MakeMKV v1.18.1 darwin(x64-release) started
Debug logging enabled, log will be saved as /Users/XXXX/MakeMKV_log.txt
Optical drive "BD-RE PIONEER BD-RW BDR-XS06JL 1.10 PFDL005733JPd" opened in OS access mode.
Using LibreDrive mode (v01.0 id=8AE8B9ABDAAB)
Using direct disc access mode
DEBUG: Code 29 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 29 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 22 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 30 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 25 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 7 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 4 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 28 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 15 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 25 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 18 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 8 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 16 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 15 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 26 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 9 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 3 at F!$<BDhDI-%<!y:29398070
DEBUG: Code 0 at F!$<BDhDI-%<!y:213137643
DEBUG: Code 2 at TwR8m;{0{V>]k|Z&:213132537
DEBUG: Code 0 at TwR8m;{0{V>]k|Z&:213131341
Failed to open disc
Just to note, the drive, computer, and the disc is NOT the cause of this, as if I boot the same Mac into macOS 14 Sonoma and use MakeMKV version 1.17.2, it reads perfectly without any problems.

Actually this error started in 1.17.3, so I have kept using 1.17.2 and never upgraded.
Unfortunately, I will probably soon need to upgrade to v1.18.1 as anything older won't even load in macOS 15.5 and hope this does get fixed soon, or if there are any workarounds, I'd like to know.

Post Reply