Sonar Professional now at a snails pace

I must admit that I, too, am experiencing slow loading projects. Even projects with just a couple of tracks. Taking about twenty to thirty seconds to open, which isn't that long, really, but seems to be a long time when you are used to them opening "almost" straight away.
 
No tips from me other than look away from the screen... As the saying goes, "a watched pot never boils."
 
cheers
 
andy

I have not seen a problem with Sonar opening any slower but plugins that use lots of samples like Kontakt can take a while to load. So I would look at the plugins you have in the project to see if they are the reason.
 
 
 
 

I have SSD system and data drives so perhaps that's why my projects are opening a little bit quicker.
 
To be honest, I really need to do a bit more research on exactly what is happening my end. I am probably not helping matters by sometimes using my OCTA-CAPTURE and then switching to my QUAD-CAPTURE when I am not in my studio.
 
Not using any sample libraries as such. I do have Iris 2 loaded in one project that is slow to open but I only have small local samples loaded... So many things to consider I guess...

I have Sonar Professional, W10. Projects open in about 3-4 seconds.

I shall now check with Windows defender off as well, just to update on the issue when I opened Sonar and monitored the CPU in task manager it only got to around 7% usage. What I did notice though was that the Sonar start screen appeared around 3 or 4 times in the process list, has everyone else got that many on launch? The command center also opened but has now gone.

Dunno if I'm just being stupid here but when I make changes to open elements of Sonar the configuration is not saved with  the project. I close browser and inspector and they still open again after saving and re-opening.
 
The initial lag is also before any project is even open.

mattburnside
Also, has anyone any experience is stopping Windows Defender from affecting Sonar besides completely disabling it? White list maybe?
 

Windows Defender seems to be transparent, in my experience, by excluding the following:
 
Program Files \ Cakewalk folder
Sonar executable
File types - .cwp, .cwt, .wav, aif, .flac, (or any other audio format)
Projects Folder (I actually exclude my project drive)
VST Scan path(s)
 
Some of these are redundant, but that's where I ended up.
No issue with Defender in a while now.
 
Good luck! 

Does it happen with every project or just some projects ?
If you have an older VST or one that is having problems loading, this will surely create a delay in start up.
Give me a few and I will check task manager for multiple start screens but I don't think that's it.

Are you opening projects within SONAR or by double clicking them on the desktop?
If so do you see the same delay when you open the project within SONAR? 
You can also try disabling the start screen if your web connectivity is slowing things down.

Have you tried disabling the start screen? If SONAR is opening without a file or template, there is no reason for the app itself to take excessive time to start unless some driver or control surface is blocking taking a long time to initialize. 

SONAR takes about 3 seconds to start up here. Loading a specific project, of course, can take a long time depending on how many sampled instruments it contains. I have one I'm working on ATM that takes over 3 minutes the first time I load it after rebooting, but only 30 seconds the second time I load it due to disk caching.
 
Seeing that lag while the start page is initializing suggests some kind of I/O issue. A failing disk drive could be one explanation, e.g. SONAR requiring multiple retries while reading the thumbnails. As Noel says, SONAR isn't doing any intensive processing at that point. If I disable the start screen, that only knocks maybe 1 second off the load time. If you can actually see that screen's elements being painted then something outside of SONAR is dragging you down.
 
It might be informative to pull up Task Manager and watch it while SONAR is loading. See what other processes are running and if any of them are eating CPU. Look at the performance tab and see if there is excessive CPU, memory or disk activity. Open the Resource Monitor to find out which processes are using the most resources.
 

Noel Borthwick [Cakewalk]
Have you tried disabling the start screen? If SONAR is opening without a file or template, there is no reason for the app itself to take excessive time to start unless some driver or control surface is blocking taking a long time to initialize. 

 
I don't know how to do that - I will look it up and see if it makes any difference.
 

bitflipper
SONAR takes about 3 seconds to start up here. Loading a specific project, of course, can take a long time depending on how many sampled instruments it contains. I have one I'm working on ATM that takes over 3 minutes the first time I load it after rebooting, but only 30 seconds the second time I load it due to disk caching.
 
Seeing that lag while the start page is initializing suggests some kind of I/O issue. A failing disk drive could be one explanation, e.g. SONAR requiring multiple retries while reading the thumbnails. As Noel says, SONAR isn't doing any intensive processing at that point. If I disable the start screen, that only knocks maybe 1 second off the load time. If you can actually see that screen's elements being painted then something outside of SONAR is dragging you down.
 
It might be informative to pull up Task Manager and watch it while SONAR is loading. See what other processes are running and if any of them are eating CPU. Look at the performance tab and see if there is excessive CPU, memory or disk activity. Open the Resource Monitor to find out which processes are using the most resources.
 

Typically, the day I decide to time it, it opens quicker than usual, but still not what you'd call quick.
 
I'm not very familiar with what is what in windows, but FWIW here is what I observed...
 
At rest after boot and doing nothing else there are 10 Processes running, the most significant sizes being..
 
windows explorer 23,412k
desk win manager 10,548k
 
the other 8 look to be insignificant to me - much smaller numbers.
 
Performance at idle
 
cpu 0-5% max spike but mostly hovering around 0/1%
 
RAM 1.18GB (of 8)
 
Plat time from initiation to start screen 1:18 during which RAM remains largely static, increasing to 1.25GB at times
 
CPU max spike at 41% after 30/40 secs but under 10% for the majority of the time.
 
Means nothing to me other than suggesting that it could be working harder.
 
Sounds like my school report ! 
 
 
As far as project times go, it does vary, but always seems slower than x3 was. I didn't time any today, but as a rule they contain mostly frozen softsynths and audio tracks with a few fx, but nothing that taxes even my puny by modern standards system too much. I presume that any samples etc are not loaded into RAM again unless I unfreeze, so effectively they are all audio tracks anyway? Generally I don't leave many melodyne clips open either, maybe one or two, but I always break them up into short phrases so there shouldn't be much going on there as a rule.