## ARCue C++ compiles and source

#####
Reply #16 –

But that's cheating...

Anyway, aren't there different pressings out there that have a different offset **but also** one or more differing tracks? In that case a feature like the one newly added to ARCue could lead people to believe they have a different pressing but also that their rip was not accurate for those tracks, but in fact the difference is not caused by an extraction error but due to different CD mastering of the pressings or a manufacturing defect.

PS: I just discovered another feature of ARCue "Plus" somewhat related to different pressings:

PJ Harvey - 2007 - White Chalk (UK Issue).cue:

Checking AccurateRip database

Track Ripping Status [Disc ID: 000daddc-8c07f50b]

1 ** Rip offset: 12 ** (confidence 33) [44ddbfe3]

1 Accurately Ripped (confidence 10) [87304a8f]

2 ** Rip offset: 12 ** (confidence 33) [9f5c966e]

2 Accurately Ripped (confidence 11) [29d440ca]

3 ** Rip offset: 12 ** (confidence 33) [70e1a31a]

3 Accurately Ripped (confidence 10) [3a67d5c6]

4 ** Rip offset: 12 ** (confidence 33) [effac918]

4 Accurately Ripped (confidence 11) [2e532c80]

5 ** Rip offset: 12 ** (confidence 33) [afd7ce6b]

5 Accurately Ripped (confidence 11) [9863b65b]

6 ** Rip offset: 12 ** (confidence 33) [7f11946d]

6 Accurately Ripped (confidence 11) [c56f3f05]

7 ** Rip offset: 12 ** (confidence 33) [abec05f5]

7 Accurately Ripped (confidence 11) [50372b4d]

8 ** Rip offset: 12 ** (confidence 33) [b008bf56]

8 Accurately Ripped (confidence 11) [e2c2a632]

9 ** Rip offset: 12 ** (confidence 32) [727fd8b3]

9 Accurately Ripped (confidence 11) [3f670eb7]

10 ** Rip offset: 12 ** (confidence 32) [80fe4fc8]

10 Accurately Ripped (confidence 11) [9f7bfa78]

11 ** Rip offset: 12 ** (confidence 32) [1d89a664]

11 Accurately Ripped (confidence 11) [17194990]

_______________________

All Tracks Accurately Ripped.