title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Naim rips claimed to be superior to dBpoweramp rips.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • likesmusic

    • Apr 2011
    • 2

    Naim rips claimed to be superior to dBpoweramp rips.

    Hi.

    On this thread on the Naim forum it is being argued by David Dever, the US distributor for Naim, that rips made by a Naim UnitiServe are audibly superior to dBpoweramp rips across a range of players, and that this may point "to a flaw in the header information of dBpoweramp rips". I think the UnitiServe rips to WAV. Other members of the same forum have compared dBpoweramp and Naim rips and found there to be a difference in the WAV headers, but not in the audio data.

    Is there a flaw in the way dBpoweramp makes a WAV header, or is there a flaw in the way Naim do it, or shouldn't it matter? How might differences in the file header affect the sound quality?
    Last edited by likesmusic; April 25, 2011, 02:36 PM.
  • Spoon
    Administrator
    • Apr 2002
    • 44583

    #2
    Re: Naim rips claimed to be superior to dBpoweramp rips.

    I have read that, a fact chunk makes no difference to a wave file, it simply informs the size of the wave file in samples and should not even be used for normal PCM wave files, it is only needed for compressed wave files (such as mp3 in a wave file) where the sample count is unknown.

    How it effects the quality, Naim would have to specifically code to degrade the audio stream if it does not contain a fact chunk (which would be absurd if they did), otherwise there would be no degradation.
    Spoon
    www.dbpoweramp.com

    Comment

    • likesmusic

      • Apr 2011
      • 2

      #3
      Re: Naim rips claimed to be superior to dBpoweramp rips.

      Thanks spoon. I'll post your answer on that forum in the same thread if you don't mind, particularly as someone there has suggested you 'don't give a sh*t'. Maybe you'll participate directly,

      Comment

      Working...

      ]]>