Page 1 of 1

After AACS v82 error, BD-RE Rip fails

Posted: Mon Mar 31, 2025 3:28 pm
by mmdesunida
Hey,

I have a Blu-ray TV recorder which can record TV program to Blu-ray discs (SHARP BD-W550)
Dumping backups from that BD-RE with recorded TV programs on MakeMKV worked until last week,
but after I tried AACS v82 rip on MakeMKV it stopped backing up the recorded contents...
(or maybe it is because I also tried playing the BD protected with AACSv82 on the recorder... it played well at least)

If I try some old BDs like AACSv70 to rip, it works but after that BD-RE rip still fails with AACSv82 related error message.
I already tried deleting MakeMKV and ~/Library/MakeMKV but no changes. (I'm using MakeMKV on macOS 13 Ventura M1 mac mini)
Is there any way to roll back this AACS latest settings for MakeMKV? or has my BD recorder been upgraded despite no internet connection?

Re: After AACS v82 error, BD-RE Rip fails

Posted: Thu Apr 10, 2025 1:46 am
by mmdesunida
I've found out another BD-RE with AACS v81 encrypted, tried recording dubs and decrypt with MakeMKV failing to with showing AACS v82 protection...
This means my BD TV recorder has been polluted with AACS v82... I think I gotta wait till MakeMKV deals with AACS v82 perfectly or find the keys of my rips by myself...

Re: After AACS v82 error, BD-RE Rip fails

Posted: Thu Apr 10, 2025 6:00 am
by MartyMcNuts
mmdesunida wrote:
Thu Apr 10, 2025 1:46 am
I've found out another BD-RE with AACS v81 encrypted, tried recording dubs and decrypt with MakeMKV failing to with showing AACS v82 protection...
This means my BD TV recorder has been polluted with AACS v82... I think I gotta wait till MakeMKV deals with AACS v82 perfectly or find the keys of my rips by myself...
Ensure you are using MakeMKV v1.18.1 and if a dump is generated for an AACS v82 MKB, email the dump to svq@makemkv.com and wait a few days before trying to rip it again.

Re: After AACS v82 error, BD-RE Rip fails

Posted: Fri Apr 11, 2025 1:47 pm
by mmdesunida
MartyMcNuts wrote:
Thu Apr 10, 2025 6:00 am

Ensure you are using MakeMKV v1.18.1 and if a dump is generated for an AACS v82 MKB, email the dump to svq@makemkv.com and wait a few days before trying to rip it again.
Thanks for the advice, I've sent the dump, but I'm not sure if it is right to send the dump for my private BD-RE rip... this is not the disc officially released.

Re: After AACS v82 error, BD-RE Rip fails

Posted: Fri Apr 11, 2025 11:24 pm
by MartyMcNuts
mmdesunida wrote:
Fri Apr 11, 2025 1:47 pm
MartyMcNuts wrote:
Thu Apr 10, 2025 6:00 am

Ensure you are using MakeMKV v1.18.1 and if a dump is generated for an AACS v82 MKB, email the dump to svq@makemkv.com and wait a few days before trying to rip it again.
Thanks for the advice, I've sent the dump, but I'm not sure if it is right to send the dump for my private BD-RE rip... this is not the disc officially released.
Don't know exactly how discs of TV recordings work exactly. I would assume the blu-ray recorder adds some kind of encryption to the disc/files.

Re: After AACS v82 error, BD-RE Rip fails

Posted: Tue Apr 29, 2025 3:15 am
by mmdesunida
MartyMcNuts wrote:
Fri Apr 11, 2025 11:24 pm

Don't know exactly how discs of TV recordings work exactly. I would assume the blu-ray recorder adds some kind of encryption to the disc/files.
I searched for this a whlie ago and now I think I realized what actually happened to my BD recorder with experiment.

According to some articles on the net, AACS certs of BD drive is always open to overwrite for the latest version, but no rollback can be applied nevertheless of initialization.

This was my experiment procedure:

1. Format BD-RE
2. Initialize my BD recorder
3. Dub recorded videos on formatted BD-RE with 2's BD recorder
4. Check out on old BD-RW drive with older version of MakeMKV, without internet connection

The result showed up as the BD-RE is still locked with AACS v82.
So this case would be closed as:
- BD recorder might have been recently updated(we call it 'contaminated') when I put a brand new BD-rom protected with AACS v82.
- It doesn't matter if both writer drive and discs are initialized.

Anyway the key from my private disc seems registered on KEYDB so it works from last week... Thanks for the effort everyone!