CUETools versions 1.9.5 through 2.1.5 (current)
Reply #584 – 2009-08-14 12:14:14
Hi, I'm using the stable version of CUETools (1.9.5) and I would like to know: does this program correct the offsets by default if it find the corrected value via AccurateRip? In other words, I've got this log, are the files generated corrected?[Verification date: 14/08/2009 13.04.59] [Disc ID: 001491a5-00d42732-9b0b0a0d] Track [ CRC ] Status 01 [227cc5b1] (00/08) No matches 02 [7aa2afe3] (00/07) No matches 03 [d9678ca5] (00/07) No matches 04 [7a66fd12] (00/07) No matches 05 [46d14a8a] (00/06) No matches 06 [4bd71e44] (00/07) No matches 07 [6a3638d9] (00/07) No matches 08 [40a4d6cc] (00/07) No matches 09 [287e3303] (00/07) No matches 10 [7e027f0e] (00/07) No matches 11 [03734de5] (00/07) No matches 12 [4079e0f2] (00/07) No matches 13 [5863eb0b] (00/07) No matches Offsetted by 48: 01 [58181c12] (08/08) Accurately ripped as in pressing(s) #1 02 [f72940f5] (07/07) Accurately ripped as in pressing(s) #1 03 [dac12a18] (07/07) Accurately ripped as in pressing(s) #1 04 [763bf9ba] (07/07) Accurately ripped as in pressing(s) #1 05 [90f62ee8] (06/06) Accurately ripped as in pressing(s) #1 06 [da6441db] (07/07) Accurately ripped as in pressing(s) #1 07 [bd8c400d] (07/07) Accurately ripped as in pressing(s) #1 08 [d3ef6460] (07/07) Accurately ripped as in pressing(s) #1 09 [a6dd0315] (07/07) Accurately ripped as in pressing(s) #1 10 [02b7f27b] (07/07) Accurately ripped as in pressing(s) #1 11 [ab7d547f] (07/07) Accurately ripped as in pressing(s) #1 12 [5d1f9351] (07/07) Accurately ripped as in pressing(s) #1 13 [ad0de8c4] (07/07) Accurately ripped as in pressing(s) #1