• SONAR
  • Sonar stays in memory after close
2015/06/27 10:07:40
jkoseattle
Most of the time when I work on music projects, my work time is concluded with (and due to) a Sonar crash. I have come to accept this as the norm, though every session is concluded with a string of expletives at Cakewalk. Knowing how time-consuming it is to track such things down, I have just lived with it. 
 
However, one thing seems really troubling, and that is that I can't get SONAR.EXE out of memory after it crashes, which requires a complete reboot of the PC. After a crash, the Task Manager shows Sonar right up top consuming 2Gb of RAM. Choosing End Process does not clear it out. Any idea what's happening?
 
Also, because my projects are thick and complex, they can take 5+ minutes just to load, so on the occasions where a Sonar crash does not end my working session I will leave the project open, and sometimes it is a few days before I can get back to it. I only use the computer for Sonar, iTunes and light web browsing. Is there a reason why leaving a project open like that would cause problems?
2015/06/27 10:11:16
Doktor Avalanche
What happen when you get rid of your 32 bit plugins?

Otherwise you should be looking at a particular plugin as the cause of this first.

Also try disabling antivirus.

I strongly recommend shutting down your PC at the end of the day if only to keep up your green credentials and reduce your electricity bill. Generally keeps your machine running more smoothly as well...
2015/06/27 10:37:45
jkoseattle
Thanks for the quick reply. How do I know which of my plug-ins are 32-bit?
 
Also, my hard drive is spinning like crazy all the time. Looking at the disk chart in resource monitor, it's maxed out much of the time, no surprise since I can hear the thing working anyway. 
 
 
2015/06/27 11:05:48
mudgel
How old's the hard drive. If it's spinning all the time maybe that's a clue as to a problem especially if projects are taking 5 minutes to load.
2015/06/27 11:07:50
synkrotron
jkoseattle
How do I know which of my plug-ins are 32-bit?

 
I click on a plug-in in the Browser and right at the bottom of that window it gives some details on that plug-in, including whether it is 32 or 64 bit
 
cheers
 
andy 
2015/06/27 11:21:22
Beepster
You seem to have a couple of M-Audio devices listed in your profile. I have seen lots of reports about M-Audio stuff not releasing Sonar from memory/taks/etc. I don't fully understand this issue because the only M-Audio device I own seems to work fine but I have seen this issue mentioned before (but not for a long time). I know others have found a solution so perhaps anyone who remembers all that can provide some help.
2015/06/27 11:29:12
jkoseattle
synkrotron
jkoseattle
How do I know which of my plug-ins are 32-bit?

 
I click on a plug-in in the Browser and right at the bottom of that window it gives some details on that plug-in, including whether it is 32 or 64 bit
 
cheers
 
andy 




What browser? I don't see anything that says that. Plug-in manager? The Synth window itself? 
2015/06/27 11:44:32
Beepster
jkoseattle
synkrotron
jkoseattle
How do I know which of my plug-ins are 32-bit?

 
I click on a plug-in in the Browser and right at the bottom of that window it gives some details on that plug-in, including whether it is 32 or 64 bit
 
cheers
 
andy 




What browser? I don't see anything that says that. Plug-in manager? The Synth window itself? 




He's talking about the Media, Synth, Plugin Browser (press B to open... but you know that). It seems if you click on an entry at the bottom of the Browser it provides additional info on the Plug. I had never noticed that until just now.
 
Pretty cool, Andy. Thanks.
2015/06/27 12:12:56
mudgel
Adq
http://forum.cakewalk.com...yannoyed-m2640092.aspx


That's a 3 year old thread related to an issue with X1.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account