28 Years Later - says v82 is to new?

[Rander]

Been trying for about a month now to rip 28 Years Later. When inserting the disc in my Linux machine, MakeMKV reports

Code: Select all

Drive Information
OS device name: /dev/sr0
Current profile: BD-ROM
Manufacturer: ASUS
Product: BW-16D1HT
Revision: 3.10
Serial number: KLHJCRI3745
Firmware date: 2119-01-04 10:14
Bus encryption flags: 1F
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 3.10
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Disc Information
Label: 28_YEARS_LATER
Timestamp: 2025-07-31 08:36:22
Protection: AACS v82
Data capacity: 33.56 Gb
Disc type: BD-ROM
Number of layers: 2
Channel bit length: 74,5 nm (25.0 GB max. per layer)

When trying in my Windows machine:

Code: Select all

Drive Information
OS device name: \Device\CdRom0
Current profile: BD-ROM
Manufacturer: ATAPI
Product: iHBS112 2
Revision: PL06
Serial number: 3772512087 226331500436
Bus encryption flags: 1E
Highest AACS version: 82

Disc Information
Label: 28_YEARS_LATER
Timestamp: 2025-07-31 08:36:22
Protection: AACS v82
Data capacity: 33.56 Gb
Disc type: BD-ROM
Number of layers: 2
Channel bit length: 74,5 nm (25.0 GB max. per layer)

When opening the disc, it says

Code: Select all

Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
This disc uses newer version of AACS protection. Please let us know about it by visiting http://www.makemkv.com/a/?iam1YiqVwtGyNhABd+YVmDR2fMvwvSRYT1/QspC08iC8XZ4kGHEPvsF21z7ZvA==

This happens on both my Linux and Windows machines - on Windows, the link is http://www.makemkv.com/a/?CTDwEpy2WaEhF ... ss/arklA==

I obviously clicked the link, but I'm wondering why it says the disc uses a newer protection, and then says that is uses v82, which is supported?

It does rip the disc, but the resulting file skips and is full of what looks like compression artefacts. It plays perfectly fine in my br-players, so it's not just a bad disc...

Running v1.18.2 on both...

[dcoke22]

Regular blu-rays that use the latest version of encryption, AACS v82, have to be handled similar to 4K UHDs and slightly differently than regular blu-rays with older versions of encryption.

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.

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. For 4K UHDs, dumps from Pioneer drives can not generally be used for keyDB submissions. For regular blu-rays, dumps from Pioneer drives can be used for keyDB submissions. MakeMKV can use the keys provided by the public keyDB to decrypt discs with any brand of optical drive.

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.

UHD FAQ

[Rander]

Okay, I'm confused. It doesn't say it doesn't have the key - it says that the disc is using AACS v82, which is newer than AACS v82, which, I think we can agree, makes no sense. So is it still missing the key? I am already using keydb.cfg, and yes, I just updated it to 2026-01-10 17:38:01 to check, but alas, it made no difference...

So, how do I make the dump to submit the disc to the keydb on Linux?

[dcoke22]

MakeMKV should've made the dump the first time you tried to rip the disc. It'll be a .tgz file located in the 'data directory' that's configured for your MakeMKV (listed on the General tab in MakeMKV's preferences). It should've also mentioned it made the dump file and where it went in the log when it was created. If the dump file already exists, it isn't mentioned in the log.

If you remove the dump from the data directory and try to rip the disc again, it'll create the dump again.

[tommik128]

Can somebody make this clear for me please:

Is there a difference between clicking on the link in MakeMKV and sending a dump file to svq@makemkv.com?

Thank you.

[Woodstock]

Yes, there is. Clicking the link in the program sends SOME information about the disk to MakeMKV's author, but sending the file that is generated (ending in .TGZ) provides more information. It's actually something that is built into the program to provide information on earlier disk formats, which I think doesn't work as well as it did in the past.

[Rander]

MakeMKV should've made the dump the first time you tried to rip the disc. It'll be a .tgz file located in the 'data directory' that's configured for your MakeMKV (listed on the General tab in MakeMKV's preferences). It should've also mentioned it made the dump file and where it went in the log when it was created. If the dump file already exists, it isn't mentioned in the log.

Nope, not there...

Code: Select all

lars@dt:~/.MakeMKV$ ls -l
total 60968
-rw------- 1 lars lars 61502642 Jan 10 17:18 KEYDB.cfg
-rw-rw-rw- 1 lars lars   903168 Jan 12 08:08 _private_data.tar
-rw-rw-rw- 1 lars lars      556 Jan 12 08:35 screen.conf
-rw-rw-rw- 1 lars lars      598 Oct  3  2024 settings.conf
-rw-rw-rw- 1 lars lars      194 Jan 12 08:03 update.conf
lars@dt:~/.MakeMKV$

On the Windows machine there's only the _private_data.tar...

Oh, and to add to the mystery: VLC plays the disc just fine!

EDIT: While playing around with this, starting VLC and MakeMKV and opening the disc in different orders, suddenly MakeMKV DID actually make the dump file! After moving it from the data-dir, I have been unable to get MakeMKV to dump it again, so something is definately weird about this...