SF 10 seems to block asio access in cubase -Sound Forge - PC

Subject:SF 10 seems to block asio access in cubase Posted by: Mindmatter Date:11/18/2009 9:15:35 AM 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 I also upgraded to SF 10.0a 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 driver not 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. But thing is: 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. so, although SF runs only through the internal mac soundcard, I suspect that it blocks access to the asio drivers in some way. So I tried today to close SF10 every time before opening Cubase, and aha - the drivers were always available. Besides, SF 7 did not cause any problems and the problem seems to have started since the use of SF10. Couls it be that SF10 "secretly" accesses the asio drivers although it runs on the microsoftsopund mapper? grateful for any hint! Thanks!
Subject:RE: SF 10 seems to block asio access in cubase Reply by: pwppch Date:11/18/2009 9:41:28 AM Forge does not connect/allocate devices it is not using. Make sure that Windows is not mapping the DIGI hardware to the default sound device. Peter
Subject:RE: SF 10 seems to block asio access in cubase Reply by: Mindmatter Date:11/18/2009 11:58:31 AM Hi Peter, default device in Windows is always the internal mac card in my setup. It does not solve the problem, as that has been the setting from the start.

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 I also upgraded to SF 10.0a
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 driver not 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.
But thing is: 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.
so, although SF runs only through the internal mac soundcard, I suspect that it blocks access to the asio drivers in some way.
So I tried today to close SF10 every time before opening Cubase, and aha - the drivers were always available. Besides, SF 7 did not cause any problems and the problem seems to have started since the use of SF10.
Couls it be that SF10 "secretly" accesses the asio drivers although it runs on the microsoftsopund mapper?
grateful for any hint!
Thanks!