title
Products            Buy            Support Forum            Professional            About            Codec Central
 

dBpowerAMP CD Ripper Problems

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • DJPT-UK

    • Apr 2007
    • 9

    dBpowerAMP CD Ripper Problems

    I recently paid for dBpowerAMP CD Ripper after using the R12 Beta. I am using it on XP Home.

    I am ripping my CD collection with a Plextor PX-760A. I have FUA switched on, C2 errors, ultra secure ripping and verify with AR. I am still getting clicks when ripping some CDs - yet the ripper always confirms the rip was secure (if disk is not in the AR database).

    When the ripper says it is secure, I presume it means a bit-perfect copy right? If this is the case, why the clicks on some CDs? (Even CDs that are not scratched and not copy protected etc). The CDs in question here play perfectly. I have never had a track marked as error because it wasn't able to rip properly - so all my ripped tracks should be perfect shouldn't they?

    Also, even though I have the rip report thing enabled it never displays it after ripping. Why is this?

    So far I am not too pleased with this software. I've paid for it (OK, it wasn't an un-reasonable price) and it dosen't seem to do it's job all that well.
  • LtData
    dBpoweramp Guru

    • May 2004
    • 8288

    #2
    Re: dBpowerAMP CD Ripper Problems

    Did you get the green check-mark for your rips or an green "i"? The check mark means that the rip was secure, the "i" means that some errors could have slipped through.
    Are you using Burst mode or Secure mode? This option is found under the Options menu.

    Under the arrow beside the option button, under "After Ripping" do you have "Show Information Log" checked?

    Comment

    • DJPT-UK

      • Apr 2007
      • 9

      #3
      Re: dBpowerAMP CD Ripper Problems

      When the disc is not in AR, I get a green tick "Secure". I have never had an "i" or anything else other than the green tick "Secure".

      I am ripping in Secure Mode with Ultra Secure enabled. Yes the show info log is enabled.

      Could it be something to do with FUA or C2 maybe? Or could it just be the quality of the CDs?

      Comment

      • LtData
        dBpoweramp Guru

        • May 2004
        • 8288

        #4
        Re: dBpowerAMP CD Ripper Problems

        Did you test for FUA or C2 or did you just check the boxes?

        Comment

        • DJPT-UK

          • Apr 2007
          • 9

          #5
          Re: dBpowerAMP CD Ripper Problems

          Yes I tested with both first.

          I used a badly scratched CD for the C2 test and the ripper said it detected C2 pointers and will be used. The FUA said something like cache detected, when I turned FUA on I ran another FUA test and it said the cache detected was 0.

          Comment

          • LtData
            dBpoweramp Guru

            • May 2004
            • 8288

            #6
            Re: dBpowerAMP CD Ripper Problems

            Try turning off FUA and take a CD that, when ripped, had scratches and pops in it, and try re-ripping it with the new setting and see if you get different results or a different CRC.

            Comment

            • DJPT-UK

              • Apr 2007
              • 9

              #7
              Re: dBpowerAMP CD Ripper Problems

              I will try that when I get home later today and report back.

              Just one other question, I am thinking of ditching my Plextor PX-760A and buying a PX-230A (I have read reviews on Hydrogen Audio etc and it seems a much better drive). Does the PX-230A support C2?

              Thanks

              Comment

              • DJPT-UK

                • Apr 2007
                • 9

                #8
                Re: dBpowerAMP CD Ripper Problems

                I've located and fixed the problem.

                It seems the drives were in "PIO Only" mode for some bizarre reason. I uninstalled the drivers and re-installed and so far so good. Any ideas why it might have done this? That probably explains why the first 10 or so CDs I ripped are perfect, then the more recent ones are clicking like chuff.

                The drives are almost brand new (couple of months) as is the IDE cable. It's never done this before. Maybe it's because when I re-installed XP I didn't properly uninstall the drives and re-install again, just left them in during the whole re-install??

                Comment

                • LtData
                  dBpoweramp Guru

                  • May 2004
                  • 8288

                  #9
                  Re: dBpowerAMP CD Ripper Problems

                  No, the problem is XP itself. I found that when I used Ultra Secure to rip CDs that weren't in AccurateRip, after a few CDs, the drive would drop to PIO mode. This is due to the "feature" in XP that drops the CD read speed down to PIO Mode if you are getting read errors, or apparently if you re-read the same thing over and over). There isn't a way to disable this, unfortunately, so you still have to reboot.

                  Comment

                  • DJPT-UK

                    • Apr 2007
                    • 9

                    #10
                    Re: dBpowerAMP CD Ripper Problems

                    So I guess the only thing to do here is keep checking that Windows hasn't dropped back into PIO Mode. Is uninstalling the drivers and re-installing the only way to sort this? Will I have to keep re-configuring AR everytime or will it be OK?

                    Finally, do you know if the PX-230A supports C2?

                    Thanks!

                    Comment

                    • LtData
                      dBpoweramp Guru

                      • May 2004
                      • 8288

                      #11
                      Re: dBpowerAMP CD Ripper Problems

                      I don't know about the PX-230A, but the only way I know to fix it is to uninstall and reinstall the IDE controller that that device is attached to.

                      No, you don't need to reconfigure AR after you do this.

                      Comment

                      Working...

                      ]]>