I am looking for the fastest DVD reader that is also the most versatile I can find out there for better transfer rates when using in tandem with my NEC2510a. I have a Lite-ON right now, and would like suggestions on the best brand, and where to get it.
You need a Lite-ON 166S or 167T with Codeguys firmware, but you will also need a hard drive with either a 16MB cache, see Maxtor, OR a current SCSI hard drive to get optimum performance from the drive.
Interesting, I’ve had peaks of 15.4x with my 166S’s and they will regularly sustain 12x, although I think they’re probably better with DS1C FW versus DS1E, further testing will follow on this during the holiday season. Personally I’ve never bothered to time a rip, or perhaps I should say make note of what DVD Decrypter reports.
Mike was talking about dvd9 ripping speed The aopen is great, slightly faster in single layer reading too. The lite-on and aopen are both great, i have a lite-on 166s with codeguys 14x firmware which runs great on decent quality discs. There’s also a toshiba dvd-rom that’s supposed to be very fast too.
I hope this isn’t considered cross posting (since I’m not starting a new thread either time) but it seems like the 18 page aopen thread might be dead and this is about the liteon too. I got the impression the a open doesn’t work well for error scanning because it reads too fast and reprots to many errors. If it is getting a lot of errors at high speeds, wouldn’t it be beter to use a slower drive? Wouldn’t you get a beter copy or am I misunderstanding this because I am considering buying one for dvd9 ripping (the liteon or the aopen).
I have used both the Liteon 167T with codeguys firmware and the AOpen 1648 AAP at the same time. On the same media, the AOpen is faster, as reported. At the beginning of the WAY too long Aopen thread it was reported that a German publication had done testing on the error correction capability and had found it to be one of the best they had tested.
When my AOpen detects an error it slows down in an attempt to read the error at a lower speed. It has worked in all but 3 cases in hundreds of reads of pressed discs. One could not be read by anything and the error in the disc was clearly observable when viewing. The other two could be read by my 3500. As anyone who uses the Aopen for fast reads will also have a burner, that should give them a second chance at reading. Since my 3500 is not known for reading ability, I would have to assume that the discs the AOpen couldn’t read were flukes. As much as I would love to spend a few more bucks on some new toys, I have seen no reason to seek out one of those drives with “superior” reading ability (BenQ 1620 or Toshiba). In only one case has a rip proven to be corrupted. A second reading on the same AOpen was fine. I have to conclude that the fast ripping is not a problem.
I was thinking less along the lines of wether the rip was successfull and more along the lines of even if it is successfull, would the slower drive have less errors, or does error corection take care of that where the final output is the same if it is succesfully read? Its too bad my toshiba reader died if they are pretty good readers.
Thats great information guys. Thanks. I posted here due to the generic brand requests, and the fact that i wanted pricing and locales. I actually had the AOpen bookmarked as one of my finalists, good affirmation from this thread on that one. I usually encode through DVDShrink to my HD, then burn with Nero, and i have seen some who rip to the hard drive first. Does that improve speed? I would have to check on the cache on my drive, i dont remember what it is. Usually takes about 30-40 minutes to encode the movie. and 6-14 minutes to burn, depending on 4x or 8x.
@chas0039, I treat DVD Decrypter rips the same way. If it rips successfully, then I consider it good. I am curious tho, about what let you know that the one rip was corrupt? How did you know it was corrupt?
Before I burn I run the files through DVDShrink. The initial read seems to be a good check for errors as it has always been able to find a problem such as a missing file.
In this case it reported a crc error half way through. I now check all my files and burns this way. It is not perfect but it is fast and catches major read problems and burns with hidg PI/PIF errors. This was how I found out that my batch of Ritek R03s had turned bad in the middle of the stack.