iTunes Settings for High-Quality AAC
Reply #19 – 2012-12-18 15:51:35
So from an accuracy standpoint, is the only real difference between the two the number of times they re-read when errors are detected? Possibly, but with both AccurateRip and CTDB confirmation, you still know whether it's securely ripped or not.In addition, CUERipper comes with CUETools Database compatibility built-in. I read that this database provides the "ability not only to detect, but also correct small amounts of errors that occurred in the ripping process". Would anyone be able to comment on this feature? I like the idea that I can somehow perfect my imperfect rips, but what are the chances that the database provides data from an imperfect rip and screws up my own rip? Don't worry - you can easily check with CueTools, which will verify it against the Accurate Rip database too. Then it should be correct in both. Also, CTDB requires secure ripping to accept data from another rip and the correction information is independent of the offset used, so even a wrong offset should be OK. Also CTDB, not having so many options, is hard to set up wrong. EAC, by contrast, has plenty of options that can screw up your ripping if wrongly set (e.g. wrong cache size, use drive's flawed C2 info), and having a CTDB plugin it can submit rips to CTDB, which I guess could be the result of a bad setup. Nonetheless, AR and CTDB will be pretty good confirmation.