Dune Part 2 Dump Submitted

[Coopervid]

I've re-examined the public KEYDB.cfg for "Dune: Part Two" disks, and (as of June 17th 2024) can see 6 UHD entries in there. It might be worth checking whether your disk matches one of these.

The KEYDB.cfg file needs to be copied into the .MakeMKV/ directory, which is also where MakeMKV writes its .tgz dump files.

Thanks mate, I tried this a few days ago and it didn't work, however I've just downloaded keydb.cfg again and it's now working. Cheers.

You should regularily use the "synchronize" function of FindVUK and not redownload.

[Maxpower]

Below are the Dune Part Two UHDs in KEYBD.cfg as of 18JULY2024

Still waiting for this one: MKB20_v77_Dune-_Part_Two_BBAA from July 11

DUNE_PART_TWO (Dune: Part Two) | D | 2024-03-08 |MKBv77/BEE/FindVUK 1.75 - VolumeSize: 97574387712 (UHD)
DUNE_PART_TWO (Dune: Part Two) | D | 2024-02-24 |MKBv77/BEE/FindVUK 1.75 - VolumeSize: 84558086144 (UHD)
DUNE_PART_TWO (Dune: Part Two) | D | 2024-02-24 |MKBv77/BEE/FindVUK 1.75 - MainPlaylist: 00000.mpls - VolumeSize: 84558675968 (UHD)
DUNE_PART_TWO (Dune: Part Two) | D | 2024-03-23 |MKBv77/BEE/FindVUK 1.74 - VolumeSize: 84558675968 (UHD)
DUNE_PART_TWO (Dune: Part Two) | D | 2024-02-24 |MKBv77/BEE/UHD (LEGACY)
DUNE_PART_TWO (Blu-ray) | D | 2024-04-09 |MKBv77/BEE - VolumeSize: 87961108480 (UHD)

[lordmortis]

I just updated my KEYDB.cfg with the version from 2024-06-18 03:48:47 and it worked!

[MrPenguin]

Still waiting for this one: MKB20_v77_Dune-_Part_Two_BBAA from July 11

I think you must mean "18JUNE2024" and "June 11" .

But isn't that the same one that matpro76 was also waiting for? And matpro76 said yesterday (June 17th) that MakeMKV can now decrypt his disk using the latest KEYDB.cfg file.

Try computing the SHA1 hash of your disk's AACS/Unit_Key_RO.inf file: Logically, it should therefore match the DiscID of one of those 6 UHD entries you mentioned.

If you're a Linux or MacOS user then your file names are almost certainly case-sensitive, so you need to name it KEYDB.cfg instead of keydb.cfg. And you need to copy KEYDB.cfg into MakeMKV's data directory, which is the same directory where MakeMKV writes its .tgz dump files.

[Maxpower]

Still waiting for this one: MKB20_v77_Dune-_Part_Two_BBAA from July 11

I think you must mean "18JUNE2024" and "June 11" .

But isn't that the same one that matpro76 was also waiting for? And matpro76 said yesterday (June 17th) that MakeMKV can now decrypt his disk using the latest KEYDB.cfg file.

Try computing the SHA1 hash of your disk's AACS/Unit_Key_RO.inf file: Logically, it should therefore match the DiscID of one of those 6 UHD entries you mentioned.

If you're a Linux or MacOS user then your file names are almost certainly case-sensitive, so you need to name it KEYDB.cfg instead of keydb.cfg. And you need to copy KEYDB.cfg into MakeMKV's data directory, which is the same directory where MakeMKV writes its .tgz dump files.

Yes, you are correct @MrPenguin . . . it is June not July. Wishing my time away.
I loaded the latest KEYDB.cfg and it worked. Very happy.
This is the first time I have needed to do this with makemkv. Previously, new key files would be automatically downloaded during the disc scan. Is something broken now?
Thanks again.

[MrPenguin]

This is the first time I have needed to do this with makemkv. Previously, new key files would be automatically downloaded during the disc scan. Is something broken now?

MakeMKV's processing queue works in mysterious ways, and AFAIK it always has. In this particular case, it just seems that your disk's keys have appeared in KEYDB.cfg before they have in MakeMKV's hashed keys. I doubt there's anything more to it than that, seeing as hashed keys for other disks still seem to be appearing.

[yyuksel]

Loaded content hash table, will verify integrity of M2TS files.
Saved AACS dump file as C:/Video/MKB20_v77_Dune-_Part_Two_6EF8.tgz
The volume key is unknown for this disc - video can't be decrypted

[MrPenguin]

Saved AACS dump file as C:/Video/MKB20_v77_Dune-_Part_Two_6EF8.tgz

Have you also tried downloading and installing the KEYDB.cfg file, as described earlier in this thread? There is a chance that 6EF8 corresponds to one of the six "Dune: Part Two" disks that it contains.

[dcoke22]

Loaded content hash table, will verify integrity of M2TS files.
Saved AACS dump file as C:/Video/MKB20_v77_Dune-_Part_Two_6EF8.tgz
The volume key is unknown for this disc - video can't be decrypted

Email the dump file to svq@makemkv.com.

UHD FAQ

The KEYDB.cfg method may also work, but please email the dump.

[Octopi]

... The best I've seen is xreveal which has a freeware version. ...

I checked the xreveal site but it doesn't tell me the difference between the freeware and the paid version. Do you know?
Edit: Found it.

Unfortunately it Xreveal now also offline.
What's going on here?
First Redfox and now Xreveal.

[MrPenguin]

Unfortunately it Xreveal now also offline.

AFAIK Xreveal is just a decryption engine that needs the user (i.e. "you") to provide an external KEYDB.cfg file for its keys. I suggest checking your installation...

[Octopi]

AFAIK Xreveal is just a decryption engine that needs the user (i.e. "you") to provide an external KEYDB.cfg file for its keys. I suggest checking your installation...

I know how the program works and the installation is correct.
This is about the Xreveal website.
It was still online yesterday and today this website is no longer available.

[Coopervid]

... The best I've seen is xreveal which has a freeware version. ...

I checked the xreveal site but it doesn't tell me the difference between the freeware and the paid version. Do you know?
Edit: Found it.

Unfortunately it Xreveal now also offline.
What's going on here?
First Redfox and now Xreveal.

XReveal is not offline. Don't post false information.

[SamuriHL]

Xreveal.com is still there. I don't know what it means that it's "offline". As mentioned, you need the latest keydb.cfg and to point to it in the settings.

[Octopi]

XReveal is not offline. Don't post false information.

Xreveal.com is still there.

All is well again.
The Xreveal website is available again.
This was not false information yesterday.
The website was down for almost 24 hours.