• SONAR
  • Very slow project loading - any fixes? (p.3)
2013/03/06 08:17:18
Guitarhacker
Doing the disk defrag and the other scans is good.... also consider a registry scan/repair. Every time I do a registry scan it finds a number of issues.  Good links to locations helps it find things faster. 

That may or may not help. 

It kinda sounds like it's taking the time to load lots of things from disk to memory. I would try an experiment. 

Start a new project and record or drag in one audio track... it can be any audio. 

Close X1 and then reopen it. Note the time. Now add one synth track and record a few measures. again repeat the close/re-open and note the time. 

Your post #20 says that you believe it IS a VST causing the issue. 


There may be one synth in particular that is the culprit. One synth that is taking 4 minutes to load. You may just need to find that one, and it may take some detective work to do. 

Keep notes on what synths are in the project. Then, if and when you find a synth, that when added, causes a long load time, delete if from the synth rack so it's gone from the project and repeat the close/reopen. 

add it again.... recheck the load time, and then remove the OTHER synths and recheck.... It may be one synth, it may be several..... but unless someone else has the definitive answer, this is how I would start on the quest to locate the reason for the long load times.

You can and should also do this if you have not yet done so. Cold boot the the computer and when you run Sonar, RIGHT CLICK the icon and select Run as Administrator.  Don't ask me the particulars but doing that will sometimes allow it to run normally and do what it's supposed to do even when you simply run as a user from that time forward. It's worth a try. I know doing this has solved some other issues in the past for a few people. 


If all else fails, an email to tech couldn't hurt.... just be patient on the reply. 
2013/03/06 11:10:39
moebiuscat
The thing is that it only takes a long time after the cold boot. Then if I close X2 and open it again - project takes 18 seconds to load... I already tried it with removing instruments from the rack one by one. Addictive Drums is the worst (3 min), others are more or less equally spread.
2013/03/06 11:16:31
twaddle
moebiuscat


The thing is that it only takes a long time after the cold boot. Then if I close X2 and open it again - project takes 18 seconds to load... I already tried it with removing instruments from the rack one by one. Addictive Drums is the worst (3 min), others are more or less equally spread.

That's interesting, have you tried cold booting, opening sonar but not loading any projects, then closing and reopening sonar and seeing if still take 4 minutes.
What is the time gap between cold booting and opening sonar? you would think there was some process running at windows start up that was using your ram or cpu but if that were the case
it should also effect cubase.


Steve
2013/03/06 11:18:03
Guitarhacker
AD takes 3 minutes?  That's where I would spend time looking. If they have a forum, go there and ask this question and or contact their support. It sounds like it might be loading tons of samples and not just the one kit it might need. 

Come to think about it, I believe Jamstix ...also a drum program takes a bit longer to load than most of the other synths,,,,, I had forgotten that since I don't use it much these days..... but still nowhere close to the 3 minute mark.... maybe 15 or 20 seconds depending on the kit it was loading....  Most things (VST synths & samples) are loaded in 5 to 10 secs. 

I don't have a particularly large or fast DAW.  Intel i5 with 4G RAM and normal (2) internal drives. 
2013/03/06 11:26:43
twaddle
Guitarhacker


AD takes 3 minutes?  That's where I would spend time looking. If they have a forum, go there and ask this question and or contact their support. It sounds like it might be loading tons of samples and not just the one kit it might need. 

Come to think about it, I believe Jamstix ...also a drum program takes a bit longer to load than most of the other synths,,,,, I had forgotten that since I don't use it much these days..... but still nowhere close to the 3 minute mark.... maybe 15 or 20 seconds depending on the kit it was loading....  Most things (VST synths & samples) are loaded in 5 to 10 secs. 

I don't have a particularly large or fast DAW.  Intel i5 with 4G RAM and normal (2) internal drives. 

The thing is it's not happening with the same projects in Cubase which really throws a spanner in the works and makes most of the suggestions here a bit pointless as no one seems to have picked up on this ? 
Also that it's only after a cold boot, once he's opened and closed sonar, and then opened it again projects load normally, but, cubase doesn't do this.
This might suggest something in sonars setting needs to be changed but then why do projects load ok once it's been opened and closed. I'm stumped.

Steve

2013/03/06 11:50:41
Bristol_Jonesey
It almost sounds like the samples are being loaded from an external 'green' drive.

What drives are on your system and what's on each of them?

Something is slowing it down.
2013/03/06 11:58:23
Frostysnake
I was kinda wondering about what drives you were using as well...extrenals can definetly slow things up...I have one that takes about 3-4 minutes to load...
2013/03/06 12:03:57
Paul P
moebiuscat : "The thing is that it only takes a long time after the cold boot. Then if I close X2 and open it again - project takes 18 seconds to load.."

The second time there'll be a lot of disk pages still hanging around in memory so the system doesn't have to get them from disk.

Sounds like you're loading an awful lot of stuff.
2013/03/06 12:25:26
burkek
John


If you run Kontakt or other NI synths projects will load slower because they need to load their samples into memory. VSTis take a little time to fully load. VSTs shouldn't take much time.

There in no need to stop VST scan on startup now. CW did a lot to make it instant if there is no change. If you have added a VST it will only scan that one. 

VST scanning is quick IF one has not engaged the 'Rescan existing ...' or 'Rescan failed ..' settings in the VST control panel. If one of those is on, and in particular the former, scanning can take a long time depending on the number of VSTs and associated hardware that is used with those VSTs (ex: Maschine).
 
KEv
2013/03/06 12:49:39
John
What you are saying about automatic scanning on start of X2 is untrue. It does not scan all VSTs only those that have been added. If none have been added it wont scan. If you scan from the Plugin Manager it will scan all the VST folders and all VSTs. This is basically a rescan. 



 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account