Many moons ago, I wrote a program to verify CDs I had already ripped to Apple Lossless against the AccurateRip checksum, which was a life saver in verifying that my collection was good without having to re-rip 1000 or so CDs.
I've recently decided to revisit this and to update it to use the new AR v2 checksum, which seems to work fine. But I am getting some discs which rip accurately when I try them with the ripper, but my verifier is unable to confirm this, and this seems to be down to the use of a pressing offset.
From browsing around what Spoon has written about the pressing offset calculation, I understand that it is calculated using the same method as the drive offset calculation - a sliding window is moved over the data from the disc around frame 450, and when the resulting CRC matches the known CRC for that disc, the offset of the frame is the pressing offset. (Or at least I think that's how it works!)
All that is fine; the bit I don't understand is how to get the target value for the pressing offset CRC from the AccurateRip database. This has to be stored by the database - is it one of the CRCs in the standard packet that is downloaded for the disc when the database is queried, or is it acquired by some other means?
I've recently decided to revisit this and to update it to use the new AR v2 checksum, which seems to work fine. But I am getting some discs which rip accurately when I try them with the ripper, but my verifier is unable to confirm this, and this seems to be down to the use of a pressing offset.
From browsing around what Spoon has written about the pressing offset calculation, I understand that it is calculated using the same method as the drive offset calculation - a sliding window is moved over the data from the disc around frame 450, and when the resulting CRC matches the known CRC for that disc, the offset of the frame is the pressing offset. (Or at least I think that's how it works!)
All that is fine; the bit I don't understand is how to get the target value for the pressing offset CRC from the AccurateRip database. This has to be stored by the database - is it one of the CRCs in the standard packet that is downloaded for the disc when the database is queried, or is it acquired by some other means?
Comment