Problem saving BR Porcupine Tree - Anesthetize

[patrick8639]

Hello,
I've first tried to save this bluray with version 1.9.2. MakeMKV says that the AACS certificate was revoked.
This morning, I've installed version 1.9.3. Now, when I try to save this bluray, MakeMKV starts, indicates (twice) that the integrity of the M2TS files will be checked, and ... does nothing more!
No more access to the bluray disc, no error message, nothing... even after half an hour.

Is this due to the try with version 1.9.2?
Is this a bug of version 1.9.3?
Do you have a solution to this problem?

Thanks in advance.

[mike admin]

Is this a bug of version 1.9.3?

Apparently yes
Can you please see if anything is written to error log, even if MakeMKV "hung"?

The likely workaround would be to make a decrypted full disc backup, and then open the backup in MakeMKV.

[patrick8639]

Hi Mike,

first thing, even if I have MakeMKV 1.9.3, the information says that my drive supports AACS until version 52!
I thought that version 54 should be supported by version 1.9.3.

Drive Information
OS device name: \Device\CdRom0
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BH16NS40
Revision: 1.00
Serial number: K84CCOE4316
Firmware date: 2112-10-31 19:17:
Bus encryption flags: 17
Highest AACS version: 52

Disc Information
Label: PT_ANESTHETIZE
Timestamp: 2014-02-11 16:40:22
Data capacity: 35.62 Gb
Disc type: BD-ROM
Number of layers: 2
Channel bit length: 74,5 nm (25.0 GB max. per layer)

When doing the backup, the only thing that the log displays is:

Backing up disc into folder "C:/Users/Patrick/Desktop/Video/backup/PT_ANESTHETIZE"
Loaded content hash table, will verify integrity of M2TS files.
Loaded content hash table, will verify integrity of M2TS files.

I'm now trying to make a MKV of the bluray content.

[patrick8639]

Mike,
another information: MakeMKV says that the protection of the disc is AACS v44

[Woodstock]

"Highest AACS version" lists the highest version your installation has seen. Mine says 53 right now.

[patrick8639]

Mike,
this morning, I've tried to backup a Blu-Ray that I already backuped before: some thing!
In the Windows Task Manager, there is a makemkvcon64 process that is running at 100% of a core, even after I stop MakeMKV and remove the Blu-Ray.

[patrick8639]

Mike,
having seen someone on the forum that has the same problem with another BluRay and you are asking for the debug log.
Here is the debug log from my side (I hope you can do something with these cryptic messages!).
DEBUG: Code 0 at wmCI]u>Qa:!AB69h:213139828
DBG ASSERT: /=Uy5>Q1NZ)}K_e?%zjQ,:<s6e1gf7$MKEe?_U::m+p-K at wmCI]u>Qa:!AB69h:29403797

[mike admin]

Mike,
this morning, I've tried to backup a Blu-Ray that I already backuped before: some thing!
In the Windows Task Manager, there is a makemkvcon64 process that is running at 100% of a core, even after I stop MakeMKV and remove the Blu-Ray.

Please reproduce this, and then follow instructions at /onlinehelp/dump.html - Ctrl+Alt+Del, Task Manager, create dump file. This would help a lot.

[MrVanx]

"Highest AACS version" lists the highest version your installation has seen. Mine says 53 right now.

Just to confirm, my information shows the following:

Drive Information
OS device name: \Device\CdRom0
Manufacturer: HL-DT-ST
Product: BDDVDRW UH12NS30
Revision: 1.03
Serial number: [REMOVED FROM POST!]
Firmware date: 2114-04-24 19:00:
Bus encryption flags: 16
Highest AACS version: 50

So that doesn't mean my drive only supports up to AACS v50....it means that the highest version I have worked with, in the history of the discs I have popped in the drive, is v50?

If so that's good, I have been expecting newer discs (AACS v51 and higher) to be a problem since there isnt a firmware update for my drive afaik.

[Woodstock]

The problem isn't really firmware in the drive, other than the fact that it will read the list of revoked keys and record them in its memory.

The problem is whether or not the version of MakeMKV you are running has a key that is NOT in that list. The key used by 1.9.2 is in the list that comes with AACS v54, so 1.9.3 has a different key.

Right now, though, you should hang onto the install file for 1.9.2 in case you hit one of the bugs in 1.9.3. And watch the reported "highest AACS version", in case you do find a v54 or later disk.