I have the same problem, when I close a decent sized project sonar crashes. I know it crashes only when I try to open it again and it doesn't open. bit bridge is usually running in the background I can close it and reopen sonar once. If I try this process again I'm usually not successful. This leads me to wonder is anyone using J-bridge having this issue? I want to buy it just to see if it solves this. This may be the reason some people are 100% 64bit on all plugins.

frankjcc


I have the same problem, when I close a decent sized project sonar crashes. I know it crashes only when I try to open it again and it doesn't open. bit bridge is usually running in the background I can close it and reopen sonar once. If I try this process again I'm usually not successful. This leads me to wonder is anyone using J-bridge having this issue? I want to buy it just to see if it solves this. This may be the reason some people are 100% 64bit on all plugins.

you bring up a good point,id also like to hear from those using J bridge and see if they have the hang problems us with bit bridge are.
because bit bridge is running here when this happens.
i have noticed though its mostly 3rd party plug ins that do it,32 bit plug ins.

I use JBridge and BitBridge but still get the dreaded crash and then Sonar not being able to be killed NO MATTER what I try. That includes TASKILL from CMD and also running 3rd party Process killer software. Its deffo a 64 bit issue....I have also tried killing the bitbridge process tree. I have tried killing ALL the audio processes and services but Sonardpr.exe still wont give up the game. 
"Share with other programs" is selected also.

Seriously, I have tried EVERYTHING to rectify this issue (I'm actually a Microsoft Network Engineer so I know a few things about PC's) and there is NO way round it.

chuckebaby

frankjcc


I have the same problem, when I close a decent sized project sonar crashes. I know it crashes only when I try to open it again and it doesn't open. bit bridge is usually running in the background I can close it and reopen sonar once. If I try this process again I'm usually not successful. This leads me to wonder is anyone using J-bridge having this issue? I want to buy it just to see if it solves this. This may be the reason some people are 100% 64bit on all plugins.

you bring up a good point,id also like to hear from those using J bridge and see if they have the hang problems us with bit bridge are.
because bit bridge is running here when this happens.
i have noticed though its mostly 3rd party plug ins that do it,32 bit plug ins.

The fact the the drivers are held on to is more likely just one of the results of Sonar hanging and not closing as it should on your system. Besides the audio driver there are a likely many other unseen resources that are held on to as well. You are just seeing the drivers being held onto as evidence of such resources being held.

This is not meant as anything more than to properly focus your troubleshooting.

Try this:

Run MSCONFIG

In the services tab, click Hide Microsoft services.
Now disable ALL other services that you see there

Click the startup tab
Disable all the startup items there

restart windows.

You will have less add on stuff running at this point and may not be able to print for instance
as you have turned off services.

You may have to go back into msconfig in and turn on your audio card services if they exist
but:

Run Sonar in this environment and see if it doesn't terminate as expected.

You can rerun msconfig again at any time to turn everything back on or only selectively enable things.

:Ron

Yes, Rebooting is GREAT!

:(

Anyone thats reading this and has the issue of SONARDPR.EXE hanging around, please IGNORE this crazy suggestion, it simply doesnt work.

I am getting sick and tired of useless answers to the release of the Process issue...... 

Restart, blah blah, defrag...blah blah...update drivers..blah blah...I could go on......

The fact of this matter is this. 

Its a Sonar issue thats hard to pin down in a 64 bit environment.

So, Sonar...****ing well deal with it.

Fellow Sonar users please stop posting ****ty work arounds that dont work.

bitman


The fact the the drivers are held on to is more likely just one of the results of Sonar hanging and not closing as it should on your system. Besides the audio driver there are a likely many other unseen resources that are held on to as well. You are just seeing the drivers being held onto as evidence of such resources being held.

This is not meant as anything more than to properly focus your troubleshooting.

Try this:

Run MSCONFIG

In the services tab, click Hide Microsoft services.
Now disable ALL other services that you see there

Click the startup tab
Disable all the startup items there

restart windows.

You will have less add on stuff running at this point and may not be able to print for instance
as you have turned off services.

You may have to go back into msconfig in and turn on your audio card services if they exist
but:

Run Sonar in this environment and see if it doesn't terminate as expected.

You can rerun msconfig again at any time to turn everything back on or only selectively enable things.

:Ron

I quit using Bitbridge and overall 32 bit VSTs in a 64 bit world. I went entirely to 64 bit plugs only. That greatly reduced the hanging of Sonar. The only thing I miss are the UAD plugins but they are going to be 64 bit by year end.

The fact of this matter is this.  Its a Sonar issue thats hard to pin down in a 64 bit environment. So, Sonar...****ing well deal with it. Fellow Sonar users please stop posting ****ty work arounds that dont work.

You're on a user based discussion forum (not official support)...
Why **** at folks who are trying to help?
Someone may throw out a tip to help you effectively work around the issue.
If not, what are you out?
You don't like the idea of "workarounds"... but the situation is what it is (imperfect).
Trouble-shooting and problem-solving is a HUGE part of what we do (as folks working with audio/technology).
Sour attitude won't help...

  UPDATE**** Well, 24hrs later after checking "share with drivers with other programs" button, haven't had a hang up yet. (Thanks Bob!) I realize I'm really tempting fate by typing that last sentence, but so far so good, thanks so much. I'm going to try bitman's MSCONFIG solution if the problem starts recurring, but for now I'm going to leave well enough alone. Thanks for all the suggestions everyone.

Interesting....   I always have that option enabled, and don't recall the last time I couldn't get the SONAR.exe to exit if needed (XP, Vista and Win7, three different interfaces).    I never made a connection between the two but now I wonder...
 

This has been a problem for a while now.
Sonar, once it hangs, requires like 7 minutes to close, unless I reboot.
It does not matter what converter you use, since people think that it is M-Audio, when it is not.
I just gave up on this issue and either wait or reboot.
I think Sonar can be programmed to exit.
But it seems like there is not a will to do it.
Maybe the original frame of the source code is too complicated to try to understand where to rewrite to make Sonar exit.
The reason I say this is because one time I wrote to CW and ask if they can put the slide latency bar for WDM driver to be put right on top of the main GUI. Imagine how easy it would be to change it back and forth, like slide it to minimum when tracking and raise it when mixing? I got an answer from CW that it is not easy to do so.  Lol, everything in nowaday programming is module.  So how hard is that to take that module and incorporate it to the main GUI? Meaning make a call to that submodule from the main GUI.
The only bad thing is that if it hangs while you forgot to save, then you loose everything you have done up to that point.
So I learn to save often. But sometimes I forgot when I am deep into it, like writing a part or recording a take, etc...
But on the other hand there are a lot of other things that Sonar exceeds when compared to other daws.
sincerely.,
dan le