Dump submitted - MKB20_v76_Mad_Max_2-_The_Road_Warrior_25B7

[Mitsu]

Hello, i already submit this dumb by mail to svq@makemkv.com a few days ago.
Thanks for your help

[MrPenguin]

Hello, i already submit this dumb by mail to svq@makemkv.com a few days ago.

The latest KEYDB.cfg file contains these entries:

Code: Select all

0x016FC73B59210BF44FA9BDD552FBBB902268925E = MAD_MAX_2_THE_ROAD_WARRIOR (Mad Max 2: The Road Warrior) | D | 2021-09-29
0x4BA628458F5145E506C250A50E71405EC555C613 = MAD_MAX_2_THE_ROAD_WARRIOR [Mad Max 2: The Road Warrior 4K Ultra HD] | D | 2021-12-08

Does copying this file into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV help?

[Mitsu]

Thanks, it works.
However, I had tried to put the KEYDB.cfg file in the same location before my request, but I could not copy the BD.
Perhaps it was necessary to remove the first part of text from KEYDB.cfg or limit it to the only title likely to correspond?


Thanks again !

[MrPenguin]

Thanks, it works.
Perhaps it was necessary to remove the first part of text from KEYDB.cfg or limit it to the only title likely to correspond?

You should install the entire KEYDB.cfg file into MakeMKV's data directory. The lines I posted above are meaningless by themselves because they deliberately contain no keys.

KEYDB.cfg is updated regularly, so it's always worth checking for new keys. The best way to update it is to execute "findvuk synchronize" rather than re-downloading the entire file each time.