Public KeyDB Disc Submissions

[keydb_helper]

Disc type: UHD
Disc ID: 0xB5B814B870CB16C9293CBB796F5507DBFFB5B1BA
Disc dump filename: MKB20_v77_Casablanca_98C7.tgz

Hey Brian, as I mentioned to frameloose just now, you can actually self-serve that particular title using SamuriHL's KeyDB Tool.

*Added 0x prefix to the SHA-1 hash to match template formatting

Thanks for paying attention to the template, it is appreciated.

[frameloose]

MKB20_v82_The_Housemaid_E7A4

Hey frameloose, thanks for the new disc dump. Your disc has been added to the public keydb. As you use Windows, you could've processed this particular disc with SamuriHL's KeyDB Tool. That would've avoided the need to post to this thread, so I'd definitely recommend trying it in the future. You can always post here if your title remains unsupported.

Here i have been using KeyDB Tool for like a year without knowing that feature Will try it next time

[BrianInSC]

Thank you! Working on the Samurai app now. My first disc dump and I'll continue to contribute.

[MrPenguin]

@RandomSelf, please stop creating new threads for each disc. You've created dozens of threads with zero replies and all it does is slow down the process of adding new titles by effectively hiding your own submissions.

To be clear, creating a new thread for each movie title (such as "Elio") is how MakeMKV expects people to announce their dump variants, as well as emailing those dumps to svq@makemkv.com. This allows people to know which TGZ dump files have already been emailed in, and so helps avoid overloading the mailbox with duplicates.

But the best way to add your dump to KEYDB is to post to this "Public KeyDB Disc Submissions" thread by following @keydb_helper's template .

[BrianInSC]

I had great success with the Samurai tool. Thank you for pointing me in that direction. It's easy and also, make sure your makemkv points to the updated directory. I did the Samurai tool and makemkv didn't work because I hadn't changed the database folder location. Very impressive.

[keydb_helper]

Here i have been using KeyDB Tool for like a year without knowing that feature Will try it next time

I had great success with the Samurai tool. Thank you for pointing me in that direction. It's easy and also, make sure your makemkv points to the updated directory. I did the Samurai tool and makemkv didn't work because I hadn't changed the database folder location. Very impressive.

Thanks guys. I didn't want to seem like I was complaining about the submissions, but self-serve really is the quickest and easiest option for everyone where possible.

Great to hear the custom data folder location is handled properly, I know that can be a source of frustration for MakeMKV users.

To be clear, creating a new thread for each movie title (such as "Elio") is how MakeMKV expects people to announce their dump variants, as well as emailing those dumps to svq@makemkv.com. This allows people to know which TGZ dump files have already been emailed in, and so helps avoid overloading the mailbox with duplicates.

Fair point, I probably should've requested a post here in addition to rather than instead of a title-specific thread.

But the best way to add your dump to KEYDB is to post to this "Public KeyDB Disc Submissions" thread by following @keydb_helper's template .

I'm not 100% sure the '@'-tagging works here - I was only notified about the quote/reply. No idea why I thought that would work in my earlier post.

[BrianInSC]

"Thanks guys. I didn't want to seem like I was complaining about the submissions, but self-serve really is the quickest and easiest option for everyone where possible.

Great to hear the custom data folder location is handled properly, I know that can be a source of frustration for MakeMKV users."

No problem at all. I want to clarify the workflow if I could. If Makemkv can't locate a key, run Samurai's db tool first to update the database as that alone might fix the issue. If not, and the app is pointed to the new/updated database, a disc dump would be the next step. Let me know if I missed anything.

Lastly, would grabbing the disc info from the db tool and saving it locally be of any value to the end user?