www.makemkv.com

I have a collections of BD ISO's ripped using AnyDVDHD. When I open one to convert it to MKV I get a warning popup of "It appears that you have AnyDVD enabled...Do you want to continue anyway (error may occur)?"

I do not have AnyDVD enabled.

I don't know if it is related but when I open the ISO I also get the following in the log file:

MakeMKV v1.9.2 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\Mark/MakeMKV_log.txt
Using direct disc access mode
AACS directory not present, assuming unencrypted disc
DBG ASSERT: hO}HtNN\{^EB+"(|XAiqW at hkrCAjcek{u=KKv2xt:29393493
DBG ASSERT: hO}HtNN\{^EB+"(|XAiqW at hkrCAjcek{u=KKv2xt:29393493
DBG ASSERT: hO}HtNN\{^EB+"(|XAiqW at hkrCAjcek{u=KKv2xt:29393493
DBG ASSERT: hO}HtNN\{^EB+"(|XAiqW at hkrCAjcek{u=KKv2xt:29393493

If AnyDVD created the ISO, it will appear to MakeMKV that you are reading the BD through AnyDVD... the "signature" would be the same. AnyDVD has had versions that create damaged files. That is why the warning is in place.

Mike will have to provide translation as to what the debug asserts mean. They report specific things about the disk as MakeMKV reads it, when things aren't what they should be.

Since I have all of the source Blurays would it be safer to just re-rip? There doesn't seem to be any significant performance improvement starting with the ISO.

Mike said last year that the version that had the issue is now rather old, so you're PROBABLY safe ignoring the warning. It will be an irritant, but telling MakeMKV to continue will speed up the conversion a bit, since the data is already on a hard disk.

What I WOULD do, though, is dig out the disk that you're getting the assert messages on, and testing it to see if you get the same messages. After that test, you can make your own informed decision.

The same 4 assertions come from any of the ISO's that I ripped with AnyDVD; They do not occur when I poen the physical disc. Although not a perfect test by any means, I did an MKV from the physical disc for two movies and the output file size is identical to the MKV created from the ripped ISO.

I'll see if Mike comments on the debug assertions...

I've seen this message on BDs ripped with DVDfab and so far ignoring it hasn't caused any problems.