Takes a binary track of correct length, MD5 redump.org hash and a starting sample value. Proggie pads +588 to -588 samples to find correct offset. Overwrites your file with the adjustments if found.

Thanks to all for the track cutting idea (inspiration). D:
Repairing lots of redbook now. :)

Thanks to everyone for sharing this godsend database

Is it possible to mention the offset value of the first non-zero byte in each track (assuming track isn't all zeroes)? I'd like to try moving the data around first before patch/re-rip/trash some mismatch redbook tracks.

Someone mentioned it once for Lunar Track02 and that solved my problem

Thanks in advance for any replies