Yesterday I was surprised, I thought Cuetools was able to verify pressings with different offset automatically and I realized it was not always the case.
Before fixing the offset manually: (Not accurate)
[CUETools log; Date: 20/07/2016 06:01:28; Version: 2.1.6]
[CTDB TOCID: FJE5bHuttMI.k7ZJG_ShMtRgoNo-] found.
[ CTDBID ] Status
[4960160e] (16/16) Accurately ripped
Track | CTDB Status
1 | (16/16) Accurately ripped
2 | (16/16) Accurately ripped
3 | (16/16) Accurately ripped
4 | (16/16) Accurately ripped
5 | (16/16) Accurately ripped
6 | (16/16) Accurately ripped
7 | (16/16) Accurately ripped
8 | (16/16) Accurately ripped
9 | (16/16) Accurately ripped
10 | (16/16) Accurately ripped
11 | (16/16) Accurately ripped
12 | (16/16) Accurately ripped
13 | (16/16) Accurately ripped
14 | (16/16) Accurately ripped
15 | (16/16) Accurately ripped
16 | (16/16) Accurately ripped
17 | (16/16) Accurately ripped
[AccurateRip ID: 0025e3fc-01ebb30d-e70fa511] found.
Track [ CRC | V2 ] Status
01 [1119c2ae|5c8a5a62] (0+0/4) No match
02 [4a4667c4|489a7912] (0+0/4) No match
03 [17f79a3c|e7085aa5] (0+0/4) No match
04 [bba8b337|91d1d4b8] (0+0/4) No match
05 [20c25d31|6ccba031] (0+0/4) No match
06 [900ca1dc|f061f75d] (0+0/4) No match
07 [1473cf38|d62bb70b] (0+0/4) No match
08 [155dac0e|de8857f3] (0+0/4) No match
09 [4dc0b8f8|f7e792ee] (0+0/4) No match
10 [5c3bda5f|8412677b] (0+0/4) No match
11 [96f35c77|f7ef8664] (0+0/4) No match
12 [ae06e6ba|71d5f14c] (0+0/4) No match
13 [73db24ce|69fd7ede] (0+0/4) No match
14 [f37febc9|3ca717d3] (0+0/4) No match
15 [fb719bd0|b05afe4d] (0+0/4) No match
16 [1d5413c7|33b843f6] (0+0/4) No match
17 [71e6694d|b31d295f] (0+0/4) No match
Offsetted by 667:
01 [f4b37882] (0/4) No match (V2 was not tested)
02 [19bfc8ac] (0/4) No match (V2 was not tested)
03 [18482812] (0/4) No match (V2 was not tested)
04 [0ba29c5e] (0/4) No match (V2 was not tested)
05 [f78bf496] (0/4) No match (V2 was not tested)
06 [4dfdfe3c] (0/4) No match (V2 was not tested)
07 [d3b8b914] (0/4) No match (V2 was not tested)
08 [f4de77f4] (0/4) No match (V2 was not tested)
09 [0d5abad6] (0/4) No match (V2 was not tested)
10 [b0e8e9d5] (0/4) No match (V2 was not tested)
11 [3f125ab3] (0/4) No match (V2 was not tested)
12 [5882633b] (0/4) No match (V2 was not tested)
13 [e2fdca3b] (0/4) No match (V2 was not tested)
14 [60b05e38] (0/4) No match (V2 was not tested)
15 [9cc72543] (0/4) No match (V2 was not tested)
16 [dcac27da] (0/4) No match (V2 was not tested)
17 [1bc80690] (0/4) No match (V2 was not tested)
Track Peak [ CRC32 ] [W/O NULL]
-- 100,0 [D790BC83] [EBD10AB9]
01 98,8 [5A304890] [9D1CDDFA]
02 98,8 [ABED67C9] [8BBEE65F]
03 98,8 [EC11C3D8] [E0D4AD23]
04 98,8 [664C7EB4] [8A64C043]
05 98,8 [37A9D3D9] [103B3090]
06 98,8 [DFE5262B] [378BDFF5]
07 98,8 [E0765CC3] [E3921E80]
08 98,8 [04E4EE5C] [FB09F0D8]
09 98,7 [1BB4C16E] [11BBBF09]
10 98,8 [FCDFB00E] [44299CCA]
11 98,8 [08892148] [C0E24480]
12 98,8 [F88319F3] [52C69A3A]
13 100,0 [3A3F14EE] [0B3EB7DE]
14 98,8 [1274678F] [98350307]
15 98,8 [FED211D7] [EE3F9CB0]
16 98,8 [CE3261CA] [0D3C74B2]
17 98,8 [FA20A189] [97703284]
After fixing the offset manually (Accurate) :
[CUETools log; Date: 20/07/2016 18:18:46; Version: 2.1.6]
Offset applied: 667
[CTDB TOCID: FJE5bHuttMI.k7ZJG_ShMtRgoNo-] found.
[ CTDBID ] Status
[4960160e] (16/16) Accurately ripped
Track | CTDB Status
1 | (16/16) Accurately ripped
2 | (16/16) Accurately ripped
3 | (16/16) Accurately ripped
4 | (16/16) Accurately ripped
5 | (16/16) Accurately ripped
6 | (16/16) Accurately ripped
7 | (16/16) Accurately ripped
8 | (16/16) Accurately ripped
9 | (16/16) Accurately ripped
10 | (16/16) Accurately ripped
11 | (16/16) Accurately ripped
12 | (16/16) Accurately ripped
13 | (16/16) Accurately ripped
14 | (16/16) Accurately ripped
15 | (16/16) Accurately ripped
16 | (16/16) Accurately ripped
17 | (16/16) Accurately ripped
[AccurateRip ID: 0025e3fc-01ebb30d-e70fa511] found.
Track [ CRC | V2 ] Status
01 [f4b37882|33435413] (0+4/4) Accurately ripped
02 [19bfc8ac|0984b049] (0+4/4) Accurately ripped
03 [18482812|d44093d6] (0+4/4) Accurately ripped
04 [0ba29c5e|ec114523] (0+4/4) Accurately ripped
05 [f78bf496|3d6ed076] (0+4/4) Accurately ripped
06 [4dfdfe3c|5be027bd] (0+4/4) Accurately ripped
07 [d3b8b914|86942f6e] (0+4/4) Accurately ripped
08 [f4de77f4|b7fae96d] (0+4/4) Accurately ripped
09 [0d5abad6|8db9a53e] (0+4/4) Accurately ripped
10 [b0e8e9d5|1a74c90a] (0+4/4) Accurately ripped
11 [3f125ab3|9fc472ac] (0+4/4) Accurately ripped
12 [5882633b|1868d81b] (0+4/4) Accurately ripped
13 [e2fdca3b|d5ddf15d] (0+4/4) Accurately ripped
14 [60b05e38|a061772e] (0+4/4) Accurately ripped
15 [9cc72543|75bc2576] (0+4/4) Accurately ripped
16 [dcac27da|f788f3ef] (0+4/4) Accurately ripped
17 [1bc80690|3ad45fbd] (0+4/4) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL]
-- 100,0 [3DAFCCF6] [EBD10AB9]
01 98,8 [47F69EA5] [7D6BB354]
02 98,8 [3AFEB0FE] [E8C695D5]
03 98,8 [2E3FFF18] [1DA7215B]
04 98,8 [A88A6210] [DEC72C5E]
05 98,8 [8499EDB3] [5D786BAE]
06 98,8 [E793291F] [B260FA5B]
07 98,8 [E2444CD0] [EABB0EE8]
08 98,8 [D0E24621] [45EEBC97]
09 98,7 [B4685EED] [55DB28CE]
10 98,8 [81A5A9D4] [01E48252]
11 98,8 [422329BF] [72E0357E]
12 98,8 [59BA900F] [F3F3368B]
13 100,0 [3D90862C] [E4340417]
14 98,8 [83F3F19B] [68D4FCF6]
15 98,8 [B0AD8226] [C05CF207]
16 98,8 [AA15B1DE] [2E26F637]
17 98,8 [9C74A495] [92DE76A7]
Is this normal ? I thought Cuetools was able to check a rip with a bad offset automatically ... Is it just me who was wrong assuming Cuetools could do it ? I was kinda shocked as I may have deleted a bunch of perfectly valid rips due to my assumption ...
Quote from Cuetools Wiki:
The unique feature of CUETools AccurateRip verification is offset detection. A rip that was made without offset correction can still be verified against the database; the offset can be found and corrected.