Page 1 of 1

Verifying m2ts files after ripping

Posted: Sun Feb 26, 2023 5:51 pm
by radishhorse
Hi,

I know that MakeMKV validates the hashes of the m2ts files when it's creating a backup of a Blu-ray Disc. Is there a way to recheck the hashes after the backup is complete? I want to be able to do so, so that down the line I can verify that the files are valid. I can find the hash tables (ContentHash000.tbl, ContentHash001.tbl) in the AACS directory but I'm unsure how to use these to check my files.

Thanks!

Re: Verifying m2ts files after ripping

Posted: Sun Feb 26, 2023 11:12 pm
by Billycar11
Hmm not sure you can do that directly
But you can just make a hash in like md5 sha1/256 whatever right after it's done and keep that to make sure it never gets corrupt

Re: Verifying m2ts files after ripping

Posted: Mon Feb 27, 2023 3:49 pm
by dcoke22
If you've made a backup of a disc, you could always just use MakeMKV again to make a .mkv file from the backup. I'm pretty sure MakeMKV will validate the hashes again.

Re: Verifying m2ts files after ripping

Posted: Tue Feb 28, 2023 2:39 am
by radishhorse
So I tried backing up a disc, once encrypted and once decrypted. If I look at the m2ts files, they're all the same size (encrypted vs. decrypted) but different md5 hash values. Is this expected? I guess it makes sense that the hash values are different but it's odd to me that the file size didn't change.

Re: Verifying m2ts files after ripping

Posted: Tue Feb 28, 2023 3:03 am
by Billycar11
radishhorse wrote:
Tue Feb 28, 2023 2:39 am
So I tried backing up a disc, once encrypted and once decrypted. If I look at the m2ts files, they're all the same size (encrypted vs. decrypted) but different md5 hash values. Is this expected? I guess it makes sense that the hash values are different but it's odd to me that the file size didn't change.
thats expected the files are encrypted vs not so the files are differnt

Re: Verifying m2ts files after ripping

Posted: Tue Feb 28, 2023 4:48 pm
by radishhorse
Thanks! Didn't realize that encryption didn't change file size.