For those of us with Pioneer drives? /Dumps

[CLV_Ripper]

Apologies if this has been covered before, as I did some digging but couldn't find an answer here or otherwise.

I have been able to rip a couple thousand of my discs but with some of the recent releases I am running into the issue of "Volume key unknown." I read the threads pertaining to getting the dump logs and such but (and correct me if I am wrong) if you only have Pioneer drives, those are not able to provide the necessary information.

I have no problem waiting patiently if this is something that resolves itself over time, I just wanted to make sure I am not missing something that I can do to resolve this issue.

The discs currently presenting issues are;

Cloud Atlas UHD
Jarhead UHD
Boogie Nights UHD
Leaving Las Vegas UHD

Thank you. I appreciate any advice/help y'all are willing to provide.

[dcoke22]

MakeMKV supports two different disc decryption mechanisms. The built-in mechanism is called hashed keys and it works with all dumps from MakeMKV regardless of the brand of drive. When there is not a key for you disc and MakeMKV produces a dump, email that dump to svq@makemkv.com. Eventually a hashed key will be produced and MakeMKV will automatically download it as needed.

UHD FAQ

The other source for decryption keys is the public keyDB. The first post in the Public KeyDB Disc Submissions thread includes a template and instructions on how to submit dumps for inclusion in the keyDB. It also has links to where the keyDB can be downloaded, utilities to help keep it updated, and where to put the file so MakeMKV can use it.

These two ways to decrypt discs can be used together. If you can submit a dump to the keyDB you can also email it to svq@makemkv.com. Accidental duplicates emailed to MakeMKV aren't a big deal but duplicates submitted to the keyDB should be avoided if possible.

[CLV_Ripper]

Thanks for the reply.

When I try to access a disc I can see the folder it creates:

MakeMKV v1.18.2 win(x64-release) started
Using LibreDrive mode (v02.1 id=DFAA920B9011)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz
The volume key is unknown for this disc - video can't be decrypted
Failed to open disc

In reading the post you linked from Mike regarding the Hash key perhaps I missed it, but what is the file I am looking for to email as in the folder created I have a number of files (none that really clue me in) with .dat, .bin extensions along with two text files one of which is log while the other is version.
I also have two sub-folders; "AACS" and "BDMW" respectively.
Pardon if this is a silly question, but I presume I am not to be sending the entire folder, correct?

Again, thanks for the help.

[dcoke22]

The dump files are .tgz files. For Boogie Nights, it is MKB20_v82_Boogie_Nights_A332.tgz according to the log you posted.

[MartyMcNuts]

Thanks for the reply.

When I try to access a disc I can see the folder it creates:

MakeMKV v1.18.2 win(x64-release) started
Using LibreDrive mode (v02.1 id=DFAA920B9011)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz
The volume key is unknown for this disc - video can't be decrypted
Failed to open disc

In reading the post you linked from Mike regarding the Hash key perhaps I missed it, but what is the file I am looking for to email as in the folder created I have a number of files (none that really clue me in) with .dat, .bin extensions along with two text files one of which is log while the other is version.
I also have two sub-folders; "AACS" and "BDMW" respectively.
Pardon if this is a silly question, but I presume I am not to be sending the entire folder, correct?

Again, thanks for the help.

As per your log:

Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz

This is actually a link. If you click on it, it wil open the directory where the dump is (MKB20_v82_Boogie_Nights_A332.tgz) and you can add the dump to the email you send to svq@makemkv.com

[keydb_helper]

I have been able to rip a couple thousand of my discs but with some of the recent releases I am running into the issue of "Volume key unknown." I read the threads pertaining to getting the dump logs and such but (and correct me if I am wrong) if you only have Pioneer drives, those are not able to provide the necessary information.

Hey CLV_Ripper, just to be clear, you are correct that Pioneer disc drives cannot be used to generate entirely new entries for the public keydb. But they can utilise the existing records in the public keydb to decrypt discs in exactly the same manner as LG/Asus/Buffalo drives.

You can configure MakeMKV to utilise the public keydb by following my instructions here or use SamuriHL's utility for Windows (Link)

The discs currently presenting issues are;

Cloud Atlas UHD
Jarhead UHD
Boogie Nights UHD
Leaving Las Vegas UHD

Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz

The A332 variant of Boogie Nights was added to the public keydb on December 6. There is at least one supported UHD disc variant for your three other titles as well, so you've got a chance to go 4/4 with the keydb.

[CLV_Ripper]

I have been able to rip a couple thousand of my discs but with some of the recent releases I am running into the issue of "Volume key unknown." I read the threads pertaining to getting the dump logs and such but (and correct me if I am wrong) if you only have Pioneer drives, those are not able to provide the necessary information.

Hey CLV_Ripper, just to be clear, you are correct that Pioneer disc drives cannot be used to generate entirely new entries for the public keydb. But they can utilise the existing records in the public keydb to decrypt discs in exactly the same manner as LG/Asus/Buffalo drives.

You can configure MakeMKV to utilise the public keydb by following my instructions here or use SamuriHL's utility for Windows (Link)

The discs currently presenting issues are;

Cloud Atlas UHD
Jarhead UHD
Boogie Nights UHD
Leaving Las Vegas UHD

Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz

The A332 variant of Boogie Nights was added to the public keydb on December 6. There is at least one supported UHD disc variant for your three other titles as well, so you've got a chance to go 4/4 with the keydb.

Thank you for this (and also to the other responders,) I really appreciate the time and help.

Regarding the public Keydb, is there a way I can verify that MakeMKV is accessing/utilizing it? I downloaded the keydb zip file and decompressed it placing the .cfg in the appropriate folder (user/.MakeMKV) per the instructions. Still the referenced A332 version of Boogie Nights is giving the same "missing key" error.

