![]() It cannot do a better job of matching than the mathematics allow and the data and information available. The addition of the CTDB actually makes CueTools/CueRipper and EAC with the CTDB plugin more useful for verifying rips than dBpoweramp alone.Ĭlick to expand.I am certain that CueTools is doing the best that it can to find matches within the constraints of the AccurateRip algorithms and mathematics. CTDB often has more results in it for CDs, especially for newly released CDs, than AccurateRip. CueTools also has the advantage of its own CTDB for verifying rips. I haven't noticed any problems or false negatives. If it doesn't know the offset then it is going to find fewer matches.ĬueTools is working fine in my use of CueTools. That drive offset needs to be taken into account when finding matches. ![]() CueTools also has a more challenging job in finding matches if it doesn't know the offset of the drive that originally ripped the files. And there is a difference between AccurateRip version 1 and AccurateRip version 2 in the way matches can be found and the number of matches to different pressings (offsets). Both are just as accurate and just as useful for verifying the rip.ĭBpoweramp and CueTools report AccurateRip numbers differently. It doesn't matter if it finds a match with only 4 other rips or 204 other rips. Click to expand.False negatives are not a problem at all.
0 Comments
Leave a Reply. |