A misbehavior report:
With a damaged but CTDB fixable rip that have an extra data file but don't have a log (so no length info):
If CT automatically finds the data track length & you try to repair it, after the reparing the rip is AR not found as it seems the data track length is not automatically applied after the reparing.
Exemple:
Damaged:
[CUETools log; Date: 28/10/11 12:33:19; Version: 2.1.2a]
CD-Extra data track length 32:53:50.
[CTDB TOCID: NSFKOWYhdRg5JvTHPsSbYUIVH6I-] found.
[ CTDBID ] Status
[205e81aa] (1/1) Differs in 12 samples @04:35:57
[AccurateRip ID: 000f1d51-007811a9-7f11af0a] found.
Track [ CRC ] Status
01 [251c8174] (2/2) Accurately ripped
02 [de2afa36] (0/2) No match but offset
03 [aaddb5c4] (2/2) Accurately ripped
04 [80eefc16] (2/2) Accurately ripped
05 [14ea8187] (2/2) Accurately ripped
06 [a78830c5] (2/2) Accurately ripped
07 [b96f1704] (2/2) Accurately ripped
08 [538cf213] (2/2) Accurately ripped
09 [987b6e4b] (2/2) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL]
-- 98,7 [31E95D45] [439F38B1]
01 59,7 [E28F0A65] [35FF4800]
02 98,7 [11C967E5] [49FA5025]
03 98,7 [56420A86] [0841F570]
04 98,7 [396F04C5] [BA7238A5]
05 98,7 [250AC844] [3EAFDFD3]
06 98,7 [405E456A] [D89DABCC]
07 98,7 [828BB200] [4C6E261F]
08 98,7 [9976F05A] [F8FA4991]
09 98,7 [4CECDF52] [36B60187]
After reparing:
[CUETools log; Date: 28/10/11 15:42:10; Version: 2.1.2a]
CD-Extra data track length 32:53:50.
CUETools DB: corrected 12 errors.
[AccurateRip ID: 000f1d51-007811a9-7f11af0a] disk not present in database.
Track Peak [ CRC32 ] [W/O NULL]
-- 98,7 [437B0988] [82B5FA4C]
01 59,7 [E28F0A65] [35FF4800]
02 98,7 [342F4426] [D9F55817]
03 98,7 [56420A86] [0841F570]
04 98,7 [396F04C5] [BA7238A5]
05 98,7 [250AC844] [3EAFDFD3]
06 98,7 [405E456A] [D89DABCC]
07 98,7 [828BB200] [4C6E261F]
08 98,7 [9976F05A] [F8FA4991]
09 98,7 [4CECDF52] [36B60187]
Should have been: (Manual re-verification of the same fixed data as above)
[CUETools log; Date: 28/10/11 15:43:50; Version: 2.1.2a]
CD-Extra data track length 32:53:50.
[CTDB TOCID: NSFKOWYhdRg5JvTHPsSbYUIVH6I-] found.
[ CTDBID ] Status
[205e81aa] (1/1) Accurately ripped
[AccurateRip ID: 000f1d51-007811a9-7f11af0a] found.
Track [ CRC ] Status
01 [251c8174] (2/2) Accurately ripped
02 [9c754a56] (2/2) Accurately ripped
03 [aaddb5c4] (2/2) Accurately ripped
04 [80eefc16] (2/2) Accurately ripped
05 [14ea8187] (2/2) Accurately ripped
06 [a78830c5] (2/2) Accurately ripped
07 [b96f1704] (2/2) Accurately ripped
08 [538cf213] (2/2) Accurately ripped
09 [987b6e4b] (2/2) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL]
-- 98,7 [437B0988] [82B5FA4C]
01 59,7 [E28F0A65] [35FF4800]
02 98,7 [342F4426] [D9F55817]
03 98,7 [56420A86] [0841F570]
04 98,7 [396F04C5] [BA7238A5]
05 98,7 [250AC844] [3EAFDFD3]
06 98,7 [405E456A] [D89DABCC]
07 98,7 [828BB200] [4C6E261F]
08 98,7 [9976F05A] [F8FA4991]
09 98,7 [4CECDF52] [36B60187]
Not that it matters much if you are aware of it, but it is missleading as I could have thought that my rip wasn't fixed if I would not have manually re-verified.