QUOTE
So I'm guessing AccurateRip does not look for matching records with different offsets, but CTDB does. Is this correct?
EAC's built-in AccurateRip app doesn't check ARv1 at other offsets. I have not experienced it checking ARv2 at other offsets.The CTDB stores one record for all offsets so The EAC CTDB plugin doesn't need to check CTDB at other offsets.
QUOTE
The CTDB plugin for EAC must not tell you in the EAC rip log when your rip had to be offset to match any database records. For example, for the Zelda CD I initially posted about, it reported "(7/7) Accurately ripped" for each track except the bad one, but it wasn't until after processing the tracks with CUETools and looked at the .accurip log that I learned an offset was required to find any matching records in the database.
The EAC CTDB plugin only contacts CTDB (CUETools database). EAC's built-in AccurateRip app only contacts the AccurateRip database. The EAC CTDB plugin and EAC's built-in AccurateRip app don't share data.The CUETools app can contact both the AccurateRip database and CTDB (CUETools database). The CUETools app can check ARv1 at other offsets. The CUETools app can not check ARv2 at other offsets.