UHD key file sticky needed

[datman]

Is there a way to have a separate key list for UHD keys? I just started messing with making UHD backups with Makemkv and only a few will work. I can only assume all or most of the thousands that must be in the latest KEYDB file are Blu-ray files not UHD. So far The Martian, Hunger Games, Catching Fire, and Independence Day are the only ones that work. 5 Bourne movies, Apollo 13, Serenity all don't work.

I'm not even sure I'm unpacking them correctly. Does it need to stay a .cfg file or can I just keep an ongoing notepad file where a paste new keys on the file.

[Relight]

I have updated the OP here: http://forum.doom9.org/showthread.php?t=175194

Notepad can be used to edit a save a .cfg file, and yes, you can just add keys to the end by yourself.

[datman]

I have updated the OP here: http://forum.doom9.org/showthread.php?t=175194

Notepad can be used to edit a save a .cfg file, and yes, you can just add keys to the end by yourself.
Thanks as far as I can tell that is the file I have had. I reunpacked being careful how I paste additions everything gets jumbled up. I just need to look for AACS 2.0 files.

I guess DEUHD has a better grasp on the files.

[Relight]

KEYDB.cfg is a plain text file. It could be called ".txt" but whatever the original file history, it was decided to name it ".cfg" and so I guess that's what programs that make use of the file are looking for.

Not sure what you mean by "jumbled up" - only thing I can think of is that different operating systems - Windows, Mac, Linux - use different carriage return encoding. It shouldn't affect the ability to use the file, it only affects what you might see when you look at or edit the file, depending on the editing program you use. KEYDB.cfg has Windows-based encoding. You mentioned Notepad so I believed you were on Windows as well. EditPad Lite is a nice Notepad replacement that has an option for carriage return encoding.

[datman]

KEYDB.cfg is a plain text file. It could be called ".txt" but whatever the original file history, it was decided to name it ".cfg" and so I guess that's what programs that make use of the file are looking for.

Not sure what you mean by "jumbled up" - only thing I can think of is that different operating systems - Windows, Mac, Linux - use different carriage return encoding. It shouldn't affect the ability to use the file, it only affects what you might see when you look at or edit the file, depending on the editing program you use. KEYDB.cfg has Windows-based encoding. You mentioned Notepad so I believed you were on Windows as well. EditPad Lite is a nice Notepad replacement that has an option for carriage return encoding. Well mindlessly coping and pasting multiple .cfg files and pasting other text only keys if you're not careful where the cursor is you have no idea where things start and stop and appears to be all jumbled up. The new hashed keys posted at the mkv forum are complete. http://s000.tinyupload.com/?file_id=05962162787401969656

[Relight]

Sorry, I'm not really sure how to help you since you didn't give any new information or reply to any of my suggestions, you only reiterated your technical explanation that the file "appears to be all jumbled up."

The "hashed keys" posted in the MakeMKV forums will ONLY work with MakeMKV - they're of no use to non-MakeMKV users.

[datman]

Sorry, I'm not really sure how to help you since you didn't give any new information or reply to any of my suggestions, you only reiterated your technical explanation that the file "appears to be all jumbled up."

The "hashed keys" posted in the MakeMKV forums will ONLY work with MakeMKV - they're of no use to non-MakeMKV users.
You can copy paste the text into your old .cfg file.

Yea this new hashed file seems to be a complete aacs 2.0 key list so I removed everything I pasted in before and just have that list and in the future I will be mindful of exactly what and where it is being pasted.