XLD: verify with AR / detect offset feature... Options

[Jedi82]

guys, i also discovered these two amazing features of XLD but so hard for me to understand them. If i understand it write, it's a way to test and correct old rip. So i pick some old rip that i made: tracks for all of them where not present in AccurateRip database but now testing them they are...

1) here is the log

CODE

List of alternate offset correction values
(1) 658 (confidence 84)
(2) -226 (confidence 3)

AccurateRip Summary
Track 01 : OK (AR2, confidence 11, with different offset)
Track 02 : OK (AR2, confidence 11, with different offset)
Track 03 : OK (AR2, confidence 11, with different offset)
Track 04 : OK (AR2, confidence 11, with different offset)
Track 05 : OK (AR2, confidence 11, with different offset)
Track 06 : OK (AR2, confidence 11, with different offset)
Track 07 : OK (AR2, confidence 11, with different offset)
Track 08 : OK (AR2, confidence 11, with different offset)
Track 09 : OK (AR2, confidence 11, with different offset)
Track 10 : OK (AR2, confidence 11, with different offset)
Track 11 : OK (AR2, confidence 11, with different offset)
Track 12 : OK (AR2, confidence 11, with different offset)
Track 13 : OK (AR2, confidence 11, with different offset)
Track 14 : OK (AR2, confidence 11, with different offset)
->All tracks accurately ripped.

All Tracks
Album gain : -8.21 dB
Peak : 0.996429
CRC32 hash : C970A6A3
CRC32 hash (skip zero) : 5ECFE413

Track 01
Track gain : -9.19 dB
Peak : 0.994904
CRC32 hash : C045E483
CRC32 hash (skip zero) : C41438EA
AccurateRip signature : 16BB25A1
->Accurately ripped! (AR2, confidence 11)
(matched with the different offset correction value;
calculated using an additional offset of 658;
the signature after correction is: C2C73A14)

in this case, what am i supposed to do with my old rip? If i select "detect offset" i receive -->



and if i click on modify and save XLD start ripping the cd one more time. I don't want it now, i just want to correct my old rip and save all for future use


2) here is the log

CODE

X Lossless Decoder version 20110703 (135.1)

XLD AccurateRip checking logfile

TOC of the selected file
Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 00:00:00 | 02:32:35 | 0 | 11434
2 | 02:32:35 | 03:14:20 | 11435 | 26004
3 | 05:46:55 | 03:52:27 | 26005 | 43431
4 | 09:39:07 | 03:15:35 | 43432 | 58091
5 | 12:54:42 | 04:31:28 | 58092 | 78444
6 | 17:25:70 | 03:52:65 | 78445 | 95909
7 | 21:18:60 | 04:19:12 | 95910 | 115346
8 | 25:37:72 | 03:50:30 | 115347 | 132626
9 | 29:28:27 | 04:12:10 | 132627 | 151536
10 | 33:40:37 | 03:47:48 | 151537 | 168609
11 | 37:28:10 | 03:00:50 | 168610 | 182159
12 | 40:28:60 | 03:50:74 | 182160 | 199483
13 | 44:19:59 | 03:49:31 | 199484 | 216689
14 | 48:09:15 | 03:11:57 | 216690 | 231071
15 | 51:20:72 | 04:47:46 | 231072 | 252642
16 | 56:08:43 | 02:59:38 | 252643 | 266105

AccurateRip Summary
Track 01 : OK (AR2, confidence 5)
Track 02 : OK (AR2, confidence 6)
Track 03 : OK (AR2, confidence 6)
Track 04 : OK (AR2, confidence 6)
Track 05 : OK (AR2, confidence 5)
Track 06 : OK (AR2, confidence 5)
Track 07 : OK (AR2, confidence 5)
Track 08 : OK (AR2, confidence 5)
Track 09 : OK (AR2, confidence 6)
Track 10 : OK (AR2, confidence 5)
Track 11 : OK (AR2, confidence 5)
Track 12 : OK (AR2, confidence 5)
Track 13 : OK (AR2, confidence 3)
Track 14 : OK (AR2, confidence 3)
Track 15 : OK (AR2, confidence 3)
Track 16 : OK (AR2, confidence 3)
->All tracks accurately ripped.

All Tracks
Album gain : -9.50 dB
Peak : 1.000000
CRC32 hash : 52F73D73
CRC32 hash (skip zero) : 11C08918

