title
Products            Buy            Support Forum            Professional            About            Codec Central
 

High CPU useage

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

    • Mar 2004
    • 2

    High CPU useage

    When running dBpowerAMP Music Converter to rip a CD MusicConverter.exe (which I assume dbpa is using) takes up 40 - 90% of my CPU. This is a relatively new issue, as I ripped a large number of CDS before experiencing this.

    I am using what I belive to be the latest version of the app, and dont have any issues with my cd-rom drive, which is 52x.

    Is there something I can do to prevent this?
  • Spoon
    Administrator
    • Apr 2002
    • 44574

    #2
    Re: High CPU useage

    Nothing wrong with high CPU usage, if it used only 10% it would take 10x longer to rip...
    Spoon
    www.dbpoweramp.com

    Comment

    • eightdotthree

      • Mar 2004
      • 2

      #3
      Re: High CPU useage

      True, but this is a new thing that has just happened seemingly overnight. I can no longer rip a cd while working, and for me its a pain.

      It could be something else on my end, I just wanted to see if it there was a fix for it.

      thanks

      Comment

      • Unregistered

        #4
        Re: High CPU useage

        New issue? I normally use Roxio to burn/rip CDs, but I have used dBpoweramp's to burn/rip, and in both programs I have 90-100% CPU usage. I have a Compaq PC, 40x CD-RW Drive, P4 2.53 (not HT), and 512mb DDR RAM. If you have RD-RAM, and your processor has HT, then maybe because of the multi-tasking abilities of your computer, your computer didn't use all the CPU usage. So what I am saying is if you are using RD-RAM, and have a (strong) HT processor, than this may be an issue. But I doubt you have RDRAM because there are very few companies that use that anymore. I don't even think Alienware does. Also, using 100% CPU, even with HT and RD-RAM would be good for speed of burning/ripping (as you already know).


        Good Luck

        Comment

        Working...

        ]]>