Tweet
I know in the past there was discussion that the read offset used by accuraterip, dBpoweramp and EAC is off by 30. It was decided that it was not really an issue, especially since fixing it would require scrapping all of accuraterip.
I was wondering if the way AccurateRip 2.0 will be implemented, that is able to read across pressings, would also make it possible to reset the offset by the correct 30 frames and keep the current AR db?
I was wondering if the way AccurateRip 2.0 will be implemented, that is able to read across pressings, would also make it possible to reset the offset by the correct 30 frames and keep the current AR db?
Comment