title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Start of Cd Ripper very slow (70 secs)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Oliviander
    • Sep 2010
    • 36

    Start of Cd Ripper very slow (70 secs)

    Hi Spoon,
    I still have the problem that the start of dbpowerampCDRipper takes very very long
    exactly 70 seconds and that reproducable on the second
    I have this Problem since Version 13.5 (and have now 14.2)
    Even a total deeinstallation does not help.
    Is there any registry entry that might be responsible for this.
    I got Windows 7 Prof SP1 64bit on my private PC where this problem occurs.

    On my Office PC (same Configuration) this problem doesn't exist.

    I'd appreciate your help
    thx in advance

    Oliviander
  • Spoon
    Administrator
    • Apr 2002
    • 44376

    #2
    Re: Start of Cd Ripper very slow (70 secs)

    Do a full wipe then reinstall:

    ...also how to do a full reset of dBpoweramp? (if dBpoweramp crashes for some reason) Where does dBpoweramp save its files / settings? It is installed to c:\Program Files\Illustrate\dBpoweramp or c:\Program Files (x86)\Illustrate\dBpoweramp The 64 bit version of dBpoweramp is installed to: c:\Program Files\dBpoweramp It
    Spoon
    www.dbpoweramp.com

    Comment

    • Oliviander
      • Sep 2010
      • 36

      #3
      Re: Start of Cd Ripper very slow (70 secs)

      Originally posted by Spoon
      Hi spoon,
      did it
      uninstalled all illustrate programs
      run dbpoweramp-reset.exe (all options checked)
      Rebooted
      reinstalled dbpoweramp 14.2

      Still: 70 secs to start :o(
      (It's the same 70 secs always exactly to the second)

      Look at the taskManager
      process grab.exe is there immediately with ~2k working space
      after 70 secs it extends to ~5k working space
      and the program starts

      What alse can I try

      Oliviander

      Comment

      • dbfan
        dBpoweramp Guru
        • Jan 2011
        • 937

        #4
        Re: Start of Cd Ripper very slow (70 secs)

        You are starting cd ripper with no cd disk in the drive?

        Comment

        • Oliviander
          • Sep 2010
          • 36

          #5
          Re: Start of Cd Ripper very slow (70 secs)

          Originally posted by mrspoonsi
          You are starting cd ripper with no cd disk in the drive?
          Yes two CD drives and no CD in it.

          Comment

          • Spoon
            Administrator
            • Apr 2002
            • 44376

            #6
            Re: Start of Cd Ripper very slow (70 secs)

            I have no ideas.
            Spoon
            www.dbpoweramp.com

            Comment

            • Oliviander
              • Sep 2010
              • 36

              #7
              Re: Start of Cd Ripper very slow (70 secs)

              Nobody else any ideas ?

              I tried disabling of all CD Drives and all audio components.
              I reinstalled the ripper several times and used the reset program.
              But it still takes 70 secs for the ripper to start.
              No other program on my Computer shows any similar behavior.

              Buhu

              Comment

              • Spoon
                Administrator
                • Apr 2002
                • 44376

                #8
                Re: Start of Cd Ripper very slow (70 secs)

                Try CD Ripper >> Options >> Communication >> Windows Internal
                Spoon
                www.dbpoweramp.com

                Comment

                • BrodyBoy
                  dBpoweramp Guru
                  • Sep 2011
                  • 777

                  #9
                  Re: Start of Cd Ripper very slow (70 secs)

                  It's a long shot, but maybe you could look at the Windows Event Viewer for clues. (Perhaps an error or info flag is posted when the program is doing whatever it's doing for those 70 seconds. )

                  Comment

                  • Spoon
                    Administrator
                    • Apr 2002
                    • 44376

                    #10
                    Re: Start of Cd Ripper very slow (70 secs)

                    You could enable debug mode for dbpoweramp (dBpoweramp configuration >> music converter tab >> debug check)

                    Then start cd ripper and end task 20 seconds into the delay, the debug log will appear and show the last action cd ripper was taking.
                    Spoon
                    www.dbpoweramp.com

                    Comment

                    • Oliviander
                      • Sep 2010
                      • 36

                      #11
                      Re: Start of Cd Ripper very slow (70 secs)

                      Hi Spoon and Brody Boy

                      1. Windows Internal didn't help

                      2. No Event visible in the event viewer

                      3. Debug log:

                      Using SCSI PassThrough [clCDDA::SetCommunication]
                      ->-> [frmMain::RefreshTrackListing]
                      Quitting Meta Thread: Quit
                      ->-> [clCDDA::ReturnDriveList]
                      Got drive B:\ ** not CD Rom, type: 3 [cddaSCSIPassTru::FillDriveList]
                      Got drive C:\ ** not CD Rom, type: 3 [cddaSCSIPassTru::FillDriveList]
                      Got drive D:\ CD ROM [cddaSCSIPassTru::FillDriveList]
                      Got drive F:\ CD ROM [cddaSCSIPassTru::FillDriveList]
                      Got drive G:\ ** not CD Rom, type: 2 [cddaSCSIPassTru::FillDriveList]
                      Got drive H:\ ** not CD Rom, type: 2 [cddaSCSIPassTru::FillDriveList]
                      Got drive I:\ ** not CD Rom, type: 2 [cddaSCSIPassTru::FillDriveList]
                      Got drive J:\ ** not CD Rom, type: 2 [cddaSCSIPassTru::FillDriveList]
                      Got drive Z:\ CD ROM [cddaSCSIPassTru::FillDriveList]
                      <-<- [clCDDA::ReturnDriveList]
                      ->-> [clCDDA::ReadTOC]
                      LBA FirstIndex: 0 last Index: 0
                      Type: Audio Track 0 LBA Address: 0
                      MSF FirstIndex: 0 last Index: 0
                      Type: Audio Track 0 MSF: 0/0/0
                      <-<- [clCDDA::ReadTOC]
                      <-<- [frmMain::RefreshTrackListing]

                      Any Clues

                      I also tried to kill DBpoweramp task just before the 70 secs were up
                      but no debug log appeared.

                      Comment

                      • dbfan
                        dBpoweramp Guru
                        • Jan 2011
                        • 937

                        #12
                        Re: Start of Cd Ripper very slow (70 secs)

                        Do you have 3 cd drives?

                        Comment

                        • Oliviander
                          • Sep 2010
                          • 36

                          #13
                          Re: Start of Cd Ripper very slow (70 secs)

                          Actually I have 2 physical and 1 virtual drive,
                          but even deactivating them all does not help.

                          Comment

                          • Oliviander
                            • Sep 2010
                            • 36

                            #14
                            Re: Start of Cd Ripper very slow (70 secs)

                            Hi Spoon,
                            not any idea from you, before I actually will reinstall windows7

                            Comment

                            • Spoon
                              Administrator
                              • Apr 2002
                              • 44376

                              #15
                              Re: Start of Cd Ripper very slow (70 secs)

                              No Ideas
                              Spoon
                              www.dbpoweramp.com

                              Comment

                              Working...

                              ]]>