An attempt to interpret AccurateRip results given by CUETools
Reply #6 – 2009-04-03 07:47:16
I totally agree with you on the red results, I consider them as unknown. So I rely on the EAC log because it's better than nothing. For AR2, I hope that this will helps accuraterip in case it tells you that all your tracks are accurately ripped somewhere in the log, but ties these accurate results to two different pressings within the same offset. 5 of my logs are like this, if all accurately ripped tracks would be tied to a particular offset, as far as I understund, it would help identify a particular pressing, so tracks from different pressings would not be mixed. My rips with partial matches might be due EAC margin of error. But my tangled results are not.[Verification date: 03/04/2009 05:34:36] [Disc ID: 001821bb-00f11312-ab0b7f0d] Track [ CRC ] Status 01 [e8b31938] (08/49) Accurately ripped as in pressing(s) #2 02 [2270c5ad] (08/50) Accurately ripped as in pressing(s) #2 03 [d5d3aa81] (08/50) Accurately ripped as in pressing(s) #2 04 [2da949d5] (09/51) Accurately ripped as in pressing(s) #2 05 [2d8ec054] (08/50) Accurately ripped as in pressing(s) #2 06 [2ef6fb03] (08/50) Accurately ripped as in pressing(s) #2 07 [a42d32ed] (08/50) Accurately ripped as in pressing(s) #2 08 [ed5a3334] (07/49) Accurately ripped as in pressing(s) #2 09 [72d73d84] (08/50) Accurately ripped as in pressing(s) #2 10 [0dad6b83] (08/50) Accurately ripped as in pressing(s) #2 11 [051a4d96] (08/50) Accurately ripped as in pressing(s) #2 12 [9869c721] (08/50) Accurately ripped as in pressing(s) #2 13 [688497e9] (07/49) Accurately ripped as in pressing(s) [color=#FF0000]#3[/color] Offsetted by -664: 01 [fb408b16] (11/49) Accurately ripped as in pressing(s) #3 02 [120ec26c] (11/50) Accurately ripped as in pressing(s) #3 03 [85f0005e] (11/50) Accurately ripped as in pressing(s) #3 04 [b8a33a89] (11/51) Accurately ripped as in pressing(s) #3 05 [9ee9fa8c] (11/50) Accurately ripped as in pressing(s) #3 06 [05266d98] (11/50) Accurately ripped as in pressing(s) #3 07 [403cb7a9] (11/50) Accurately ripped as in pressing(s) #3 08 [edb3f690] (11/49) Accurately ripped as in pressing(s) #3 09 [5ee9bf2c] (11/50) Accurately ripped as in pressing(s) #3 10 [db81fbd8] (11/50) Accurately ripped as in pressing(s) #3 11 [6318fe63] (11/50) Accurately ripped as in pressing(s) #3 12 [8327d2c8] (11/50) Accurately ripped as in pressing(s) #3 13 [5450181d] (11/49) Accurately ripped as in pressing(s) [color=#FF0000]#2[/color] Track [ CRC32 ] [W/O NULL] [ LOG ] -- [C04C0029] [B504C32B] W/O NULL 01 [761D8B53] [3A060ABE] 02 [652FA4C0] [BF458F43] 03 [443FC333] [910C9063] 04 [67AF66EB] [56FF1809] 05 [032967CB] [6D9A284D] 06 [F1AF0183] [5BA95345] 07 [3975EA10] [17357CF5] 08 [75689670] [69435E30] 09 [7C7E63EE] [CE2DC789] 10 [BFA70D31] [E2C57C5D] 11 [90D1CACC] [17DC757E] 12 [A28F31AA] [9F45450E] 13 [DA03CD32] [3D096CE2] As I am very stupid I may be wrong but, as far as I understund, these results could be fixed with an accuraterip design improvement, no ? Edit: I agree you can split the thread in fact all this should be asked to Spoon. I didn't knew where to post, so as I used cuetool I posted here.