No. You're mistaken The disc was tested extensively by a number of people that know what they're doing, and dvdfab did not release a version that worked properly until Sept. 1st. You either didn't do a full discbackup--or, quite simply, you have a faulty backup.
WRONG! I did a complete backup and all features work for me - I watched the backup that I made with DVDFab 3.1.7.6, prepped with PGCEdit and then burned with ImgBurn 2.3.2.0. Perhaps PGCEdit fixed whatever remaining structures others had problems with after using DVDFab? So, your conclusions are not the final word here - DVDFab DID get the data to my hard drive, and then my usual PGCEdit prep (normally just to examine layer break possibilities) and ImgBurn DID result in a flawless backup - thank you.
This was the only program that worked properly with that disc since day 1.
Maybe as a one step solution (see my success with DVDFab/PGCEdit/ImgBurn)
All Anydvd betas that were released at that time were open, yes. click
http://forum.slysoft.com/showpost.php?p=48669&postcount=1
No. You're completely wrong.
COMPLETELY wrong? No, I'm right - I caveated my statement by saying that AnyDVD may have had it licked, but it was in a beta that was announced in the forum and NOT in the main download area on Slysoft where I looked and I expect that the average user would turn to when they are looking for a new release to fix such an issue.
Because you don't, and you're writing things that are completely wrong.
As you admitted, you don't know the specifics either, and actually said the following:
My point really has nothing to do with that aspect (of scanning the disc through the menu; as far as that goes, I'm about as much in the dark about the specifics as most people are.)
So, if you are in the dark about that, and that is my theory on how AI works, how can you judge my hypothesis "completely wrong?"
Yes, with previous versions. Presently the only disc I'm aware of having an issue with the A.I. scanner enabled is 8 Below Japan.
Great, thanks for verifying that the AI scanner is still buggy. That illustrates and strengthens my point. As I said earlier, future bugs will likely be encountered when new titles are released with protection that target the technology. However it is promising that the number of broken titles is shrinking, so perhaps the AI scanner will indeed end the cat and mouse game with the copy protection developers after all - as a paying customer I'm in Slysoft's corner!
No. And the answer is because you don't understand how the A.I. scanner works--and you quite simply don't know what I do know (and I can't reveal it at this time, unless someone from Slysoft does so first).
Fine, I surrender - you win. Keep using AI scanning and examining your backups in detail for any unintended artifacts that it might have been introduced. Then, if and when you do find one, you can toss the backup and try backing it up with it disabled. I'll continue trying my backups with it disabled, confident that AI couldn't have introduced errors, so I don't have to watch the movie again to be sure. Only if I have issues with it disabled will I turn it on, and then will have to follow the same verification routine. My method seems like it would consume less time, but as you stated I don't know what I'm talking about...
I really didn't intend to escalate this discussion to this level. I entered this thread because I initially encountered an issue with AI scanning and PUO removal and thought I should report it, and then had the decency to come back and state that because it stopped happening, it must have been something on my end. I'm a chemical engineer and I'm very familiar with experimental design and root cause failure analysis, and these precepts confirm that AnyDVD's AI scanning could not be the cause for my initial experience with PUO removal and proper playback.
My mistake was to take it further than this - it seemed obvious to me that if a new feature is causing issues with previously broken protections and introducing errors, then it is best used with extereme caution. These issues caused another developer to make their similar feature a fallback, but since AI is now apparently more intelligent and less fallible, then Slysoft has nothing to learn from them.
Thanks for the stimulating and educational discussion - I'm done with this thread. Other readers can judge for themselves if I've made any points or suggestions worthy of consideration and implementation. Above all else, I'm a dedicated Slysoft fan and consumer. My intention was never to badmouth the products, which are indeed superior to the competition. I was only hoping to make some helpful suggestions to do a "slow roll" on the AI implementation until it was more mature...
Regards,
fordman