002 rack keeps losing asio driver in cubase 4.5

[nincompoop]

Hey all,

recently did a full clean reinstall of my XP pro partition, SP3 on a mac pro under bootcamp 2.1, cubase 4.5.2
My setup used to run fine, for 2 years, and I reinstalled everything exactly as it's always been.
Sice the new install, I keep getting the " digi 002 rack asio drive rnot connected "message when opening a song.
I then open the device menu and rechoose the driver, and it mostly works whenI just booted XP. But during work sessions, after closing C4 a couple of times and working with other apps such as soundforge 10, I reopen cubase and the driver is gone again, when choosing it in devices I get either a "bad device" message or " unknown error".
I tried changing Firewire ports, using different protools drivers, the standalone as well as the full install of 7.3 etc, same thing.
Why is it that I get that since the new install, and what could be the troublemaker? I always have to reboot to get rid of the problem.
I should mention that even when the digi002 is unable to connect to cubase, I can still choose it as the audio asio device for soundforge and it works there. That is why i suspect it to be a C4 issue, but not sure. Strange that it only occurs after my new clean XP install.

grateful for any hint!
Thanks!

[koo_koo_bonkers]

My system

• Asus P5E-VM HDMI updated drivers
• Windows XP pro Sp3 updated
• Using the on-board firewire port
• 003r
• Digidesign ASIO Drivers v7.4
• Pro tools LE is not installed
• Reason 4.01
• Kore2.1.0.9
  

Intermittently KORE2 or Reason cannot connect to the 003r as the ASIO driver is unavailable. Reason reports "Sound driver problem. The sound driver used in the previous session could not be opened." and Kore brings up its sound driver preference clearly showing the Digidesign ASIO driver is not available. To get it working I end up shutting down the computer and also restarting the 003r before a connection can be restored. When I do get the driver running in KORE2 or Reason I have to setup the driver preferences in each application again from scratch. This is killing my workflow.

At any time Soundforge (8.0d) can connect to the 003r with no problems.

[BScout]

I can guess the problem but can't give you a solution. The Digi drivers aren't multiclient and Soundforge (most likely) is not releasing the driver when shut down so the other two apps can't use it. Most modern audio devices with ASIO drivers are multiclient so this doesn't matter but Digi didn't do that.

I'd also make sure that the "sounds and audio devices" control panel does NOT have any of the digi hardware set as default hardware for system sounds, etc. Also, if Soundforge has a "release audio driver" option like Cubase, I'd check it.

[nincompoop]

Hi BScout,

Sondforge never uses the digi asio drivers, but the internal mac soundcard when I use it with Cubase open. Also, Windows only uses the internal device.
The whole problem appears to be random, sometimes C4 would have no problem, sometimes it would not find the drivers, and I don't think any other app is interfering with the sound devices - I rather suspect that the firewire port might be unaccessible to cubase for some unknown reason...but just speculating.