UHD disc keys recognized on one drive but not another

[outlier]

I saved many of my discs when my computer had 1-bit in a DIMM that was defective (0x2 could get stuck on in a particular byte in certain circumstances). So, after replacing the RAM I'm re-saving those discs using the same computer and OS (for the curious I am comparing the original & new files using a custom app I write to see which & how many files have evidence of this bad bit).

Some of the discs I'm re-saving are now reporting unknown keys and generate a tgz. Examples are:

MKB20_v60_Lone_Survivor_A15D.tgz
MKB20_v61_Jack_Reacher_Never_Go_Back_B12B.tgz
MKB20_v61_Ready_Player_One_6B49.tgz
MKB20_v77_Avatar-_The_Way_of_Water_0F3E.tgz

I'm typically running two instances of MakeMKV, each pointing to a different drive (a Pioneer BDR-XS07U and a Pioneer BDR-X13U). When the issue does occur (which is uncommon but not rare) it's always the BDR-XS07U instance that doesn't recognize the disc, so I then later save the disc without issue in the BDR-X13U instance.

I'm not sure if it's a drive-specific issue, or just generically about multiple MakeMKV instances (I usually start the BDR-X13U instance first). I do use a keydb.cfg, so I suppose it's possible that the one keyfile (i.e., this one vs. MakeMKV's native file) is properly shared but the other is not. I suppose it might depend on whether some of these discs are in one file but not the other.

I suppose the TL;DR is whether there's an issue in MakeMKV to fix or of there's really a need for me to send these files to svq@ .

[MrPenguin]

MKB20_v60_Lone_Survivor_A15D.tgz
MKB20_v61_Jack_Reacher_Never_Go_Back_B12B.tgz
MKB20_v61_Ready_Player_One_6B49.tgz
MKB20_v77_Avatar-_The_Way_of_Water_0F3E.tgz

If the latest KEYDB.cfg file doesn't work then I'm sure The Powers That KEYDB would be interested in examining those dump files too, were you to make them available somehow please?

Did you use "findvuk synchronize" to ensure that both your KEYDB.cfg files are up-to-date?

[outlier]

Did you use "findvuk synchronize" to ensure that both your KEYDB.cfg files are up-to-date?

It's all the same file, so there is no "both". Basically launch MakeMKV twice on the same computer--one says the disc is unrecognized and spits out a tgz and the other processes the same disc without issue. So, despite the same keys & files being used by both MakeMKV processes only 1 of the 2 can find what it's looking for.

[MrPenguin]

It's all the same file, so there is no "both". Basically launch MakeMKV twice on the same computer--one says the disc is unrecognized and spits out a tgz and the other processes the same disc without issue. So, despite the same keys & files being used by both MakeMKV processes only 1 of the 2 can find what it's looking for.

I have checked the KEYDB.cfg file, and it looks like at least two of your disks cannot have a MakeMKV-compatible entry in there. I cannot explain what MakeMKV is doing but I would still be interested in those TGZ dump files please, to see if The Powers That KEYDB can generate any extra VUKs.

[MartyMcNuts]

Did you use "findvuk synchronize" to ensure that both your KEYDB.cfg files are up-to-date?

It's all the same file, so there is no "both". Basically launch MakeMKV twice on the same computer--one says the disc is unrecognized and spits out a tgz and the other processes the same disc without issue. So, despite the same keys & files being used by both MakeMKV processes only 1 of the 2 can find what it's looking for.

You shouldn't use MakeMKV that way. To use multiple instances, go into preferences and check the box for "Single Drive Mode". This way, when you want to use multiple instances of MakeMKV, each one will ask you to select the drive to use for that instance. This way, the drives and MakeMKV instances won't interfere with each other.

[outlier]

You shouldn't use MakeMKV that way. To use multiple instances, go into preferences and check the box for "Single Drive Mode". This way, when you want to use multiple instances of MakeMKV, each one will ask you to select the drive to use for that instance. This way, the drives and MakeMKV instances won't interfere with each other.

I always use MakeMKV in this way (i.e., I do get the prompt and pick out the drives), I just didn't spell it out.

[outlier]

Another title now: MKB20_v76_Ghost_in_the_Shell_7751.tgz

As an experiment I closed both MakeMKV and just launched one for the BDR-XS07U and still experienced the issue. So, it seems like it something specific with MakeMKV and the BDR-XS07U rather than about concurrent instances.

[MartyMcNuts]

Another title now: MKB20_v76_Ghost_in_the_Shell_7751.tgz

As an experiment I closed both MakeMKV and just launched one for the BDR-XS07U and still experienced the issue. So, it seems like it something specific with MakeMKV and the BDR-XS07U rather than about concurrent instances.

Is this drive LibreDrive enabled? If not, has the drive certificate been revoked at all?

[outlier]

Is this drive LibreDrive enabled? If not, has the drive certificate been revoked at all?

It works fine with other 4K discs.

Drive Information
Manufacturer: PIONEER
Product: BD-RW BDR-XS07U
Revision: 1.01
Firmware date: 2020-09-03
Bus encryption flags: 13
Highest AACS version: 81

LibreDrive Information
Status: Enabled
Drive platform: RS8E21
Firmware name: PIONEER BDR-BDS7
Firmware type: Original (unpatched)
Firmware version: 1.01/ID05
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

[MartyMcNuts]

Is this drive LibreDrive enabled? If not, has the drive certificate been revoked at all?

It works fine with other 4K discs.

Drive Information
Manufacturer: PIONEER
Product: BD-RW BDR-XS07U
Revision: 1.01
Firmware date: 2020-09-03
Bus encryption flags: 13
Highest AACS version: 81

LibreDrive Information
Status: Enabled
Drive platform: RS8E21
Firmware name: PIONEER BDR-BDS7
Firmware type: Original (unpatched)
Firmware version: 1.01/ID05
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Maybe you need to give the discs a good clean before using that drive.

[Mr_Orange]

Did you use "findvuk synchronize" to ensure that both your KEYDB.cfg files are up-to-date?

It's all the same file, so there is no "both". Basically launch MakeMKV twice on the same computer--one says the disc is unrecognized and spits out a tgz and the other processes the same disc without issue. So, despite the same keys & files being used by both MakeMKV processes only 1 of the 2 can find what it's looking for.

You shouldn't use MakeMKV that way. To use multiple instances, go into preferences and check the box for "Single Drive Mode". This way, when you want to use multiple instances of MakeMKV, each one will ask you to select the drive to use for that instance. This way, the drives and MakeMKV instances won't interfere with each other.

I wasn't aware of this option but will use it from now on. I only bought a second drive a couple of months ago andonly tend to use both when ripping TV series.

[outlier]

Maybe you need to give the discs a good clean before using that drive.

It it was an LG drive I'd be more open to it, but the Pioneers tend to read with accuracy or refuse to read. Well, I'm basing that in part on how people tend to think that LGs make up things with they have problems reading part of a disc (and I do also have 2 LGs, but don't use so much now that I have 3 Pioneers), though I'm not sure how much of that believe about LGs can be believed given how MakeMKV will verify track contents against the hash files. Anyway, today's disc (out of 1 or a few dozen) is MKB20_v76_News_of_the_World_74C1.tgz.