www.makemkv.com

Is it possible for a manufacturer to put an invalid content hash table on a blu-ray disc? I've done a full disc backup of the retail American Woman disc three times on two different drives and, even though all three rips are bit perfect matches, my log looks like this with tons of hashcheck errors:

MakeMKV v1.16.4 win(x64-release) started
Backing up disc into folder "D:/BluRay/Temp/American Woman Test/AMERICAN WOMAN"
Loaded content hash table, will verify integrity of M2TS files.
Hash check failed for file 00001.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00001.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00001.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00001.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00001.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00001.m2ts.
Hash check for /BDMV/STREAM/00001.m2ts : 97.36% corrupt, 0% correct, 97.36% checked.
Hash check failed for file 00005.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00005.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00005.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00005.m2ts at offset 780288, file is corrupt.
Hash check for /BDMV/STREAM/00005.m2ts : 87.67% corrupt, 0% correct, 87.67% checked.
Hash check failed for file 00006.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00006.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00006.m2ts at offset 583680, file is corrupt.
Hash check for /BDMV/STREAM/00006.m2ts : 79.33% corrupt, 0% correct, 79.33% checked.
Hash check failed for file 00007.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00007.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00007.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00007.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00007.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00007.m2ts.
Hash check for /BDMV/STREAM/00007.m2ts : 99.60% corrupt, 0% correct, 99.60% checked.
Hash check failed for file 00004.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00004.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00004.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00004.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00004.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00004.m2ts.
Hash check for /BDMV/STREAM/00004.m2ts : 99.98% corrupt, 0% correct, 99.98% checked.
Hash check failed for file 00002.m2ts at offset 190464, file is corrupt.
Hash check failed for file 00002.m2ts at offset 387072, file is corrupt.
Hash check failed for file 00002.m2ts at offset 583680, file is corrupt.
Hash check failed for file 00002.m2ts at offset 780288, file is corrupt.
Hash check failed for file 00002.m2ts at offset 976896, file is corrupt.
Too many hash check errors in file 00002.m2ts.
Hash check for /BDMV/STREAM/00002.m2ts : 99.99% corrupt, 0% correct, 99.99% checked.
Encountered 126617 errors of type 'HashCheck Error' - see http://www.makemkv.com/errors/hashcheck/...
Backup done but 6 files failed hash check

IIRC, I've seen this on a few other Vertical Entertainment discs and basically ignored it because multiple rips were identical. Another interesting thing about this discs is that they are BD-Rs, not pressed discs. The .m2ts files play fine and I don't notice anything that would seem like 99.99% corruption. One other final note of interest is that MakeMKV simply lists the protection as AACS where it normally gives the AACS version:

Clean the disc clean the drive laser

Billycar11 wrote: ↑

Mon Jul 26, 2021 4:14 am

Clean the disc clean the drive laser

I understand that this is the mantra around here, but, I think in this instance, it really doesn't apply. I always clean my discs before any rips. And, in this case, I cleaned it in between each rip as well to try to get a clean rip. I even performed a fourth rip on a third drive and, once again, the rip was a binary match to those created from the other two drives yet generated identical errors in MakeMKV. I think that eliminates a dirty laser as well.

If this was limited to just one disc, I could chalk it up to a bad burn by the manufacturer. It is a BD-R after all. But, I've seen this same behavior on a few other discs from the same company.

Spyderm@n wrote: ↑

Mon Jul 26, 2021 4:08 pm

Billycar11 wrote: ↑

Mon Jul 26, 2021 4:14 am

Clean the disc clean the drive laser

I understand that this is the mantra around here, but, I think in this instance, it really doesn't apply. I always clean my discs before any rips. And, in this case, I cleaned it in between each rip as well to try to get a clean rip. I even performed a fourth rip on a third drive and, once again, the rip was a binary match to those created from the other two drives yet generated identical errors in MakeMKV. I think that eliminates a dirty laser as well.

If this was limited to just one disc, I could chalk it up to a bad burn by the manufacturer. It is a BD-R after all. But, I've seen this same behavior on a few other discs from the same company.

If you got a BD-R disc, you certainly got a bootleg copy. Neither of the big companies use BD-R for their release unless, and only if, you get it from Amazon and it is an On-Demand Manufacture title, but I've only seen this for DVD. Never for a Blu-Ray title. Most likely your disc is a bootleg.

puertorican wrote: ↑

Tue Jul 27, 2021 6:51 pm

Spyderm@n wrote: ↑

Mon Jul 26, 2021 4:08 pm

Billycar11 wrote: ↑

Mon Jul 26, 2021 4:14 am

Clean the disc clean the drive laser

I understand that this is the mantra around here, but, I think in this instance, it really doesn't apply. I always clean my discs before any rips. And, in this case, I cleaned it in between each rip as well to try to get a clean rip. I even performed a fourth rip on a third drive and, once again, the rip was a binary match to those created from the other two drives yet generated identical errors in MakeMKV. I think that eliminates a dirty laser as well.

If this was limited to just one disc, I could chalk it up to a bad burn by the manufacturer. It is a BD-R after all. But, I've seen this same behavior on a few other discs from the same company.

If you got a BD-R disc, you certainly got a bootleg copy. Neither of the big companies use BD-R for their release unless, and only if, you get it from Amazon and it is an On-Demand Manufacture title, but I've only seen this for DVD. Never for a Blu-Ray title. Most likely your disc is a bootleg.

I don't know that is is an On-Demand Manufacture title because Amazon lists it as in stock, but according to blu-ray.com, it is a BD-R:

https://www.blu-ray.com/movies/American ... ay/254411/

So, I don't think it is a bootleg disc. It did come from Amazon, though.

Either way, as I mentioned in my original post, even though MakeMKV reports the disc as being 99.99% corrupt, it plays perfectly both video and audio-wise. I'm just going to write it off as bogus errors, especially since I've seen identical behavior on other discs from this distributor and they play equally as well.

I did do some more testing with the disc and made the following observations:

1) I was unable to create an encrypted backup of the disc on one of my drives (Pioneer BDR-209M) with the following error:

Backing up disc into folder "D:/BluRay/Temp/American Woman Encrypted/AMERICAN WOMAN"
Loaded content hash table, will verify integrity of M2TS files.
Both disc and drive require bus encryption, but the bus key is not known.
Backup failed

2) I was, however, able to create an encrypted backup on my other drives. But the encrypted backup gave identical hash check failures as performing a decrypted backup.

if it's a manufactured on demand disc, its probably not encrypted. the protection mechanisms are

a) that its very difficult to read with PC bluray players (some standalone plyers also have issues)
b) they somehow write invalid data to areas of the disc which cause problems (might relate to a)
c) they heavily chunk the file and have playlists that randomize the order of those chunks (IIRC there was no protection at the actual playback level to pick a random playlist if cracked, as it can't tell as their is no encryption) it just makes life more difficult for people trying to convert to mkv or the like.

Basically, makemkv is the wrong tool to try and make a rip out of it. You might need to spend a few weeks trying to make a raw copy of the ISO to the point you are fairly confident you got every bit, then try and figure out which playlist it is (if there are many), by going one by one through them to see what makes sense then you can use makemkv to rip that one playlist.

its a lot of work.