I just saw that V2.09 was actually released so I tested it ... I succesfully submitted a rip with an empty track to CTDB so that part worked ... but after that I tried to "fix" another rip & I had a strange result: all tracks are now reported as accurate in the .accurip log but the batch log still concludes that the whole rip is not accurate & so the whole offset fixing didn't start, then I tried to upload that "bad" rip ... & it was accepted (Edit: The first time I didn't check if the whole rip was accurate in the batch log before being accepted, despite being accepted it "wasn't accurate" in batch log too I just re-checked):
Batch log: Bad hence "offset not fixable" with my filter
CDImage.cue: AR: rip not accurate (16/16).
Bad but submitted
CDImage.cue: AR: rip not accurate (16/16), CTDB: disk not present in database, zImXwBUC_ZGAOhJghadou315CbE- has been uploaded.
.accurip log: Good but should have been "fixed" by +66 if [00000000] tracks would have been ignored.
[CUETools log; Date: 18/05/2010 20:23:30; Version: 2.0.9]
[AccurateRip ID: 0032ca87-03021fa3-4909bb17] found.
Track [ CRC ] Status
01 [25b0fccd] (05/19) Accurately ripped
02 [f926c883] (05/19) Accurately ripped
03 [3220d10e] (05/19) Accurately ripped
04 [0b9512be] (05/19) Accurately ripped
05 [0bd9f5a4] (05/19) Accurately ripped
06 [b695892c] (05/19) Accurately ripped
07 [59d33144] (05/19) Accurately ripped
08 [9ef4928e] (05/19) Accurately ripped
09 [beee4d2c] (05/19) Accurately ripped
10 [a82efa2d] (05/19) Accurately ripped
11 [4b5fb83b] (06/20) Accurately ripped
12 [00000000] (00/00) Accurately ripped
13 [00000000] (00/00) Accurately ripped
14 [00000000] (00/00) Accurately ripped
15 [00000000] (00/00) Accurately ripped
16 [00000000] (00/00) Accurately ripped
17 [00000000] (00/00) Accurately ripped
18 [00000000] (00/00) Accurately ripped
19 [00000000] (00/00) Accurately ripped
20 [00000000] (00/00) Accurately ripped
21 [00000000] (00/00) Accurately ripped
22 [00000000] (00/00) Accurately ripped
23 [09c3e978] (05/16) Accurately ripped
Offsetted by 66:
01 [4c7144a7] (14/19) Accurately ripped
02 [6999bd94] (14/19) Accurately ripped
03 [efc0b09a] (14/19) Accurately ripped
04 [a3b20f25] (14/19) Accurately ripped
05 [b62a4303] (14/19) Accurately ripped
06 [131b76eb] (14/19) Accurately ripped
07 [2716707c] (14/19) Accurately ripped
08 [5122279f] (14/19) Accurately ripped
09 [bcefe72c] (14/19) Accurately ripped
10 [183f759e] (14/19) Accurately ripped
11 [469135c7] (14/20) Accurately ripped
12 [00000000] (00/00) Accurately ripped
13 [00000000] (00/00) Accurately ripped
14 [00000000] (00/00) Accurately ripped
15 [00000000] (00/00) Accurately ripped
16 [00000000] (00/00) Accurately ripped
17 [00000000] (00/00) Accurately ripped
18 [00000000] (00/00) Accurately ripped
19 [00000000] (00/00) Accurately ripped
20 [00000000] (00/00) Accurately ripped
21 [00000000] (00/00) Accurately ripped
22 [00000000] (00/00) Accurately ripped
23 [ea572e0b] (11/16) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL]
-- 100,0 [02D97771] [08042A49]
01 100,0 [1D2F1FB9] [F51F0F51]
02 100,0 [2553F3A4] [523834A1]
03 100,0 [A7A5FC78] [4912C60B]
04 100,0 [5E7313D1] [92089105]
05 100,0 [2E581386] [E97B4DCA]
06 100,0 [B05D8912] [796EE265]
07 100,0 [C1AF8AA1] [3FE268F4]
08 100,0 [D9805A37] [8FD46487]
09 100,0 [97FB0799] [DFB237D8]
10 100,0 [CDAEDC9F] [E7A1BCEC]
11 100,0 [790C0F58] [9E32BA87]
12 0,0 [6E375D99] [00000000]
13 0,0 [6E375D99] [00000000]
14 0,0 [6E375D99] [00000000]
15 0,0 [6E375D99] [00000000]
16 0,0 [6E375D99] [00000000]
17 0,0 [6E375D99] [00000000]
18 0,0 [6E375D99] [00000000]
19 0,0 [6E375D99] [00000000]
20 0,0 [6E375D99] [00000000]
21 0,0 [6E375D99] [00000000]
22 0,0 [6E375D99] [00000000]
23 73,3 [AE335FE7] [ED630E95]
... there is actually a problem of logic in the way things are reported IMHO
Edit: Also instead of "Accurately ripped" reporting as "Silent track" would IMHO be better for newbies which doesn't understand what [00000000] means.
Edit2: If you want to be even more precise & make a difference between silent track with data (not empty) & silent track without data (empty), maybe someting like "Empty track" or "No data" would work too. I don't know if the precision is really usefull.