Wibbles
This happens with me.
 
I'd put it down to VST Scan not Sonar.

I have VST Scan OFF.
 
I should say this happens first out when Sonar just loaded. Interestingly when one opens a new file .. adding new VSTs might take about 20 secs to load for each.

Close the file and open a new file and start adding new VSTs there .. they load up good and fast

Im not sure what that has to do with caching? Just loading VSTs, no data on the track.
 

tlw
Put simply, Windows (like most modern operating systems) keeps stuff loaded into the RAM cache even after the application using it is closed. The cache is only cleared when the space is needed for something else. That way if you open the file soon after closing it the data is still there so you get fast access to it.

Memory management's quite a bit more complex than that, but that's basically what happens.

Yeah, as an experiment, the OP could try opening, say an Excel Spreadsheet after closing SONAR, make a few edits, save, close & re-open SONAR.
 
I'll be it's back to how it was in terms of opening speed.

Hey Bristol,
 
Your theory did not work :D
 
I opened SONAR, loaded a new file, added two VSTs .. took about 15 secs each to load.
 
Closed Sonar .. opened again. Loaded same 2 VSTs. They loaded straight away.
 
Closed Sonar .. Opened BLENDER 3D app. Did some 3D work on a cube for about 2 minutes. Closed Blender. Opened Sonar. Opened new file. Same 2 VSTs loaded lightening fast ..
 
BTW - I tried the above on my lesser spec'ed Desktop PC ( Core i3, 8GB Ram, Nvidia, M-Audio Profire ext audio box Firewire )
 
 
 
 

aidanodr
Using COMODO AV with all audio folders excluded ..

 
You may try to exclude *.cwp file type.
 
Good luck

aidanodr
Hey Bristol,
 
Your theory did not work :D
 
I opened SONAR, loaded a new file, added two VSTs .. took about 15 secs each to load.
 
Closed Sonar .. opened again. Loaded same 2 VSTs. They loaded straight away.
 
Closed Sonar .. Opened BLENDER 3D app. Did some 3D work on a cube for about 2 minutes. Closed Blender. Opened Sonar. Opened new file. Same 2 VSTs loaded lightening fast ..
 
BTW - I tried the above on my lesser spec'ed Desktop PC ( Core i3, 8GB Ram, Nvidia, M-Audio Profire ext audio box Firewire )
 
 
 
 

Good on you for at least trying it and following up.
 

You can use the Sysinternals tool RAMMap to see which files are still cached even after you close the program.
 
https://technet.microsoft.com/en-us/sysinternals/ff700229.aspx
 
You can also use it to empty the cache (choose "Empty Standby List" from the Empty menu).  I suspect that after doing that it will revert to post boot speeds.
 
Just running a few apps is unlikely to clear much of the cache unless you have very limited RAM or very RAM intensive apps.
 
AMB
 

AntManB
You can use the Sysinternals tool RAMMap to see which files are still cached even after you close the program.
 
https://technet.microsoft.com/en-us/sysinternals/ff700229.aspx
 
You can also use it to empty the cache (choose "Empty Standby List" from the Empty menu).  I suspect that after doing that it will revert to post boot speeds.
 
Just running a few apps is unlikely to clear much of the cache unless you have very limited RAM or very RAM intensive apps.
 
AMB

Thanks Antman,
 
Tried that - "Empty Standby List" from the Empty menu - YES .. it definitely reverted to slower load.
 
Another thing I tried was open sonar, load new file, load a VST. Closed file. Opened new file agin, loaded vst, as suspected faster.
 
Now closed the file - ran "Empty Standby List" from the Empty menu - And VST reverted to slower load