SonarPLT not releasing projects has to stop please.

It's the only truly irritating thing in the new build, IMO. I don't really care if it's plugins or whatever - please find a way to force Sonar to close all projects, every time. I can't be expected to Task Manager - "End Process"  in front of clients - it makes them nervous, and it's bad bad PR for Cakewalk.
 
Thanks!
L.

This is not normal behavior. I can't recall this ever happening to me. In the past when people had this issue it was often due to a hanging driver that wouldn't close or give Sonar the proper handshake to release it. M- Audio was known to have this problem.
 
A driver update may be in order.  

When these issues were solved in the past, the usual culprits were either drivers not releasing, or issues with bridged plug-ins where the bitbridge server didn't close. Not sure if those are things that Cakewalk can address.

BobF

John
This is not normal behavior. I can't recall this ever happening to me. In the past when people had this issue it was often due to a hanging driver that wouldn't close or give Sonar the proper handshake to release it. M- Audio was known to have this problem.
 
A driver update may be in order.  

This has been my experience as well.  Not saying it's the root of the OPs problem, but should be ruled out to clear the path for other troubleshooting

I've had this happen with all versions of Sonar and it still happens with Platinum (definitely nothing 32 bit involved anymore) - I know in my case it originates from the Roland drivers (which aren't going to be updated, but they fit the OS I'm on), which are not interacting too well with some 3rd party software (K5 in my case, which is also a known issue at NI) ...
 
Nevertheless, Cake has to find some way to keep Sonar from crashing/hanging when the audio drivers give up for whatever reason ...
 
BTW, the OP is running what is probably the most stable audio interface driver there is ... which also happens to be what Cake officials are using themselves ... so ???

FreeFlyBertl
Nevertheless, Cake has to find some way to keep Sonar from crashing/hanging when the audio drivers give up for whatever reason ...

 
I'm not sure that Sonar can know the drivers have given up if they're hanging. It probably thinks they're still doing their thing. I get the impression that drivers tell SONAR what to do, SONAR doesn't tell the drivers what to do. I could be wrong.
 

BTW, the OP is running what is probably the most stable audio interface driver there is ... which also happens to be what Cake officials are using themselves ... so ???

Could be a 32-bit something somewhere...

I have too suffered this in the past and ranted a few times on the forum about it.
 
Hasn't happened for a while now (touch wood)

Doktor Avalanche

LJB
The more you can educate your users, the less trouble you have.
 
Ludwig

Google! Or read the forums every day and educate yourself. Generally driver, firmware, plugs or not keeping your maintance up to date. Educating yourself is your responsibility nobody else's :)

 
Bit of a glib reply there Doc. I do what I can when I have the time, but I expect paid-for stuff to work, so that I can have the means of paying for it :O)

More to the point, it's fine to say users should get educated, and I of course agree, but if a service or product provider wants less traffic in the complaints dept and more available resources in the R&D and Sales dept, they need to make the essential info available to the users in an-easy-to-understand format. That's why, for instance, some ISPs are giving away free routers - so that one less unknown is removed from the equation. And that's why trouble-shooting checklists have been part of gear manuals for years. It saves time and money in the end.
 

LJB
Well, this problem has been around for several Sonar versions, under various error messages. I had Win 7 Ultimate and now Win 10, which is luckily more stable, except for that error.
It may well be worth Cakewalk's time to write some sort of a PC/OS debug tutorial then - even if it's not their bug. Where the heck do I even start looking - I make music!
The more you can educate your users, the less trouble you have.
 
Ludwig

Definitely something specific to your environment if it has been around for several versions. Its not the driver since I have the same interface and never have this issue. To troubleshoot you should see if there is something specific to your projects that causes it. Use a process of elimination - start with any project and keep removing tracks and plugins and saving versions until the hang stops happening. Then back track and find what you changed. 
Obviously we can't fix it if we cannot repro the problem or understand better what is causing it on your setup.
 
PS: Also to start out eliminate all other hardware - disable your MIDI interface, remove any control surfaces etc and see if the problem still occurs. There have been some MIDI drivers that hang on exit.

You might be best to use something like Process Explorer or Process Monitor from Microsoft and start digging into the system to see what processes are locking on what. Is a process hanging on a registry entry, a permissions issue, a file locking problem.
 
I use Process Monitor quite heavily for troubleshooting application problems through my IT job. It will tell you everything a process is trying to do when opening, running, closing from opening files, accessing registry entries etc. It can be quite daunting to use at first, but once you figure out filtering options and start looking you might just stumble on what is causing the problem.
 
