could it be the track information? The reason I use dbpoweramp is because it works at attaching the library track information for wav... others I have used had problems.
Comparing rips
I did an experiment and the results are mystifying to me. I ripped the same track with three different programs:
iTunes (error correction on)
dbpoweramp (free version) - AccurateRip verified
Exact Audio Copy - AccurateRip verified
I ripped them all to WAV.
iTunes and EAC returned the same number of bits (there are all "size on disk" numbers):
191,135,744
dbpoweramp returned a slightly larger file:
191,172,608
I then converted them to Apple Lossless files using the encoder in iTunes.
Again, two of the files matched the number of bits, but this time it was EAC and dbpoweramp!:
85,237,760
iTunes returned a different number:
71,892,990
I then ripped the track directly to Apple Lossless from dbpoweramp and dbpoweramp (EAC doesn't do this) and the results were as before:
iTunes: 71,892,990
dbpoweramp: 85,237,760
What is up with this? Has anyone seen these kind of results also?
Thanks for your help.
Mark
iTunes (error correction on)
dbpoweramp (free version) - AccurateRip verified
Exact Audio Copy - AccurateRip verified
I ripped them all to WAV.
iTunes and EAC returned the same number of bits (there are all "size on disk" numbers):
191,135,744
dbpoweramp returned a slightly larger file:
191,172,608
I then converted them to Apple Lossless files using the encoder in iTunes.
Again, two of the files matched the number of bits, but this time it was EAC and dbpoweramp!:
85,237,760
iTunes returned a different number:
71,892,990
I then ripped the track directly to Apple Lossless from dbpoweramp and dbpoweramp (EAC doesn't do this) and the results were as before:
iTunes: 71,892,990
dbpoweramp: 85,237,760
What is up with this? Has anyone seen these kind of results also?
Thanks for your help.
Mark