I've had some problems figuring out where to place keydb.cfg, and I'm still not sure it's doing it right.
I would love if MakeMKV on startup would just put a line in the status window along the lines of "Keydb.cfg found and loaded" or something to that effect...
Or is that just me?
Feature request: Acknowledgement of keydb.cfg
Re: Feature request: Acknowledgement of keydb.cfg
Yeah it would be nice to show/log what was the reason when no key was found ultimately (i.e., whether it couldn't find / open the file at the path it expects or there's no key for the respective disc in the file).
But to be fair, you can always obtain the disc ID (not VID) of a disc / backup and then check whether the KEYDB.cfg you (attempted to) provide to MakeMKV has an entry for it. If it does and MakeMKV still couldn't open your disc, then you pretty much know the file is not at the right place. (Unless it's backup of an AACS 1.0 title without discatt.dat -- MakeMKV seems / seemed to have a bug that it will leverage neither KeyDB nor HK to open the encrypted backup in such case...)
But to be fair, you can always obtain the disc ID (not VID) of a disc / backup and then check whether the KEYDB.cfg you (attempted to) provide to MakeMKV has an entry for it. If it does and MakeMKV still couldn't open your disc, then you pretty much know the file is not at the right place. (Unless it's backup of an AACS 1.0 title without discatt.dat -- MakeMKV seems / seemed to have a bug that it will leverage neither KeyDB nor HK to open the encrypted backup in such case...)