I have found the commandline tool ArCueDotNet.exe in the installation folder of CueTools and it works
e.g.: -o65
uses the offset 65 (and calculates V2 for this offset)
o without offset declaration: -o
calculates the V2 value for all detected offsets (like running ArCueDotNet multiple times with -o<offset1>, -o<offset2>, ...). This is usefull to see the best offset for a Rip without "Read offset correction".
I would find that to be useful for some of my albums. Moreover, would there be a way to add --verbose to "CUETools.exe /verify" mode? Here is the output of ArCueDotNet.exe with -v option:
[CUETools log; Date: 28/02/2015 04:42:21; Version: 2.1.5]
[CTDB TOCID: LAKiIVhc1gSqZ8BE.7VGBxXwMaE-] found.
[ CTDBID ] Status
[5c7170fc] (19/21) Accurately ripped
[bb2246f5] (01/21) No match
[5db9fe31] (01/21) No match
Track | CTDB Status
1 | (19/21) Accurately ripped
2 | (20/21) Accurately ripped
3 | (20/21) Accurately ripped
4 | (20/21) Accurately ripped
5 | (20/21) Accurately ripped
6 | (20/21) Accurately ripped
7 | (20/21) Accurately ripped
8 | (20/21) Accurately ripped
9 | (20/21) Accurately ripped
10 | (20/21) Accurately ripped
11 | (20/21) Accurately ripped
12 | (20/21) Accurately ripped
[AccurateRip ID: 0019e705-00f3b536-9e0e480c] found.
Track [ CRC | V2 ] Status
01 [54d5b239|8c859a29] (07+12/22) Accurately ripped
02 [9abaa277|446f813f] (07+13/23) Accurately ripped
03 [e671a3ee|df8aefac] (07+12/22) Accurately ripped
04 [131645c5|08404059] (07+13/23) Accurately ripped
05 [fa677611|1fcf6226] (07+12/21) Accurately ripped
06 [a48fb312|abf5ba0c] (07+13/22) Accurately ripped
07 [482b2273|1371a315] (07+12/22) Accurately ripped
08 [061ecc0d|40eb99d7] (07+12/22) Accurately ripped
09 [a9a43e39|455299f8] (07+12/22) Accurately ripped
10 [c5d77042|4c99c432] (07+12/22) Accurately ripped
11 [5e115af1|060f38c5] (07+12/21) Accurately ripped
12 [9504d38d|fd07e8a8] (07+13/22) Accurately ripped
Offsetted by -664:
01 [cb3b9709] (03/22) Accurately ripped
02 [9df3c3be] (03/23) Accurately ripped
03 [19dbfde0] (03/22) Accurately ripped
04 [217183dd] (03/23) Accurately ripped
05 [34245dad] (02/21) Accurately ripped
06 [7ead2d66] (02/22) Accurately ripped
07 [e3a0ad42] (03/22) Accurately ripped
08 [38bcafa1] (03/22) Accurately ripped
09 [2c2d1bae] (03/22) Accurately ripped
10 [ffd9b6c1] (03/22) Accurately ripped
11 [3b71ecd8] (02/21) Accurately ripped
12 [efd1a32c] (02/22) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 99,9 [EF433381] [26CF379B]
01 98,9 [C27A1E39] [CEEB2201] CRC32
02 93,4 [AB077A50] [FED0030F] CRC32
03 93,4 [3A917A0E] [FD08F022] CRC32
04 99,9 [9126A647] [9DD38039] CRC32
05 99,9 [7CF0263A] [37888463] CRC32
06 99,9 [9DFFF022] [BA5F9850] CRC32
07 99,9 [DA170E31] [6C559762] CRC32
08 99,9 [EA488401] [68C255C0] CRC32
09 99,9 [846B12B2] [93950B27] CRC32
10 89,1 [9B55BB04] [309042ED] CRC32
11 99,9 [CBBEA6BA] [34C34B04] CRC32
12 99,9 [B8A9843C] [D100069D] CRC32
Here is the output of CUETools.exe with /verify option:
[CUETools log; Date: 28/02/2015 04:44:29; Version: 2.1.5]
[AccurateRip ID: 0019e705-00f3b536-9e0e480c] found.
Track [ CRC | V2 ] Status
01 [54d5b239|8c859a29] (07+12/22) Accurately ripped
02 [9abaa277|446f813f] (07+13/23) Accurately ripped
03 [e671a3ee|df8aefac] (07+12/22) Accurately ripped
04 [131645c5|08404059] (07+13/23) Accurately ripped
05 [fa677611|1fcf6226] (07+12/21) Accurately ripped
06 [a48fb312|abf5ba0c] (07+13/22) Accurately ripped
07 [482b2273|1371a315] (07+12/22) Accurately ripped
08 [061ecc0d|40eb99d7] (07+12/22) Accurately ripped
09 [a9a43e39|455299f8] (07+12/22) Accurately ripped
10 [c5d77042|4c99c432] (07+12/22) Accurately ripped
11 [5e115af1|060f38c5] (07+12/21) Accurately ripped
12 [9504d38d|fd07e8a8] (07+13/22) Accurately ripped
Offsetted by -664:
01 [cb3b9709] (03/22) Accurately ripped
02 [9df3c3be] (03/23) Accurately ripped
03 [19dbfde0] (03/22) Accurately ripped
04 [217183dd] (03/23) Accurately ripped
05 [34245dad] (02/21) Accurately ripped
06 [7ead2d66] (02/22) Accurately ripped
07 [e3a0ad42] (03/22) Accurately ripped
08 [38bcafa1] (03/22) Accurately ripped
09 [2c2d1bae] (03/22) Accurately ripped
10 [ffd9b6c1] (03/22) Accurately ripped
11 [3b71ecd8] (02/21) Accurately ripped
12 [efd1a32c] (02/22) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 99,9 [EF433381] [26CF379B]
01 98,9 [C27A1E39] [CEEB2201] CRC32
02 93,4 [AB077A50] [FED0030F] CRC32
03 93,4 [3A917A0E] [FD08F022] CRC32
04 99,9 [9126A647] [9DD38039] CRC32
05 99,9 [7CF0263A] [37888463] CRC32
06 99,9 [9DFFF022] [BA5F9850] CRC32
07 99,9 [DA170E31] [6C559762] CRC32
08 99,9 [EA488401] [68C255C0] CRC32
09 99,9 [846B12B2] [93950B27] CRC32
10 89,1 [9B55BB04] [309042ED] CRC32
11 99,9 [CBBEA6BA] [34C34B04] CRC32
12 99,9 [B8A9843C] [D100069D] CRC32
----------------------------------------------------------
As you can see, this second mode misses many good CTDB infos. Anyway, it would be cool for stats to include an option to add the [ CRC32 ] [W/O NULL] columns for each different pressing (calculated at different offsets). It could take longer to elaborate, but one could choose to deactivate the option.