Ripping error

[BillCosbyStillsNash]

I have been happily ripping DVD's with makeMKV for a few years. Today I tried my first bluray disc and it gave this error:

Debug log started at Thu Dec 28 21:49:56 2023 , written by MakeMKV v1.17.5 linux(x64-release)
001005:0000 MakeMKV v1.17.5 linux(x64-release) started
Using 262272KB for read cache.
Network access is ENABLED, CURL version 7.74.0/OpenSSL/1.1.1w/1.43.0 (x86_64-pc-linux-gnu) , proxy server not set.
DEBUG: Code 0 at z6jq?_t<B1y?.8j.EyG^=::29393631
DEBUG: Code 0 at z6jq?_t<B1y?.8j.EyG^=::29393631
SDF v098: ASUS_BC-12D2HT_1.00_211306141200_K9DD8FD4924
SDF v098: ASUS_BC-12D2HT_1.00_211306141200_K9DD8FD4924
SDF v098: ASUS_BC-12D2HT_1.00_211306141200_K9DD8FD4924
001011:0000 Using LibreDrive mode (v06.3 id=4A7BB4081F6A)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at Na{GedVFv/gZm1nV:121265499
003310:0000 This disc uses newer version of AACS protection. Please let us know about it by visiting http://www.makemkv.com/verylongstring
DEBUG: Code 0 at Na{GedVFv/gZm1nV:29398070
003338:0000 Downloading latest HK to /config/data ...
003332:0000 Saved AACS dump file as file:///config/data/Linux ISO Obviously.tgz
003303:0000 The volume key is unknown for this disc - video can't be decrypted
DEBUG: Code 0 at RwN">DdY;aLEqG`l:213132721
DEBUG: Code 0 at RwN">DdY;aLEqG`l:213131341
DEBUG: Code 233 at qvuz8n9yipAURGj0+j0l6dWJ:0
DEBUG: Code 233 at YT/TnYdaAXy60Lof9WxTD+Zl:0
DEBUG: Code 233 at 6VRCa5Gzy2pQ/cbyz9VXenjn:0
DEBUG: Code 233 at 968WKr1dIUSLBHd6DamO2Ury:0
DEBUG: Code 233 at OyMZvkTsjKlwb+WOPXqVcH/P:0
DEBUG: Code 233 at OHFKnAhnzUT2bc0xohYVvTAW:0
DEBUG: Code 233 at ndMXOINbbwfDf0lfta9y5x6I:0
DEBUG: Code 233 at 4H2YDeKQak5k72J4+kHvAALt:0
DEBUG: Code 233 at V5R5RC3DOx0CpDke/YimNXpX:0
DEBUG: Code 233 at QYO8M9lWMKpmp0mpQAcyhZjV:0
DEBUG: Code 233 at tV34ZMDD83pAyZH2tRTuGXWe:0
DEBUG: Code 233 at CGkcCkXlJ3KJlq+adeJEuU2M:0
DEBUG: Code 233 at 9hANxZO2/Y1rgIC1VXzHwmWm:0
DEBUG: Code 233 at wo3dhg9OTugeUZ7rTmCnWs3D:0
DEBUG: Code 233 at apGJG0KK1D+zYthn0YVk8Sgb:0
DEBUG: Code 233 at YL7azCpxIJlTUsDEPvRkAErP:0
DEBUG: Code 233 at ymdWbOFde+Ji2jL2EEJidCs6:0
DEBUG: Code 233 at Bkm8YRY12iWdMUqMElpYbhB8:0
DEBUG: Code 233 at AgtqW0E3QJs34h3RLL/aq0M8:0
DEBUG: Code 233 at 9w6RGpCWzb42JDDs2iyrnGeY:0
DEBUG: Code 233 at zDMZuCGRbqWurUytPm1NZO2i:0
DEBUG: Code 233 at FxFOfr9CmRnlTwyZ4+joJahT:0
DEBUG: Code 233 at r4fem0Cs2SBkdLpS2QFhS+8r:0
DEBUG: Code 233 at Ulh0/10H4bVsn2KbcebdlA9f:0
DEBUG: Code 233 at m/uBxMjCjjSqqZVSO8ihI1M5:0
DEBUG: Code 233 at d9pFk/0UDLC5/ueuVptCmYrO:0
DEBUG: Code 233 at ZQQ9jraJljCtAR/nVjp13tON:0
DEBUG: Code 233 at 2/SLuo++MaNoW3QLi4MIYFRK:0
005010:0000 Failed to open disc
001011:0000 Using LibreDrive mode (v06.3 id=4A7BB4081F6A)
003007:0000 Using direct disc access mode
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2147483648 at Na{GedVFv/gZm1nV:121265499
003310:0000 This disc uses newer version of AACS protection. Please let us know about it by visiting http://www.makemkv.com/verlongstring
DEBUG: Code 0 at Na{GedVFv/gZm1nV:29398070

Now I don't know what any of that means. Can anyone help me out?

[dcoke22]

I don't see any actual errors in the snippet posted. Can you post the whole log?

[BillCosbyStillsNash]

I think I just did. Is that the info you need?

[Woodstock]

Your other post says that this is a drive from 2013. That's part of the reason you're getting the notice to send the "verylongstring" by clicking the link; it cannot blindly rip things by bypassing the existing lock-outs in the code. Did you submit the AACS protection information?

[dcoke22]

The release notes for MakeMKV 1.17.4 claim support for AACS v81, so the disc in question must be new.

I would presume if you try to rip an older blu-ray with an older version of AACS, then it'll rip. If you wait for an update to MakeMKV to support whatever version of AACS is on that disc, then it'll rip. If you try to rip the disc with a more modern optical drive with LibreDrive enabled, then it'll rip. Your ASUS BD-12D2HT with drive platform MT1939 is older than the more modern drives which have a MT1959 drive platform.

[BillCosbyStillsNash]

Did you submit the AACS protection information?

Yes

The release notes for MakeMKV 1.17.4 claim support for AACS v81, so the disc in question must be new.

I would presume if you try to rip an older blu-ray with an older version of AACS, then it'll rip. If you wait for an update to MakeMKV to support whatever version of AACS is on that disc, then it'll rip. If you try to rip the disc with a more modern optical drive with LibreDrive enabled, then it'll rip. Your ASUS BD-12D2HT with drive platform MT1939 is older than the more modern drives which have a MT1959 drive platform.

So if I understand you correctly, it isn't strictly necessary to get a drive with MT1959 platform and flash the firmware, as long as MakeMKV can bypass the AACS version on its own? I was reading up about flashing a drive on this forum and it read to me like it was mandatory for any blu-ray to be ripped.

[dcoke22]

So if I understand you correctly, it isn't strictly necessary to get a drive with MT1959 platform and flash the firmware, as long as MakeMKV can bypass the AACS version on its own? I was reading up about flashing a drive on this forum and it read to me like it was mandatory for any blu-ray to be ripped.

It is mandatory for UHDs to be ripped for sure. With most drives, most regular blu-rays will rip most of the time, but not necessarily in every case as this scenario illustrates.

As a side note, if you were thinking about an additional optical drive, the Pioneer drives are considered 'the best'. However, the newest firmware on those drives disables MakeMKV, so you have to get one with older firmware. The most reliable way to do that is to get one from a seller on this forum.

[BillCosbyStillsNash]

Thank you for the information. I hooked up the blu-ray drive to my windows PC and tried flashing it, but that failed. I put it back and suddenly the BD's that failed to rip before work fine now. So something worked? However these discs are from 2014 and not UHD.

[dcoke22]

Thank you for the information. I hooked up the blu-ray drive to my windows PC and tried flashing it, but that failed. I put it back and suddenly the BD's that failed to rip before work fine now. So something worked? However these discs are from 2014 and not UHD.

You're lucky your flash attempt failed. If it had 'worked' it very likely would've bricked your drive. For others reading this thread, do not try to flash firmware meant for a MT1959 platform drive onto your MT1939 platform drive. It won't work and will probably make your drive inoperable with no hope of recovery.

Power cycling the drive, jostling it around, or just attempting to rip the same disc multiple times in a row will sometimes produce different results. Reading an optical disc has a certain amount of mechanical analogness to it.

[BillCosbyStillsNash]

Keep the gremlins happy. Got it.

[dcoke22]

Keep the gremlins happy. Got it.

lol