If I get time I'll have a look at my system later on and see if I can write a quick how-to that might point you in the right direction. Thought I would just mention it quickly to get you started.
 
EDIT: Found some resources to help with using Process Explorer:
http://www.howtogeek.com/...rnals-pro/lesson3/all/
http://www.howtogeek.com/...rnals-pro/lesson5/all/

Fabio Rubato
What I find perplexing is that my Roland Quad - as mentioned in my last post - routinely hung after Plt stopped working. Now with the same project - nothing else changed in terms of vst's etc - and using RME UFX drivers, this doesn't happen. Even if Plt crashes - rare - the drivers are released almost immediately. I'm don't have the time - or tech head - to 'nut this out'. I'm just grateful that this on-going issue is solved. 
 

I think this is a Roland specific driver issue that you cannot sort out yourself anyway.
 
I'm seeing similar issues with Octa-Capture and VS-700, both Roland. Sometimes master out goes silent (and requires Sonar restart or changing ASIO buffer size to re-init audio drivers), sometimes it hangs when closing Sonar and sometimes Sonar exists normally at end of session but the DAW does not shut-down as the driver got stuck in the background keeping windows from shutting down ...
 
Good thing is that these drivers are no longer maintained (at least the VS EXPAND version of it that gives you all the I/O) and eventually I will migrate to RME (I hope you sense the irony)

Not sure if this post will go through (the forum seems to have dropped it's CSS page again) however...
 
Recently when I close a project it takes WAY longer before I can reopen Platinum. The length of time seems to be tied to how large/complex the project is. In previous versions I did usually have to wait a second or two before I could reopen Sonar but these days it can take as long as 30 seconds or more (on larger projects) and at minum around 5-10 seconds.
 
So I'm not sure if it is related to this but something is different and making me wait longer before I can reopen Sonar. Just to be clear the Sonar windows closes normally. It is just when I go to reopen Sonar I can't for a certain length of time. I click on the launch icon and nothing happens. I open and close projects often as I work (for various reasons) so it does kind of get annoying.
 
It has not gotten so bad that I have to use Task Manager though. I did have a bit of an issue the other day where I (accidentally) tried to open a different project while another one was open. This led to a severe hang and I eventurally had to use Task Manager to close SOnar (which did not work the first couple times). AFAIK I should be able to open another project while another one is open.
 
Anyway... just posting my experience in case it's related and leads to the Baker's fixing something. I was (and still kind of am) under the impression it was something on my end and was going to post a thread asking about it (eventually).
 
Cheers.
 
Hope this posts.

I suggest launching Task Manager while one of these projects that hangs on close is still open, and check to see if either BitBridge or JBridge is running, as that would indicate that a 32-bit plugin is being bridged to run in a 64-bit Sonar.
 
I used to have various issues like the above when I was still running with some 32-bit plugins, but since I deliberately made a conscious decision to move all the way to 64-bit third-party plugins, things have been WAY more stable.
 
If you can identify and swap out any 32-bit plugins for some 64-bit equivalent or upgrade, then you might see a lot more stability with your system, assuming maintenance and other environmental aspects are OK.
 
Sorry you are having these frustrations - on my exclusively 64-bit system, things have been very very stable for several years now.  Hope that helps you, and in any case, I hope you can get past these issues.
 
Bob Bone
 

Genghis
I haven't had this issue since I ditched my old MidiSport 8x8 MIDI device several versions ago.  I figured out then that it was the culprit and would simply shut it off when it hung, wait a few seconds for good measure, then turn it on again.  The process would die when I shut it off, and then the OS would pick it back up when I started it again.  Fortunately I don't use external hardware synths any more, so I sold the MidiSport and don't have the problem now.
 
The only advice I can give is to do some testing (Noel's method looks pretty sound) and figure out whether it's a bridged plugin or a driver.  Personally, I'd suspect hardware first, plugin second, unless you do a lot of bridged plugins. 

Same here with the early Delta drivers and MIDISport 2x2.  If Sonar ever got hung up, first step was to unplug the MIDISport.  That released the Sonar process 99% of the time.
 
 

Check windows event viewer.. paste errors here. That may speed things up.

We need steps to repro and full list of specs as well. Some good advice has already been given. We will simply need to go through the same troubleshooting steps we use for everybody else. And there is always Cakewalk support if OP needs help quicker. Ball in OP's court.

Ta.