I’m an occasional user of DVDFab Decrypter so I’m not a paying user, for that reason alone I know my request isn’t exactly a top priority. My request is that there be an option to turn OFF whatever inputs false data in place of unread data. In other words, what I’m looking for is the option for the rip to actually ‘fail’ and end if it encounters a read error that it can’t correct. If nothing else, I would at least like to know when random data has been used in a rip in place of the actual data from a read error.
My gripe, and it was very irritating to have it occur, is this: If DVDFab Decrypter encounters a read error while ripping, I presume it is basically inputing ‘zeros’ or something similar for the unread data. While this is actually a nice feature in the case of a heavily damaged disc in that it at least allows you to get a rip of the disc, I’ve found that it basically has inserted CRAP into a disc I ripped that is in perfect condition, a disc that should have no need whatsoever to have ‘zeros’ or whatever it is doing to fill in for the unread data.
I found this after viewing a ripped disc and noticing a small handful of momentary glitches in the video, I’ll post a capture of one of them below for an example. They aren’t on the original disc, and the original disc is in perfect condition, not a mark on it. It scans fine and the transfer rate is fine, I ripped the disc in the same drive I performed the tests below in. For the program to encounter read errors and input false data with a disc such as this is ridiculous. If the disc was in very poor condition, that would be one thing, but not a disc in this shape.
Regardless of whether I would have had this problem with this disc or not, I would REALLY like to see a simple option to turn OFF the ability of the program to input the false data, just end the rip if nothing else. Or at least notify the user at the end of the rip if any read errors and resulting false data was input for that rip, instead of a simple ‘ripped successfully’ message when it clearly wasn’t. That way I can then decide if I want to pursue other possiblities for ripping the disc rather than finding out the hard way when viewing the ripped content that crap was inserted into the data. I just ripped the disc using DVD Decrypter, no read errors, no SLOWDOWNS in rip speed, no corrupt video like in the capture below.
I consider what happened with my rip to be a serious flaw in the program, problems ripping a perfect disc, inserting false data, and making matters worse by giving the user no hint to the fact that false data was then inserted. Hopefully I didn’t overlook something, but I certainly don’t think I have. Thanks for hearing my complaint and creating an otherwise nice program (well, I hate the fact that it automatically creates a ‘DVD’ folder on startup, but I won’t go there).