AnyDVD will silently pass bad sector reads from UHDs. I often have to rip multiple times (iso) to get two rips that are identical.
The hashes (stored in AACS/ContentHash###.tbl) only apply to the encrypted data. I'm currently ripping protected ISOs so I can run a hash verifier to make sure my iso is good. I then mount the protected iso in VCD and let AnyDVD do the decryption.
It would save me a lot of hassle if AnyDVD would verify the M2TS hashes and retry until the data is good.
IMO the fact that AnyDVD returns data that may or may not be correct is a huge problem. AFAIK, this issue only affects UHDs so the UHD support caveat applies but this is a significant enough of a problem to warrant a prominent disclaimer.
The hash checks can only confirm that the M2TS files are correct (except the last size mod 196,608 bytes) so a correct ISO is not guaranteed but that's the data that matters most. Further checks could be made to ensure that the files in AACS/DUPLICATE and BDMV/BACKUP match their respective entries in AACS and BDMV.
The hashes (stored in AACS/ContentHash###.tbl) only apply to the encrypted data. I'm currently ripping protected ISOs so I can run a hash verifier to make sure my iso is good. I then mount the protected iso in VCD and let AnyDVD do the decryption.
It would save me a lot of hassle if AnyDVD would verify the M2TS hashes and retry until the data is good.
IMO the fact that AnyDVD returns data that may or may not be correct is a huge problem. AFAIK, this issue only affects UHDs so the UHD support caveat applies but this is a significant enough of a problem to warrant a prominent disclaimer.
The hash checks can only confirm that the M2TS files are correct (except the last size mod 196,608 bytes) so a correct ISO is not guaranteed but that's the data that matters most. Further checks could be made to ensure that the files in AACS/DUPLICATE and BDMV/BACKUP match their respective entries in AACS and BDMV.