Track 01
Track gain : -10.28 dB
Peak : 1.000000
CRC32 hash : 07D6540F
CRC32 hash (skip zero) : 51E76320
AccurateRip signature : 50F24C1E
->Accurately ripped! (AR2, confidence 5)

when i ripped this disc this was the log:

CODE

Peak level 100.0 %
Track quality 100.0 %
Test CRC 137613F2
Copy CRC 137613F2
Track not present in AccurateRip database

so, in this case otherwise, it's ok like this and i can archive it or what?


3) here is the log

CODE

X Lossless Decoder version 20110703 (135.1)

XLD AccurateRip checking logfile

TOC of the selected file
Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 00:00:00 | 01:50:13 | 0 | 8262
2 | 01:50:13 | 07:51:30 | 8263 | 43617
3 | 09:41:43 | 05:10:57 | 43618 | 66924
4 | 14:52:25 | 05:09:58 | 66925 | 90157
5 | 20:02:08 | 05:58:02 | 90158 | 117009
6 | 26:00:10 | 05:28:09 | 117010 | 141618
7 | 31:28:19 | 07:01:46 | 141619 | 173239
8 | 38:29:65 | 05:05:21 | 173240 | 196135
9 | 43:35:11 | 12:15:66 | 196136 | 251326

List of alternate offset correction values
(1) 12 (confidence 25)
(2) -18 (confidence 16)

AccurateRip Summary
Track 01 : OK (AR2, confidence 23)
Track 02 : OK (AR2, confidence 23)
Track 03 : OK (AR2, confidence 23)
Track 04 : OK (AR2, confidence 23)
Track 05 : OK (AR2, confidence 23)
Track 06 : OK (AR2, confidence 23)
Track 07 : OK (AR2, confidence 23)
Track 08 : OK (AR2, confidence 23)
Track 09 : OK (AR2, confidence 23)
->All tracks accurately ripped.

All Tracks
Album gain : -4.57 dB
Peak : 1.000000
CRC32 hash : 46E4DBF2
CRC32 hash (skip zero) : 2165271D

Track 01
Track gain : -5.06 dB
Peak : 1.000000
CRC32 hash : D77E5B8F
CRC32 hash (skip zero) : 63D82480
AccurateRip signature : AB1893AC
->Accurately ripped! (AR2, confidence 23)

Track 02
Track gain : -4.34 dB
Peak : 1.000000
CRC32 hash : CB933C5D
CRC32 hash (skip zero) : A0F8B0C9
AccurateRip signature : 3E7D1CB9
->Accurately ripped! (AR2, confidence 23)

same here, when i was ripping the disc it's was no AR verified but now it is...it's ok like this or not?

So hard to understand this things!!!!!!!!!!

[fracai]

When you "modify and save" what XLD is actually doing is resaving the audio with samples added and removed from the beginning or end of the file.

CDs that originally indicate that the disc is not present in the AR database may be checkable later once they have been added. This occurs often when you rip a newly released album.

[Jedi82]

Ok perfect, now i red a lot about Offset and so on and i found some of my log where the offset correction was NO set so i think i MUST use the function of XLD to' correct and save but usong it i discovered that the program save a unique corrected file despite single flac file...it is normal and if no how can i rerip all the tracks correctly?

[greynol]

how can i rerip all the tracks correctly?

What gives you reason to believe they weren't ripped correctly in the first place?

Do you have some other summary report suggesting there might be a problem? What you've provided so far strongly indicates the rip was error-free.

[Jedi82]

Ummm don't know maybe because i red the log and all thr options Are there and perfectly settings and zero error occured...but there is this offset value one Time no set, in another log wrongly set

[greynol]

there is this offset value one Time no set, in another log wrongly set

Do you have any evidence to support the idea that this may have happened in any of these specific instances?

So far it seems likely that you have a perfectly good rips and one of them may have simply originated from a pressing that wasn't present in the AR database.

This post has been edited by greynol: Jul 16 2011, 10:46

[Jedi82]

The log:

CODE

Used drive : HL-DT-STRW/DVD GCC-4247N Adapter: 1 ID: 0

Read mode : Secure
Utilize accurate stream : Yes
Defeat audio cache : Yes
Make use of C2 pointers : No

Read offset correction : 6
Overread into Lead-In and Lead-Out : No
Fill up missing offset samples with silence : Yes
Delete leading and trailing silent blocks : No
Null samples used in CRC calculations : Yes
Used interface : Native Win32 interface for Win NT & 2000
Gap handling : Appended to previous track