And with regards to my initial question, my apologies to the above. I didn't realize the "folder" I was referring to WAS the actual .tgz file, so I will be emailing those separately.

Again, thanks for any/all help

[Coopervid]

I have been able to rip a couple thousand of my discs but with some of the recent releases I am running into the issue of "Volume key unknown." I read the threads pertaining to getting the dump logs and such but (and correct me if I am wrong) if you only have Pioneer drives, those are not able to provide the necessary information.

Hey CLV_Ripper, just to be clear, you are correct that Pioneer disc drives cannot be used to generate entirely new entries for the public keydb. But they can utilise the existing records in the public keydb to decrypt discs in exactly the same manner as LG/Asus/Buffalo drives.

You can configure MakeMKV to utilise the public keydb by following my instructions here or use SamuriHL's utility for Windows (Link)

The discs currently presenting issues are;

Cloud Atlas UHD
Jarhead UHD
Boogie Nights UHD
Leaving Las Vegas UHD

Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz

The A332 variant of Boogie Nights was added to the public keydb on December 6. There is at least one supported UHD disc variant for your three other titles as well, so you've got a chance to go 4/4 with the keydb.

Thank you for this (and also to the other responders,) I really appreciate the time and help.

Regarding the public Keydb, is there a way I can verify that MakeMKV is accessing/utilizing it? I downloaded the keydb zip file and decompressed it placing the .cfg in the appropriate folder (user/.MakeMKV) per the instructions. Still the referenced A332 version of Boogie Nights is giving the same "missing key" error.

And with regards to my initial question, my apologies to the above. I didn't realize the "folder" I was referring to WAS the actual .tgz file, so I will be emailing those separately.

Again, thanks for any/all help

Depending on the OS it is case sensitive. It should be KEYDB.cfg if you are on MacOS.

[keydb_helper]

Regarding the public Keydb, is there a way I can verify that MakeMKV is accessing/utilizing it?

No, I don't believe MakeMKV will give any visual indication or record anything to its log file to suggest that it is trying to use the keydb.cfg file. It would be great if it did, as macOS/Linux users can experience issues relating to filename case sensitivity (eg: 'KEYDB.cfg' vs 'keydb.cfg')

I downloaded the keydb zip file and decompressed it placing the .cfg in the appropriate folder (user/.MakeMKV) per the instructions. Still the referenced A332 version of Boogie Nights is giving the same "missing key" error.

Just to double check, did you place the extracted keydb.cfg file in the exact same directory as the generated A332 disc dump file?

Feel free to upload your disc dump file to any file host you'd like and post a link here. It is possible that you your disc variant is distinct from the currently supported variants. Determining the title support status would be a good idea before we try to determine the keydb.cfg utilisation situation.

[CLV_Ripper]

Regarding the public Keydb, is there a way I can verify that MakeMKV is accessing/utilizing it?

No, I don't believe MakeMKV will give any visual indication or record anything to its log file to suggest that it is trying to use the keydb.cfg file. It would be great if it did, as macOS/Linux users can experience issues relating to filename case sensitivity (eg: 'KEYDB.cfg' vs 'keydb.cfg')

I downloaded the keydb zip file and decompressed it placing the .cfg in the appropriate folder (user/.MakeMKV) per the instructions. Still the referenced A332 version of Boogie Nights is giving the same "missing key" error.

Just to double check, did you place the extracted keydb.cfg file in the exact same directory as the generated A332 disc dump file?

Feel free to upload your disc dump file to any file host you'd like and post a link here. It is possible that you your disc variant is distinct from the currently supported variants. Determining the title support status would be a good idea before we try to determine the keydb.cfg utilisation situation.

- Running on a Win 11 machine so no, the issue related to Linux/MacOS shouldn't apply.

- Regarding your question about path, negative.
I followed the instructions on placing the .cfg along the path of c:>user>username>.MakeMKV folder.

The generated .tgz files are in a separate folder as created by MakeMKV in C://Media Backups
I am guessing by your question that the keydb.cfg file needs to be in the same folder as where MakeMKV drops the dump files, correct?
Or is it the other way around?

[keydb_helper]

- Running on a Win 11 machine so no, the issue related to Linux/MacOS shouldn't apply.

Thanks for the clarification.

- Regarding your question about path, negative.
I followed the instructions on placing the .cfg along the path of c:>user>username>.MakeMKV folder.

The generated .tgz files are in a separate folder as created by MakeMKV in C://Media Backups
I am guessing by your question that the keydb.cfg file needs to be in the same folder as where MakeMKV drops the dump files, correct?
Or is it the other way around?

Sorry, I should've picked up on that from your earlier post:

Saved AACS dump file as C:/Media Backups/MKB20_v82_Boogie_Nights_A332.tgz

Copy the keydb.cfg file to the folder C:/Media Backups/ and you should be good to go. The keydb.cfg file needs to go into the same path as your generated disc dump files.

I'll update my instructions accordingly.

[CLV_Ripper]

THAT DID IT!!!!

Thank you very much kind friend. I appreciate the hand holding and now the discs be spinnin and the movies be rippin.

[keydb_helper]

THAT DID IT!!!!

Thank you very much kind friend. I appreciate the hand holding and now the discs be spinnin and the movies be rippin.

I'm glad to hear everything worked out.

Feel free to post any unsupported disc dumps to the public keydb thread: Link. Unless you have a BDR-UD04 (or one of the other especially unhelpful Pioneer drives), there may be some value in your disc dump files if a 'sibling' disc is already known to the public keydb.

[SamuriHL]

My tool will tell you the status of your discs and keep the makemkv copy of the keydb up to date. Since you're on windows it could be useful.

Sent from my SM-S938U1 using Tapatalk