There is one thing I haven't understood about track CRC and AccurateRip. I have two different rips of the same CD, one correctly ripped, and the other not:
Correctly ripped:
[CUETools log; Date: 23/07/2015 12:03:24; Version: 2.1.5]
[CTDB TOCID: oIvFX8j3CpjAXxoaG80nqUK0sRI-] found.
[ CTDBID ] Status
[286d9cba] (5/5) Accurately ripped
Track | CTDB Status
1 | (5/5) Accurately ripped
2 | (5/5) Accurately ripped
3 | (5/5) Accurately ripped
4 | (5/5) Accurately ripped
5 | (5/5) Accurately ripped
6 | (5/5) Accurately ripped
7 | (5/5) Accurately ripped
8 | (5/5) Accurately ripped
9 | (5/5) Accurately ripped
10 | (5/5) Accurately ripped
11 | (5/5) Accurately ripped
12 | (5/5) Accurately ripped
[AccurateRip ID: 000ff65b-00955d8f-ad08480c] found.
Track [ CRC | V2 ] Status
01 [4f456a67|3e590718] (09+03/12) Accurately ripped
02 [f079bd04|bb12e9e8] (09+03/12) Accurately ripped
03 [72d0cc94|1125ef9a] (09+03/12) Accurately ripped
04 [1e85ebc6|7a5e12d2] (09+03/12) Accurately ripped
05 [05eaecaf|4f5c6b35] (09+03/12) Accurately ripped
06 [c5a58f8c|10c53a0d] (09+03/12) Accurately ripped
07 [334a8e1f|7efe2f01] (09+03/12) Accurately ripped
08 [b07a89df|4ccede9b] (09+03/12) Accurately ripped
09 [f48a8a88|01c65c41] (09+03/12) Accurately ripped
10 [dd520537|d0a55829] (09+03/12) Accurately ripped
11 [723d9e81|e9830e6a] (09+03/12) Accurately ripped
12 [8b21c427|658f465f] (09+03/12) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 96,2 [07D56C06] [D236334F]
01 96,2 [22FA457E] [E8BD2508] CRC32
02 90,7 [C6564A4E] [E12258B1] CRC32
03 67,7 [87F2D289] [DF1176FA] CRC32
04 87,2 [D21518EC] [0E7CC3BC] CRC32
05 91,8 [5E97A1D2] [9BF975D0] CRC32
06 90,8 [9E4ABAC0] [061F95E8] CRC32
07 81,3 [2178157E] [B5E4E176] CRC32
08 94,7 [D9139206] [C7C4CB66] CRC32
09 82,9 [08C2AFC6] [E05B2F45] CRC32
10 61,3 [7C672F27] [AD4A17BB] CRC32
11 90,6 [EC97E162] [B3BCEBF9] CRC32
12 95,7 [21390958] [096678BB] CRC32
Not correctly ripped (+690 offset applied):
[CUETools log; Date: 23/07/2015 12:08:55; Version: 2.1.5]
Offset applied: 690
[CTDB TOCID: oIvFX8j3CpjAXxoaG80nqUK0sRI-] found.
[ CTDBID ] Status
[286d9cba] (5/5) Differs in 1175 samples @06:51:41-06:51:42
Track | CTDB Status
1 | (5/5) Accurately ripped
2 | (5/5) Accurately ripped
3 | (5/5) Differs in 1175 samples @01:11:19-01:11:20
4 | (5/5) Accurately ripped
5 | (5/5) Accurately ripped
6 | (5/5) Accurately ripped
7 | (5/5) Accurately ripped
8 | (5/5) Accurately ripped
9 | (5/5) Accurately ripped
10 | (5/5) Accurately ripped
11 | (5/5) Accurately ripped
12 | (5/5) Accurately ripped
[AccurateRip ID: 000ff65b-00955d8f-ad08480c] found.
Track [ CRC | V2 ] Status
01 [4f456a67|3e590718] (09+03/12) Accurately ripped
02 [f079bd04|bb12e9e8] (09+03/12) Accurately ripped
03 [9147d31b|3442a2e7] (00+00/12) No match
04 [1e85ebc6|7a5e12d2] (09+03/12) Accurately ripped
05 [05eaecaf|4f5c6b35] (09+03/12) Accurately ripped
06 [c5a58f8c|10c53a0d] (09+03/12) Accurately ripped
07 [334a8e1f|7efe2f01] (09+03/12) Accurately ripped
08 [b07a89df|4ccede9b] (09+03/12) Accurately ripped
09 [f48a8a88|01c65c41] (09+03/12) Accurately ripped
10 [dd520537|d0a55829] (09+03/12) Accurately ripped
11 [723d9e81|e9830e6a] (09+03/12) Accurately ripped
12 [8b21c427|658f465f] (09+03/12) Accurately ripped
Track Peak [ CRC32 ] [W/O NULL] [ LOG ]
-- 96,2 [0306A90C] [DE3DF86A]
01 96,2 [22FA457E] [E8BD2508] [2938E6DF]
02 90,7 [C6564A4E] [E12258B1] W/O NULL
03 67,7 [B64DBD16] [B2D0F2EE] [DF1176FA]
04 87,2 [D21518EC] [0E7CC3BC] W/O NULL
05 91,8 [5E97A1D2] [9BF975D0] W/O NULL
06 90,8 [9E4ABAC0] [061F95E8] W/O NULL
07 81,3 [2178157E] [B5E4E176] W/O NULL
08 94,7 [D9139206] [C7C4CB66] W/O NULL
09 82,9 [08C2AFC6] [E05B2F45] W/O NULL
10 61,3 [7C672F27] [AD4A17BB] W/O NULL
11 90,6 [EC97E162] [B3BCEBF9] W/O NULL
12 95,7 [C2B0B206] [20BC2A99] W/O NULL
Don't worry about track 03, please notice the last track (nr. 12) CRCs, instead:
Correct: 12 95,7 [21390958] [096678BB] CRC32
Not corect: 12 95,7 [C2B0B206] [20BC2A99] W/O NULL
As you can see, the last track CRCs are different, while the other CRCs are the same (supposing track 03 was ripped correctly). Example:
Correct: 11 90,6 [EC97E162] [B3BCEBF9] CRC32
Not correct: 11 90,6 [EC97E162] [B3BCEBF9] W/O NULL
However, AccurateRip CRCs are the same for track 12:
Correct: 12 [8b21c427|658f465f] (09+03/12) Accurately ripped
Not correct: 12 [8b21c427|658f465f] (09+03/12) Accurately ripped
My question are:
1) Why does this happen? Or, why last track of different rips may have different CRC, but AccurateRip value is the same?
2) Why, in some other rips with different read offset, every track have the same CRC, including the last one, instead?
3) Why sometimes the only track with a different CRC, but again with identical AccurateRip value, is the first one of the album, and not the last one? It seems to depend on the applied offset anyway, with different results if it is positive or negative (positive offset = different CRC only last track, negative offset = different CRC only first track).
I hope my questions are clear.