KVR Audio

Roman Empire · Post by **Roman Empire** » Fri Apr 08, 2005 11:14 am

Hi folks

I´ve been looking for a solution to the following problem:

It happends sometimes that cubsae hangs or crashes. In those cases I wont be able to load it again, using my ASIO driver. It´s kinda locked by the terminated process.
Unfortunately all I could find on this was other people with the same problem.
Rebooting of course solves the problem, but it would be so nice if there would be a way to unlock the driver without so much effort.
So just wondering: Does anybody know about something which will do this?
I´m using the last VST build, I think it´s 3.51 (not at home so I cant check) and NOT SX.
My soundcard is an staudio DSP24.
I know that this kind of error is not unique for my card nor for ASIO. It can also happen just with normal sound card drivers.
I hope someone´s got a solution.

Thanks!

crusces · Post by **crusces** » Fri Apr 08, 2005 11:28 am

I had the same sort of problem. What usually did the trick was:
* Open windows task manager.
* Select a random proces
* Right-click on the proces
* Select "End Proces".

Windows will now warn you that this is a dangerous thing. This goes accompanied by a short .wav alarm. In order to be able to play this, Windows must reclaim the sound card from whatever was keeping it. It's not really scientific or proven to work, but it might save you from a reboot.

And don't kill that proces

isdjan · Post by **isdjan** » Fri Apr 08, 2005 11:44 am

crusces wrote:[...]And don't kill that proces

...unless it's cubase

farlukar · Post by **farlukar** » Fri Apr 08, 2005 11:44 am

Maybe there's something in your soundard's control panel like "reset values" or "factory default" that also resets the driver?

crusces wrote:And don't kill that proces

or kill "System Idle Process", it's just taking up all your clock cycles anyway

Roman Empire · Post by **Roman Empire** » Fri Apr 08, 2005 11:54 am

farlukar wrote:Maybe there's something in your soundard's control panel like "reset values" or "factory default" that also resets the driver?

crusces wrote:And don't kill that proces
or kill "System Idle Process", it's just taking up all your clock cycles anyway

No, unfortunately not, I looked into that already because I know there are audio cards with that feature.

Roman Empire · Post by **Roman Empire** » Fri Apr 08, 2005 11:56 am

crusces wrote:I had the same sort of problem. What usually did the trick was:
* Open windows task manager.
* Select a random proces
* Right-click on the proces
* Select "End Proces".

Windows will now warn you that this is a dangerous thing. This goes accompanied by a short .wav alarm. In order to be able to play this, Windows must reclaim the sound card from whatever was keeping it. It's not really scientific or proven to work, but it might save you from a reboot.

And don't kill that proces

Cool, thanks for that

Unfortunately this wouldn´t make a difference here.. I can most of the time still play wave files - I know because I then after the problem with cubase have been using winamp with no problems.
So that´s why in this case the issue in particular is with ASIO, but prolly similar to when it happends to a normal audiocard driver.

boin · Post by **boin** » Fri Apr 08, 2005 4:09 pm

Roman Empire wrote:It happends sometimes that cubsae hangs or crashes. In those cases I wont be able to load it again, using my ASIO driver.

It happens to me from time to time - normally when I'm trying some new plugin (FL / MiniHost, P4, M-Audio Delta-44). A workaround is to have another ASIO driver available.

Install ASIO4ALL. In my case only version 1.8 works - the new ones up to 2.5 have some problem with my system. If you can't use your native ASIO driver then just open the app and change to ASIO4ALL. Works well for me.

Another point: it seems that the ASIO driver is released some time after a crash occurs. At least I was able to open FL normally if I waited long enough. Can anyone shed some light on this?

snareSpanker · Post by **snareSpanker** » Fri Apr 08, 2005 4:43 pm

I think Tracktion actually has a "reset ASIO" button...

Roman Empire · Post by **Roman Empire** » Fri Apr 08, 2005 7:36 pm

snareSpanker wrote:I think Tracktion actually has a "reset ASIO" button...

It´s called restart device, I think. Just tried downloading both Tracktion 1 and 2, but none of them were able to do it

Sicklecell666 · Post by **Sicklecell666** » Fri Apr 08, 2005 7:42 pm

ASIO crashes here require a full restart. I was told that FL can force a frozen ASIO link through again, but I keep forgetting to try..

cptgone · Post by **cptgone** » Fri Apr 08, 2005 8:16 pm

Sicklecell666 wrote:ASIO crashes here require a full restart.

...if I want to use the SAME driver again, yes. But I'm always able to go on with the other driver, the one that hasn't crashed, without rebooting.

Roman Empire · Post by **Roman Empire** » Mon Apr 11, 2005 2:19 pm

I just tried ASIO4ALL, but unfortunately the driver becomes unavailable to choose there once the "real" one has crashed.
I gotta try Fruityloops though... maybe there´s our solution!

Stupid American Pig · Post by **Stupid American Pig** » Mon Apr 11, 2005 2:49 pm

Usually application crashes do not release the ASIO driver, depending on the app and driver used you may not be able to do anything about it. I find that a reboot is the best remedy, but you can also try:

a) disabling the audio device in device manager, then reenabling it.
b) my card is external and has its own power switch, sometimes I can just turn it off and wait for a moment, the stuck process sometimes releases the driver when the device isnt present.

But luckily crashes are so rare on my system that I dont mind rebooting.

A way to reset ASIO (audio-) driver?