I posted this issue in an earlier thread, but alas, I'm still having the same issue at times. Sometimes, when I'm trying to close a complex project, Sonar X2 hangs and won't close. I have to go to task manager and try to kill it there, and sometimes that doesn't work either, requiring a reboot. The reason it won't close is that Sonar won't let go of the drivers. If I try to start another audio program, Windows tells me " the device is in use elsewhere and unavailable." Some suggestions I've gotten include: Stopping the audio engine before closing. Removing any unused drivers from system. Killing anti-virus. All to no avail..sometimes. Now, granted, some of my projects are quite system taxing, including, several soft synths and guitar amp sims. And I'm not at all sure that they aren't the source of the problem. But after a long complicated session, I cringe when I have to exit the program because I know there's a 50/50 chance that I'll be spending 3 to 5 minutes finally getting Sonar to release the drivers. Is there some rock solid, no doubt about it way to kill any driver use, so I can close the program without issues and be on my merry way? Thanks in advance for any suggestions.

+1 million.

This drives me ****ing crazy and I keep barking on about it.

Whats your card? M-Audio?

  I HAD m-audio and ditched it for a Roland Quad-Capture, hoping that would do the trick. No such luck.

I know this shouldn't be a required thing - bear with me.

Have you tried checking the box to tell Sonar to Share Drivers With Other Programs?

It is in Edit>Preferences>Audio>Playback and Recording.

Just a thought, maybe it wouldn't hang.  I had not had it checked, and also would have to kill SOnar through reboot or through Task Manager, but there was one tune I was working on, where I was using another program to play back a track at a slowed speed, and I went in and checked that box so that I could run both audio programs at the same time, and ever since then, I have not had Sonar hang like it used to.

Just give it a shot and let me know if that had a positive effect on things or not, 

Bob Bone

robert_e_bone


Have you tried checking the box to tell Sonar to Share Drivers With Other Programs? 

This is worth a try. So I set it. We'll see if it makes a difference. There is a new Windows shared API in audio, but I'm not sure that works in ASIO? It could be just in WDM, does ASIO fall into that bag? I don't know.

EDIT: I should add that I had a few crashes like this in the 306 build, but so far no crashes in the 308 Quickfix.

I do not have the quick fix installed - it didn't look like it applied to me, and it said not to install it if you were having those specific problems.

So, with that box checked on my system, I have had no further hangs like I had before - hope this will fix it for you, 

Bob Bone

I've had many hangs, so I'll try that trick tomoro... my prob is I'm getting these prog freezes in various operations.  

Update:  I had already enabled that option, so that doesn't help me.

  Thanks Bob, I'll give it a shot. Don't know how effective it will be however, because usually when I get those bad crashes and try to restart X2, even X2 tells me the drivers are unavailable!

Sonar sometimes hanging on to drivers after closure/crash is a long-standing issue (though it did improve with X1). Prior to X2 checking in Task Manager if bitbridge was still running then killing the bitbridge process tree sometimes solved the problem.

I've just had X2 crash following clicking on a step sequencer window (white screen).

Task Manager couldn't kill it, and bitbridge no longer running. I openned a command console window (what used to be called a DOS window) and used the TASKLIST  command to get X2's process number then TASKKILL with the /f switch set to force X2 to shut down.

The whited-out X2 window remained open. Re-running TASKLIST showed X2 still running with the same process ID. Trying TASKKILL again got the response "the process was not found" - i.e. Windows thinks X2 is shut down when it isn't.

Time for another bug report......

by far the only thing i wish i had control over.
i too thought it may be a m audio driver at first,but i dont have them installed anymore because i thought thats what was causing my hangs.
hopefully in the future something can be done to kill the driver apon a crash.