Hey guys, I just downloaded a flac file I verified with CT (as always) which turned out to be a "no match but offset" one.
[CUETools log; Date: 22/12/2011 1:43:39; Version: 2.1.2a]
[CTDB TOCID: q.J5giMFoJd0kQr3cHgcHLEkh7s-] disk not present in database.
[AccurateRip ID: 000fed5b-006fb89e-6e098309] found.
Track [ CRC ] Status
01 [de1e3119] (0/1) No match
02 [03693299] (0/1) No match
03 [062b2a55] (0/1) No match
04 [9504aee9] (0/1) No match
05 [af53be68] (0/1) No match
06 [9e7138e5] (0/1) No match
07 [55dd40f2] (0/1) No match
08 [7065ff8a] (0/1) No match
09 [0aead0ac] (0/1) No match
Offsetted by -24:
01 [ae80cc09] (0/1) No match but offset
02 [87947cc1] (0/1) No match but offset
03 [20946c45] (0/1) No match but offset
04 [ea57ba99] (0/1) No match but offset
05 [69917058] (0/1) No match but offset
06 [55f7c0dd] (0/1) No match but offset
07 [142944ea] (0/1) No match but offset
08 [2e5f2af2] (0/1) No match but offset
09 [1396e04c] (0/1) No match but offset
Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 100,0 [93962B01] [47181DCC] CRC32
01 96,6 [C19C5852] [9A9B82D7]
02 100,0 [5AB35513] [7237144A]
03 98,0 [D3545233] [02FF9787]
04 98,3 [1F1F7C47] [489EB4AE]
05 97,9 [F6A1F5E0] [C9E2C524]
06 98,2 [7A2F2D39] [20D741B3]
07 97,2 [012EE406] [65418D67]
08 95,8 [A497CE45] [E95C3C68]
09 97,2 [CA6013F4] [1705EC9C]
Well, I ended up burning anyways, offset-correcting in the meantime.
With this my "brand new" CD I repeated the process of ripping & verifying, BUT... now it turned out to be "accurately ripped".
[CUETools log; Date: 01/01/2012 3:10:10; Version: 2.1.2a]
[CTDB TOCID: q.J5giMFoJd0kQr3cHgcHLEkh7s-] disk not present in database.
[AccurateRip ID: 000fed5b-006fb89e-6e098309] found.
Track [ CRC ] Status
01 [ae80cc09] (0/1) No match but offset
02 [87947cc1] (0/1) No match but offset
03 [20946c45] (0/1) No match but offset
04 [ea57ba99] (0/1) No match but offset
05 [69917058] (0/1) No match but offset
06 [55f7c0dd] (0/1) No match but offset
07 [142944ea] (0/1) No match but offset
08 [2e5f2af2] (0/1) No match but offset
09 [1396e04c] (0/1) No match but offset
AccurateRip v2:
01 [cff94e79] (1/1) Accurately ripped
02 [9d16df24] (1/1) Accurately ripped
03 [3d30d8f8] (1/1) Accurately ripped
04 [08b4a99a] (1/1) Accurately ripped
05 [df62cb36] (1/1) Accurately ripped
06 [77080667] (1/1) Accurately ripped
07 [9a55ed90] (1/1) Accurately ripped
08 [34e7f011] (1/1) Accurately ripped
09 [40d8ff09] (1/1) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 100,0 [D079E009] [47181DCC] CRC32
01 96,6 [4D444A54] [9A9B82D7]
02 100,0 [D843C366] [7237144A]
03 98,0 [F3E83C36] [02FF9787]
04 98,3 [6F92B98A] [489EB4AE]
05 97,9 [497DC845] [C9E2C524]
06 98,2 [365EF879] [20D741B3]
07 97,2 [11BFDF1F] [65418D67]
08 95,8 [C3D27F4A] [E95C3C68]
09 97,2 [C0B98852] [1705EC9C]
Can someone tell me why doesn't CT warn of this ARv2 match for the offset(-24) instead of stating this misleading message.
I've been discarding all those "no match but offset" since long ago taking them for bad rips, and now I suddenly come across they were all probably good.
Thanks in advance!