www.makemkv.com

It's helpful but ultimately unnecessary to have FindVUK. You can download the keydb directly from the website. FindVUK just makes it easier to keep it up to date.

...and with the .bat file it's 1-2-3. No fumbling. All is done automatically.

SamuriHL wrote: ↑

Mon Feb 19, 2024 8:18 pm

It's helpful but ultimately unnecessary to have FindVUK. You can download the keydb directly from the website. FindVUK just makes it easier to keep it up to date.

Ah - found the URL in the ini file. Thx for the heads up for us Mac users

SamuriHL wrote: ↑

Mon Feb 19, 2024 8:18 pm

It's helpful but ultimately unnecessary to have FindVUK. You can download the keydb directly from the website. FindVUK just makes it easier to keep it up to date.

So this kinda begs the question of why MakeMKV doesn't just download & use that key file directly instead of rolling its own?

rkhollister wrote: ↑

Mon Feb 19, 2024 8:38 pm

So this kinda begs the question of why MakeMKV doesn't just download & use that key file directly instead of rolling its own?

Partly because KEYDB.cfg is a "legacy" format that contains less information than either MakeMKV's database or even FinkVUK's XML files.

Because as kuel as the keydb is, and it is very very awesome, it's user generated. Meaning it requires people to upload keys. And that's hardly comprehensive of every single disc that someone may encounter. Whereas submitting a dump to MakeMKV submits the data necessary to always (AACS 2.1 notwithstanding) decrypt the keys. I'm just thankful Mike left support for reading the keydb in place.

MrPenguin wrote: ↑

Mon Feb 19, 2024 8:50 pm

rkhollister wrote: ↑

Mon Feb 19, 2024 8:38 pm

So this kinda begs the question of why MakeMKV doesn't just download & use that key file directly instead of rolling its own?

Partly because KEYDB.cfg is a "legacy" format that contains less information than either MakeMKV's database or even FinkVUK's XML files.

Not anymore.

Coopervid wrote: ↑

Mon Feb 19, 2024 10:44 pm

MrPenguin wrote: ↑

Mon Feb 19, 2024 8:50 pm

Partly because KEYDB.cfg is a "legacy" format that contains less information than either MakeMKV's database or even FinkVUK's XML files.

Not anymore.

Err, really? KEYDB.cfg doesn't contain any field for (say) whether the disc uses bus-encryption, whereas FindVUK's XML file does. Everything that comes after ";" in KEYDB.cfg is just a free-format comment.

EVERY UHD contains bus encryption so that's pointless. The only thing that REALLY matters is the decryption key(s) and the disc ID. It's not like you get to see all that great information from MakeMKV's hashed keys which are embedded and encrypted.

SamuriHL wrote: ↑

Tue Feb 20, 2024 1:05 am

EVERY UHD contains bus encryption so that's pointless.

And some non-UHD discs also contain bus encryption. The point is that KEYDB.cfg was created before bus encryption (and UHD!) even existed and so obviously its format doesn't support it.

And if you enable LIbreDrive, bus encryption ceases to become a problem. Again, the only thing that REALLY matters is the unit keys and the disc ID. All the other information is wholly irrelevant.