Terminator 2 - Judgement Day (Lionsgate)

[basketballrhinoceros]

Subject: Submitting Keyfile Information for MakeMKV

Hello everyone,

I’m new to the community and forum, but I’ve been using MakeMKV for about a year now—and I love it!

Before posting, I searched for similar issues and found various discussions about ripping Lionsgate Blu-ray discs and different editions of Terminator, but I didn’t see anything specific to my version. So please, go easy on me!

My question is: How do I submit a DVD or Blu-ray log or keyfile information to contribute to the key database (keydb) that MakeMKV uses? I came across a post with a keydb.cfg file for others experiencing similar issues, but unfortunately, my edition still won’t rip. After reviewing the file, I realized my version isn’t listed, so I’d like to know if there’s anything I can submit to help the community.

I assume I need to enable debugging and generate some kind of log, but where should I submit it? Is there a preferred method, such as a pastebin or a specific queue for these submissions?

Thanks in advance for any guidance!

[dcoke22]

Hashed Keys via MakeMKV or the alternative keydb.cfg should only be needed for 4K UHDs. MakeMKV should be able to rip just about any DVD or regular blu-ray.

UHD FAQ

[basketballrhinoceros]

I see, thanks for the info. In my case, the source disc is a non-UHD 1080p Blu-Ray , but the default and/or baked-in keydb file doesn't seem able to decrypt the disc. I'm wrong, it is decrypting it and reporting it as damaged after subsequent attempts. Verified by reading the logfile. A close inspection of the disc reveals nothing, it looks brand new. Tried lab-grade isopropyl, no help. Tried a cleaning wax, no help. I guess it's time to purchase another disc.

[basketballrhinoceros]

I was wrong in my OP. It IS in the keydb.cfg file, line # 83775:

Code: Select all

0x4AF36D780BA062A72DAC246A0666430B2DD61D1B = LOGICAL_VOLUME_ID (Terminator 2: Judgement Day) | D | 2006-06-09 | V | 0x1B19D9F201AA5F18DFD0A932AFB2C2EF | M | 0x9C9B21B4CA491B08D0C5086D1459AC4A | I | 0x2A2EA8E2C2741BAE4DE1A7D686166863 | U | 1-0x82FDCA7046ABFEE67AFE7CE639F38C95 ; MKBv3/FindVUK 1.17 - MainPlaylist: 00003.mpls - VolumeSize: 24469307392 (BD)

I thought it said it couldn't decrypt it before, I've tried several times, but I can't reproduce it now. I'll try cleaning it again. Tried cleaning it one more time, but no luck. Will buy a new disc.

Although, I still wonder, if we come across something that needs to be added to the keys database, how do we do it?

[basketballrhinoceros]

Purchased a new disc, and the issue has resolved itself. I guess it was a manufacturing defect - as the disc that wasn't working was pristine on both sides. YMMV for this title. MISCHIEF MANAGED.

[dcoke22]

Although, I still wonder, if we come across something that needs to be added to the keys database, how do we do it?

If you get a 4K UHD that MakeMKV doesn't have a hashed key for, MakeMKV will produce a dump file. You'll see the name and location of the dump file in the log. You should then email that dump file to svq@makemkv.com and post on this forum that you submitted a dump for whatever movie and the name of the dump file. If you share that file on the internet somewhere and include a link to it on that post, some users on this forum will notice and add it to the public keydb.cfg database if necessary.

[basketballrhinoceros]

Although, I still wonder, if we come across something that needs to be added to the keys database, how do we do it?

If you get a 4K UHD that MakeMKV doesn't have a hashed key for, MakeMKV will produce a dump file. You'll see the name and location of the dump file in the log. You should then email that dump file to svq@makemkv.com and post on this forum that you submitted a dump for whatever movie and the name of the dump file. If you share that file on the internet somewhere and include a link to it on that post, some users on this forum will notice and add it to the public keydb.cfg database if necessary.

Perfect, thanks for the info!