In a "new" project with no 32bit/DX plugs this is still occurring to me as well. It doesn't hang for as long because the project is much smaller (I mentioned earlier it seems directly related to the size/complexity of a project) but it's still there.
 
No controllers attached. I do have a VRM Box though (setup VIA SPDIF on my Scarlett 18i6) but this, AFAICT, only started occurring with SPlat.
 
@H&E... do you have a VRM Box hooked up?

The obvious way to rule out the VRM box is to remove it... I would think your issue is extremely unlikely to be related to the OP.

Dok... it's EXACTLY the same issue. We established that early on in the thread and the similarities continue (as both of use have had a chance to see it occur beyond the original test paramters). I have not seen him post anything to the contrary. I am more familiar with this issue than others may be who are not experiencing it (obviously).
 
I am now trying to figure out what things H&E and I have in common in regards to our setups. Please do not dismiss troubleshooting/correlation attempts. This could expose a system specific bug/problem that can be reported and corrected.
 
Knowaddiamean? Not trying to be a dick but I would like to figure out WTF this is... especially if some are experiencing it while others are not.
 
Cheers

If either of you cannot "kill Sonar" it's almost certainly drivers or plugins. More likely drivers if only a reboot will resolve it (HAL is locking something).
 
If plugins are ruled out then it's drivers/firmware. If both of you have similar systems hardware then bingo (so sure not saying your question about running VRM is invalid), other than that likelyhood is both of you have got a dodgy driver (or related firmware) somewhere, but probably a different one. First thing to do is update your audio interface and drivers in your instance (it looks like you aren't going to do this so you can't rule this out as an issue, so basically this is a standstill.. fair enough if that's what you want ).
 
Yet another suggestion... Have any of you tried the delete AUD.INI trick? (google for details)... Ta...
Anyway I think everything possible here has been suggested it's just a matter going through it one by one.
 
It's definitely not a Sonar bug, if Sonar was a possibility it would crash and then be able to start without needing a reboot or being killed in task manager.. Sonar does not have priority over the operating system here, however drivers do.
 
BTW software being locked out by drivers is fairly common...

To answer an earlier question about what to do when you absolutely love some 32-bit plugins - you might consider installing a completely 32-bit Sonar, and 32-bit version of whatever 64-bit plugins you can.
 
This way, you could build some projects completely in 32-bit mode, where nothing should be bridged, and you would have only the limitations of potentially not having access to some plugins that didn't have a 32-bit version, and also the limitations of a 4 GB address space - overhead.
 
But at least it should all work, and you could run like that for quite a long time, and you would have the choice of which bit-version of Sonar you want to build a given new project with.
 
Bob Bone
 

Well thanks to ALL especially Dr A I think I found my millstone...
 
My MOTU midi express 128 was keeping it held, I turned off devices one by one until Sonar Killed!!!
 
I have the latest 64 bit driver so may google the problem.

Ham N Egz
Well thanks to ALL especially Dr A I think I found my millstone...
 
My MOTU midi express 128 was keeping it held, I turned off devices one by one until Sonar Killed!!!
 
I have the latest 64 bit driver so may google the problem.

Assuming you are on the latest driver/firmware, may I suggest your first course of action may be to uninstall the driver/reboot/reinstall it/reboot/reset your interface settings on hardware and software (assuming there is such an option on your interface) and reconfigure it.
 
Also look at deleting AUD.INI if that does not work (google for details).
 
Cheers..

OK part 2
I don't know which of the two fixes helped but
1  I removed and reloaded the 64 bit driver
2  and I think this was it, the MOTU was plugged into a USB 3 port I move4d it to a USB 2 and now Sonar behaves itself.
 
thanks to all for the thought processes ..

MANY audio interfaces completely freak out if they are plugged into a USB 3 port, rather than a USB 2 port.
 
I have had it happen in the past, and my current audio interface had some patches to it that let you use either port, but I still generally plug it into a USB 2 port.
 
Some older computers may still have 1 or 2 USB 1.1 ports, and those might not work very well either, for many different brands/models of audio interfaces.  They mostly seem to like USB 2 ports, from what I have seen/experienced.
 
Bob Bone