title
Products            Buy            Support Forum            Professional            About            Codec Central
 

just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

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

    • Dec 2017
    • 4

    just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

    I just installed dbpoweramp - Windows 10 Pro.
    After ripping several dozen albums using CD Ripper - now I find out that all these FLAC rips are bad
    * CD Ripper didn't give any indication of errors - verify audio left checked.
    * Each CD took several minute to process.
    * The checksums 99.9% plus verified.
    * The file size looks "proper" - not an obvious too small file size.
    * I even tried Level 6, same issue.
    Even Music Converter gets angry when I try to convert these FLAC files.
    I ripped to m4a with no issues on play back.
    Any suggestions? thanks, Nigel
    At work I am famous for finding the other side of 6 Sigma, 99.9999% reliable - the 00.0001% failures in systems or software.
    FLAC - Release 16.3 (FLAC 1.3.2)
    fLaC "
    ÄBð ¥ reference libFLAC 1.3.2 20170101 C AccurateRipResult=AccurateRip: Accurate (confidence 3) [C9F85127]2 AccurateRipDiscID=012-00126729-00aef75b-8c0a3e0c-1 û©
    Attached Files
    Last edited by nigeldh; December 18, 2017, 06:07 AM. Reason: add thanks
  • Spoon
    Administrator
    • Apr 2002
    • 44506

    #2
    Re: just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

    Convert a selection of your flac files to 'Test Conversion', what happens? any messages shown at the end?

    Where are the flac files stored?
    Spoon
    www.dbpoweramp.com

    Comment

    • nigeldh

      • Dec 2017
      • 4

      #3
      Re: just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

      1. Files were going to a Drobo. The tests are going to a local drive.
      2. Only FLAC is having issues - m4a, wav, rip with no issues.
      3. Test mode - regular and highest quality checked. No errors.
      4. Here is the logging and FLAC file using Secure Ripping option.
      5. PowerISO - no problems ripping the same track to FLAC - 7,762 KB file. m4a is 8,001 KB.
      6. I even redownloaded the trial version, installed it to a different drive and folder. Still does not work.
      Header info is there, like my initial post, but the FLAC contents aren't being written into the file.
      enjoy, grin Nigel
      Attached Files

      Comment

      • Spoon
        Administrator
        • Apr 2002
        • 44506

        #4
        Re: just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

        Convert a selection of your flac files to 'Test Conversion', what happens? any messages shown at the end?
        Spoon
        www.dbpoweramp.com

        Comment

        • nigeldh

          • Dec 2017
          • 4

          #5
          Re: just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

          Spoon - curiouser and curiouser (Also the test only rip log attached)
          I did an uncompressed FLAC - I got a good FLAC file, 17 MB.
          So time for a Sysinternals Procmon deep dive for these settings:
          test;
          FLAC default - level 5, no data; dir - test6
          FLAC uncompressed - good file, ~17 MB; dir - test7
          FLAC - level 8, no data. dir - test8
          Procmon capture is ~42 MB zipped up. PM me for how you want me to get this Procmon capture to you.

          Procmon shows:
          1. ALL the FLAC levels: 5, 8, uncompressed write data to: C:\Users\[my id]\AppData\Roaming\dBpoweramp\CDRipperCache.bin
          2. ALL the FLAC levels write data to temporary [file_name]._ : D:\music\[test dir name]\01 Cormac DeBarra - Intro._

          WriteFile lines from Procmon
          Uncompressed:
          QueryStandardInformationFile AllocationSize: 17,137,664, EndOfFile: 17,133,749, NumberOfLinks: 1, DeletePending: False, Directory: False

          Level 8 (or level 5)
          QueryStandardInformationFile AllocationSize: 65,536, EndOfFile: 64,640, NumberOfLinks: 1, DeletePending: False, Directory: False

          Level 8 last lines - WriteFile
          5:09:39.7028676 AM CDGrab.exe 7560 WriteFile D:\music\test8\01 Cormac DeBarra - Intro._ SUCCESS Offset: 62,679, Length: 1,024
          5:09:39.7028798 AM CDGrab.exe 7560 WriteFile D:\music\test8\01 Cormac DeBarra - Intro._ SUCCESS Offset: 63,703, Length: 937

          Uncompressed last lines - WriteFile
          5:08:46.2710941 AM CDGrab.exe 7560 WriteFile D:\music\test7\01 Cormac DeBarra - Intro._ SUCCESS Offset: 687, Length: 62,095
          5:08:46.2711230 AM CDGrab.exe 7560 WriteFile D:\music\test7\01 Cormac DeBarra - Intro._ SUCCESS Offset: 62,782, Length: 4
          5:08:46.2711342 AM CDGrab.exe 7560 WriteFile D:\music\test7\01 Cormac DeBarra - Intro._ SUCCESS Offset: 62,786, Length: 1,024
          5:08:46.2711455 AM CDGrab.exe 7560 WriteFile D:\music\test7\01 Cormac DeBarra - Intro._ SUCCESS Offset: 63,810, Length: 823

          Later, no Procmon, I tried CD Ripper with the various File Name options using level 5: None of them worked - the file again had no data.

          thanks, Nigel
          Attached Files
          Last edited by nigeldh; December 19, 2017, 11:50 AM.

          Comment

          • mville
            dBpoweramp Guru

            • Dec 2008
            • 4021

            #6
            Re: just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

            Have you seen this?: dBpoweramp R16.3 & FLAC 1.3.2

            Comment

            • nigeldh

              • Dec 2017
              • 4

              #7
              Re: just installed dbpoweramp, all FLAC rips are bad, m4a rips are good

              Thanks, this is the issue. I switched to Level 3 compression and the issue is resolved.
              One can see the message CPU[n] compressing after the Rip. When I hover over the PowerISO .flac I see they are using FLAC 1.2.n.
              Maybe Spoon can update the wording in the FLAC dialog.
              "We're going to need a bigger hard disk"

              Comment

              Working...

              ]]>