Used output format : User Defined Encoder
Selected bitrate : 320 kBit/s
Quality : High
Add ID3 tag : No
Command line compressor : C:\Program Files\FLAC\flac.exe
Additional command line options : -V -8 -T "artist=%a" -T "title=%t" -T "album=%g" -T "date=%y" -T "tracknumber=%n" -T "genre=%m" %s


TOC of the extracted CD

Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 0:00.00 | 4:27.02 | 0 | 20026
2 | 4:27.02 | 4:18.01 | 20027 | 39377
3 | 8:45.03 | 3:49.71 | 39378 | 56623
4 | 12:34.74 | 5:06.27 | 56624 | 79600
5 | 17:41.26 | 3:58.05 | 79601 | 97455
6 | 21:39.31 | 4:04.30 | 97456 | 115785
7 | 25:43.61 | 5:31.28 | 115786 | 140638
8 | 31:15.14 | 3:42.05 | 140639 | 157293
9 | 34:57.19 | 3:47.21 | 157294 | 174339
10 | 38:44.40 | 5:02.62 | 174340 | 197051
11 | 43:47.27 | 4:00.45 | 197052 | 215096
12 | 47:47.72 | 4:52.15 | 215097 | 237011
13 | 52:40.12 | 3:24.38 | 237012 | 252349
14 | 56:04.50 | 5:23.18 | 252350 | 276592
15 | 61:27.68 | 3:48.71 | 276593 | 293763
16 | 65:16.64 | 7:41.48 | 293764 | 328386


Track 1

Filename I:\Adema - 2005 - Planets\01 - Shoot The Arrows.wav

Pre-gap length 0:00:02.00

Peak level 98.8 %
Track quality 100.0 %
Test CRC B82E2694
Copy CRC B82E2694
Copy OK

Track 2

Filename I:\Adema - 2005 - Planets\02 - Barricades In Time.wav

Pre-gap length 0:00:01.17

Peak level 98.8 %
Track quality 99.9 %
Test CRC 19FF9E10
Copy CRC 19FF9E10
Copy OK

Track 3

Filename I:\Adema - 2005 - Planets\03 - Tornado.wav

Peak level 98.8 %
Track quality 100.0 %
Test CRC B004256B
Copy CRC B004256B
Copy OK

i think all good except the offset value that XLD, damn good program, evidence like this:





so??

i don't want to say, give reasons or don't know what else, i just red a lot of stuff about, test with my rips and ask to all of you triing to understand

[greynol]

The log indicating the drive and offset configured was the crucial part that was missing.

Without it, the other information you provided from XLD was simply not enough to determine that the offset was configured incorrectly, no matter how good the program is.

[Jedi82]

ummm ok soooo? What's the answer?

[Jedi82]

Greynol, what i still don't understand is:

when i have old old rip of mine done with EAC like the one here, when there wasn't the AR function (but the T&C feature set to ON), how can i check (i'm on a mac now) if i made a good rip or not? I would like to recheck all these rip so that i can not to rerip all of them!

It's enough to open the cue file of the album with XLD and make a Accurate Rip test? And at the end, if i see a log like this:

CODE

X Lossless Decoder version 20110703 (135.1)

XLD AccurateRip checking logfile

TOC of the selected file
Track | Start | Length | Start sector | End sector
---------------------------------------------------------
1 | 00:00:00 | 03:30:22 | 0 | 15771
2 | 03:30:22 | 03:15:53 | 15772 | 30449
3 | 06:46:00 | 04:28:45 | 30450 | 50594
4 | 11:14:45 | 03:25:40 | 50595 | 66009
5 | 14:40:10 | 04:15:20 | 66010 | 85154
6 | 18:55:30 | 03:16:10 | 85155 | 99864
7 | 22:11:40 | 04:54:67 | 99865 | 121981
8 | 27:06:32 | 03:57:30 | 121982 | 139786
9 | 31:03:62 | 03:21:60 | 139787 | 154921
10 | 34:25:47 | 04:10:08 | 154922 | 173679
11 | 38:35:55 | 04:33:52 | 173680 | 194206
12 | 43:09:32 | 03:29:20 | 194207 | 209901
13 | 46:38:52 | 09:07:38 | 209902 | 250964

List of alternate offset correction values
(1) -10 (confidence 2)

