The Fugitive 4K

[G.P.L.]

Has no one else had trouble ripping The Fugitive from the 4K disc?

I get the following response from MakeMKV:

MakeMKV v1.17.6 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Gary/MakeMKV_log.txt
Using LibreDrive mode (v06.3 id=0FA242DD4D0B)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
Saved AACS dump file as C:/Users/Gary/.MakeMKV/MKB20_v77_The_Fugitive_1B34.tgz
The volume key is unknown for this disc - video can't be decrypted
DEBUG: Code 0 at g1G,9/u[_c:!rg}]:213132721
DEBUG: Code 0 at g1G,9/u[_c:!rg}]:213131341
Failed to open disc

This disc is from Amazon Canada, and has an ID of: AF785AAEB6E21E9E [THE_FUGITIVE], but I believe it's the same disc as the one from the U.S. Just the packaging is different.

I've attached the AACS dump file. Hopefully it won't appear twice.

The same message occurs with both of my ASUS BW-16D1HT drives, one internal and one in a USB enclosure.

Any help would be much appreciated.

Thanks.

Gary

[dcoke22]

You've got to email that dump into svq@makemkv.com.

UHD FAQ

[G.P.L.]

You've got to email that dump into svq@makemkv.com.

UHD FAQ

Thanks for the reply.

Yes, I did that, and tried ripping again several times since then with no luck.

I confirmed that the disc is not faulty by using AnyDVD to copy the entire contents to a hard drive.

At least I don't have to return it to Amazon.

[MrPenguin]

How did you compute the disk's "ID" of 0xAF785AAEB6E21E9E? It's too short to be what KEYDB.cfg would consider to be a disk ID value, which is computed as:

Code: Select all

SHA1(AACS/Unit_Key_RO.inf)

Is that actually its "Volume ID"?

If you become desperate, there may be a way of getting MakeMKV to decrypt using the public KEYDB.cfg file. But you will need to compute the SHA1 value of its AACS/Unit_Key_RO.inf file at the very least.

[dcoke22]

I confirmed that the disc is not faulty by using AnyDVD to copy the entire contents to a hard drive.

At least I don't have to return it to Amazon.

You can use MakeMKV's backup option to create an encrypted backup before a decryption key is available to make sure the disc is readable.

[G.P.L.]

How did you compute the disk's "ID" of 0xAF785AAEB6E21E9E? It's too short to be what KEYDB.cfg would consider to be a disk ID value, which is computed as:

Code: Select all

SHA1(AACS/Unit_Key_RO.inf)

Is that actually its "Volume ID"?

If you become desperate, there may be a way of getting MakeMKV to decrypt using the public KEYDB.cfg file. But you will need to compute the SHA1 value of its AACS/Unit_Key_RO.inf file at the very least.

Thanks for the reply.

The disc ID is what was reported in DVD Profiler when it read the disc.

When I right-click the AACS/Unit_Key_RO.inf file, I get the following:

Name: Unit_Key_RO.inf
Size: 65536 bytes (64 KiB)
SHA1: E8AF137E72078A64A64A68BAAD1493BE1E5DEBF2

But I have no idea how to enter that into the KEYDB.cfg file.

When I open the KEYDB.cfg file, nothing seems very obvious to me in terms of the format it uses.

Any idea how I enter the SHA1: E8AF137E72078A64A64A68BAAD1493BE1E5DEBF2 information, and anything else required, in the KEYDB.cfg file?

If I knew that, I assume I could decrypt discs myself using MakeMKV (I have a lifetime license), which could turn out to be very convenient.

Is there maybe a page on the forum somewhere about doing this?

I'm willing to give it a shot, after backing up the current copy of KEYDB.cfg, of course.

[MrPenguin]

Unfortunately, it's never that easy.

Check PM