Dump Submitted - Red Heat (UK)

Please post here for issues related to UHD discs
Post Reply
Bluntmad
Posts: 13
Joined: Sat Apr 20, 2024 12:34 pm

Dump Submitted - Red Heat (UK)

Post by Bluntmad » Mon Aug 12, 2024 12:07 pm

MKB20_v70_BDROM_CC2D.tgz

MrPenguin
Posts: 473
Joined: Thu Oct 19, 2023 11:31 pm

Re: Dump Submitted - Red Heat (UK)

Post by MrPenguin » Wed Aug 14, 2024 7:47 am

Bluntmad wrote:
Mon Aug 12, 2024 12:07 pm
MKB20_v70_BDROM_CC2D.tgz
The latest KEYDB.cfg contains this disk entry which has a Volume Unique Key (VUK):

Code: Select all

0x62FF3EB1D80B5E74CCCF0AEC6C393708A62108C0 = BDROM (RED_HEAT) | D | 2019-08-29
and these disk entries which just have Unit Keys:

Code: Select all

0x940570BD7FE8055B71623043D87643FC8FA2252B = _NONAME_ [Red Heat (1988) - 4K Ultra HD] | D | 2022-01-14
0x2A33421B4AA9D08FCFC52FCB303821E271381733 = BDROM (Red Heat) | D | 2019-08-20
0xE739C4DD17EBE382D72EFED4C3C3C6166938B5E2 = BDROM [Red Heat] | D | 2019-08-28
0x56C8BC5F158DC9745D0B2EA306467C40339337A2 = BDROM [Red Heat] | D | 2019-08-29
MakeMKV needs to know your disk's VUK to decrypt it. Have you tried installing KEYDB.cfg in MakeMKV's data directory (i.e. where it writes its TGZ dump files) and restarting MakeMKV?

Bluntmad
Posts: 13
Joined: Sat Apr 20, 2024 12:34 pm

Re: Dump Submitted - Red Heat (UK)

Post by Bluntmad » Wed Aug 14, 2024 9:42 am

Indeed - Ripping now. (I noticed it also grabbed an updated HK dat, so either the latest KEYDB.cfg sorted it, or makemkv DB was updated.. )

Post Reply