title
Products            Buy            Support Forum            Professional            About            Codec Central
 

insecure error after ultra secure rip

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

    • Jan 2013
    • 5

    insecure error after ultra secure rip

    Hi

    Im a new user of dbpoweramp and have set it up using Spoons guide, I keep getting error after the ultra secure rip of each track the first secure rip is fine.

    the info it gives is the the track was ripped insecurely.

    It may be to do with the c2 pointers but i thought i set it up ok as the test reported that I have them?


    can anyone help

    thanks:smile2:
  • gunner84

    • Jan 2013
    • 5

    #2
    Re: insecure error after ultra secure rip

    just an update I disabled c2 pointers and my albums now rip without errors , i don't seem to get the ultra secure rip now though despite having that enabled?

    i just get pass 1 ripping and then cpu1 encoding.

    Comment

    • dbfan
      dBpoweramp Guru

      • Jan 2011
      • 937

      #3
      Re: insecure error after ultra secure rip

      It does not need to do any passes if accuratefip verifies

      Comment

      • gunner84

        • Jan 2013
        • 5

        #4
        Re: insecure error after ultra secure rip

        Originally posted by mrspoonsi
        It does not need to do any passes if accuratefip verifies
        ok so if it passes on pass 1 thats good.

        I tried the c2 pointer test again ,this time i scratched the cd as I don't think the marker pen worked for me i re-run the test and this time it came up saying I dont have c2 pointer drive.

        it a Matshitu UJ890.

        So Ive disabled that, thats proberly why I was getting the errors on every track.

        cheers

        Comment

        • Porcus
          dBpoweramp Guru

          • Feb 2007
          • 792

          #5
          Re: insecure error after ultra secure rip

          If the drive starts to re-rip a lot of frames in each track with C2 enabled, then the drive is likely submitting bogus C2 info which makes it look like everything is wrong.

          Comment

          Working...

          ]]>