AccurateRip Summary
Track 01 : OK (AR2, confidence 11)
Track 02 : OK (AR2, confidence 11)
Track 03 : OK (AR2, confidence 11)
Track 04 : OK (AR2, confidence 11)
Track 05 : OK (AR2, confidence 11)
Track 06 : OK (AR2, confidence 11)
Track 07 : OK (AR2, confidence 11)
Track 08 : OK (AR2, confidence 11)
Track 09 : OK (AR2, confidence 11)
Track 10 : OK (AR2, confidence 11)
Track 11 : OK (AR2, confidence 11)
Track 12 : OK (AR2, confidence 11)
Track 13 : OK (AR2, confidence 11)
->All tracks accurately ripped.

All Tracks
Album gain : -9.95 dB
Peak : 0.992096
CRC32 hash : 50AFD421
CRC32 hash (skip zero) : 7EC40FF8

Track 01
Track gain : -10.99 dB
Peak : 0.988556
CRC32 hash : 097F9AE4
CRC32 hash (skip zero) : 963DF605
AccurateRip signature : 0EAE378B
->Accurately ripped! (AR2, confidence 11)

Track 02
Track gain : -9.33 dB
Peak : 0.992096
CRC32 hash : E6A66B34
CRC32 hash (skip zero) : 130E8605
AccurateRip signature : EC11CEFA
->Accurately ripped! (AR2, confidence 11)

Track 03
Track gain : -10.32 dB
Peak : 0.988556
CRC32 hash : C673233E
CRC32 hash (skip zero) : D96D5987
AccurateRip signature : 3C744965
->Accurately ripped! (AR2, confidence 11)

Track 04
Track gain : -9.73 dB
Peak : 0.988556
CRC32 hash : 4753F3EF
CRC32 hash (skip zero) : AC71BFD7
AccurateRip signature : A1D36A64
->Accurately ripped! (AR2, confidence 11)

Track 05
Track gain : -9.92 dB
Peak : 0.988556
CRC32 hash : 0CD155AA
CRC32 hash (skip zero) : DAFF1A82
AccurateRip signature : C2815E57
->Accurately ripped! (AR2, confidence 11)

Track 06
Track gain : -10.06 dB
Peak : 0.988556
CRC32 hash : DA3C52E4
CRC32 hash (skip zero) : 59FFBE9B
AccurateRip signature : 9AFFBB76
->Accurately ripped! (AR2, confidence 11)

Track 07
Track gain : -8.49 dB
Peak : 0.988556
CRC32 hash : 81B0FB39
CRC32 hash (skip zero) : 7BC20315
AccurateRip signature : ADB295DF
->Accurately ripped! (AR2, confidence 11)

Track 08
Track gain : -9.64 dB
Peak : 0.988556
CRC32 hash : 08000086
CRC32 hash (skip zero) : F8077F3A
AccurateRip signature : 81563CD3
->Accurately ripped! (AR2, confidence 11)

Track 09
Track gain : -9.43 dB
Peak : 0.988556
CRC32 hash : 71BA4A4D
CRC32 hash (skip zero) : D33C60EE
AccurateRip signature : 79484A9D
->Accurately ripped! (AR2, confidence 11)

Track 10
Track gain : -9.74 dB
Peak : 0.988556
CRC32 hash : 79372438
CRC32 hash (skip zero) : 71AA58AE
AccurateRip signature : 1E1D4C02
->Accurately ripped! (AR2, confidence 11)

Track 11
Track gain : -9.90 dB
Peak : 0.988556
CRC32 hash : 614E5283
CRC32 hash (skip zero) : 119FB02D
AccurateRip signature : FC2B1753
->Accurately ripped! (AR2, confidence 11)

Track 12
Track gain : -9.98 dB
Peak : 0.988556
CRC32 hash : AA38A273
CRC32 hash (skip zero) : 9DA198C6
AccurateRip signature : 1E9B99DB
->Accurately ripped! (AR2, confidence 11)

Track 13
Track gain : -9.56 dB
Peak : 0.988556
CRC32 hash : 0649587C
CRC32 hash (skip zero) : FA1FD4EA
AccurateRip signature : 8CE5C333
->Accurately ripped! (AR2, confidence 11)

End of status report

i can assume that all went good?

This post has been edited by db1989: May 5 2012, 00:12

Reason for edit: You know how to use a [codebox], so please do.