With the CTDB plugin installed and enabled, does EAC check both CTDB and AccurateRip after a rip, or does it only check one database? Is there a way to get EAC to check both?With
but how will I know whether CTDB has been checked?
If CTDB finds an error, will I be prompted to use its error-correction feature, or do I have to do something manually in EAC?
All tracks accurately ripped <--- IS THIS BASED ON CTDB OR ACCURATERIP?
All tracks accurately rippedNo errors occurredEnd of status report---- CUETools DB Plugin V2.1.4[CTDB TOCID: C8BYPUqGce7nqTyd1e6JwfA0_cE-] foundSubmit result: C8BYPUqGce7nqTyd1e6JwfA0_cE- has been confirmedTrack | CTDB Status 1 | (1/2) Accurately ripped 2 | (1/2) Accurately ripped 3 | (1/2) Accurately ripped 4 | (1/2) Accurately ripped 5 | (1/2) Accurately ripped 6 | (1/2) Accurately ripped 7 | (1/2) Accurately ripped 8 | (1/2) Accurately ripped 9 | (1/2) Accurately ripped 10 | (1/2) Accurately ripped 11 | (1/2) Accurately ripped
I'm still having the issue after installing the newer version of the plugin
OS is Windows 7.
So does this really mean that those tracks just aren't in the database at all
or are my rips too inaccurate? The CD isn't in that bad of shape.
This CD contains tracks that may be identical to tracks from a previously released album by the same artist, so could CTDB be comparing them to the tracks from the other album, which might be in the database, and that is why only some tracks could be verified? Or does CTDB not compare tracks from different albums?
All tracks were verified by AccurateRip with confidence 5. I worry that 5 could be from when I ripped the same CD in EAC years ago, but I never previously clicked "Send AccurateRip Results..." in EAC. So:A) Does "Send AccurateRip Results..." send the CRCs of my rips to EAC?B) If so, then the other entries in the database probably are not mine unless previous versions of EAC would automatically submit CRCs, because I never clicked "Send AccurateRip Results..." in the past.
To clarify things for me: do the "Start" and "End" columns in the database records refer to the positions on the CD where the ripped tracks begin/end?
If none of them had any gaps to speak of, why weren't all the tracks other than Track 1 "Accurately ripped"? And some of them were "Accurately ripped", so.... is it possible that the other guy actually had a bunch of badly ripped tracks? Mine were all verified by AccurateRip.
(....Or, from an entirely different angle: Could the difference between the two rips have something to do with the fact that I didn't configure EAC to overread into the lead-in and lead-out? My drive is supposedly only 6 frames off, though, not 32.)