title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Odd development: "Error calculated total RIFF chunk size differs from file

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

    • Feb 2012
    • 2

    Odd development: "Error calculated total RIFF chunk size differs from file

    Hi,
    After using the ripping program flawlessly for about 10 days, I have begun to get this error result on most files I try to rip. Watching Windows Explorer during the rip, I see the file being built, but then at the end of the encoding process, the file is reduced to only 3KB, which means no music at all. Sometimes one or two files on a disk will get built properly, but most of them vanish--

    Any ideas? I don't think I changed any settings around the time this started happening except maybe bit depth, which I have now tried at several different settings, so I don't think that's the problem--

    Thanks--

    Tim

    PS: More complete error message:

    Warning 'RiffSizeLeft != FileSizeLeft' must be extra data on end of file. [clRIFFHandler::ScanFile]
    Error calculated total RIFF chunk size differs from file. [clRIFFHandler::ScanFile]
  • dbfan
    dBpoweramp Guru

    • Jan 2011
    • 937

    #2
    Re: Odd development: "Error calculated total RIFF chunk size differs from file

    Writing wave files?

    It sounds like something is corrupting the file write, as dBpoweramp would never reduce the filesize, security software might do so.

    Comment

    • apspr

      • Feb 2012
      • 2

      #3
      Re: Odd development: "Error calculated total RIFF chunk size differs from file

      Originally posted by mrspoonsi
      Writing wave files?

      It sounds like something is corrupting the file write, as dBpoweramp would never reduce the filesize, security software might do so.
      It happens with WAV and AIFF files. My other ripping software is working as usual, so whatever the problem is, it's unique to dBpoweramp. The file write or encoding process is being corrupted, I agree. Any idea why?

      Maybe I'll do a reinstall and see if that clears it up.

      Comment

      Working...

      ]]>