CD has indexed silent tracks that do not show up in AccurateRip database
Hi everyone,
I’m trying to understand a couple of things about AccurateRip results and differences between ripping software.
I’ve noticed that several tracks from a CD do not appear to have any AccurateRip database results, even though other tracks from the same disc do. Is there a reason why individual tracks might be missing from the AccurateRip database? For example, could this be related to the particular pressing/release, track offsets, pregaps, or simply not having enough submissions for those tracks?
I’m also seeing some inconsistencies between XLD and dBpoweramp when ripping the same CD. In some cases, the programs seem to report different AccurateRip results or confidence levels, and I’m trying to understand what could account for that.
Could differences in drive configuration, read offsets, ripping modes, metadata, or how each program handles the disc/track boundaries cause the results to differ? Or, assuming both programs are configured correctly, should I generally expect them to produce the same AccurateRip verification results?
Ultimately, I would love a way for PerfectTunes (AccurateRip check) to be able to not be thrown off by these results.
I’d appreciate any insight into how AccurateRip actually identifies a track/disc and how XLD and dBpoweramp may differ in their implementation.
Thanks!
I’m trying to understand a couple of things about AccurateRip results and differences between ripping software.
I’ve noticed that several tracks from a CD do not appear to have any AccurateRip database results, even though other tracks from the same disc do. Is there a reason why individual tracks might be missing from the AccurateRip database? For example, could this be related to the particular pressing/release, track offsets, pregaps, or simply not having enough submissions for those tracks?
I’m also seeing some inconsistencies between XLD and dBpoweramp when ripping the same CD. In some cases, the programs seem to report different AccurateRip results or confidence levels, and I’m trying to understand what could account for that.
Could differences in drive configuration, read offsets, ripping modes, metadata, or how each program handles the disc/track boundaries cause the results to differ? Or, assuming both programs are configured correctly, should I generally expect them to produce the same AccurateRip verification results?
Ultimately, I would love a way for PerfectTunes (AccurateRip check) to be able to not be thrown off by these results.
I’d appreciate any insight into how AccurateRip actually identifies a track/disc and how XLD and dBpoweramp may differ in their implementation.
Thanks!
Comment