I haven't actually timed it, but sometimes a project can take a very long time to load. Never had this with SPLAT. Anyone else? I appreciate the little prompt on the right showing the progress - no complaints, but it's just scary slow sometimes.
 
I just saw this in the latest update 

Project load optimizations, including faster load times of large multitrack projects and projects that contain many AudioSnap transient markers
Maybe it will be quicker

If project specific, look for things like any VSTis that load samples to memory, AS (transients) enabled on tracks, or unbounced Melodyne tracks.

The size of the cwp file itself will help indicate AS/Melodyne being active... Those cwps can get up in the MB range easily.

Im not sure I could have said it any better than Mettelus. Those 3 things are usually the culprit on slow load times.
It could also be the audio interface and/or a driver conflict.
 
If you are serious about finding the source of your slow load times you will start timing project from click to open.
 
1- Try loading a blank project - check time
2- Try loading a blank project with some plug ins used in full projects - check time
3 - Narrow down the offender

mettelus
If project specific, look for things like any VSTis that load samples to memory, AS (transients) enabled on tracks, or unbounced Melodyne tracks.

The size of the cwp file itself will help indicate AS/Melodyne being active... Those cwps can get up in the MB range easily.

Thank you both.


I am loading Omnisphere and other large libraries. Some have Melodyne tracks and yes maybe some unbounced. It is definitely faster when nothing in it. But I have been doing large projects and even film scores with everything I have and Waves plugs all over the busses and individual tracks and it was never like this in Sonar, but could be not any fault on Cakelab but maybe my system has changed. My desktop is 5 years old - the longest I probably ever had one. Maybe I should re-install windows over the Holiday's - or maybe not. It especially happens if I haven't opened the particular tracks in maybe 6 months. It just got actually stuck on "creating ui" and had to close. The main difference in my system now is the use of Komplete Kontrol and Native Instruments. Please explain "VSTis that load samples to memory".
 
Much appreciated.

This happened to me just yesterday.  The second time I loaded CbB it took almost a minute just to load the program.  What it turned out to be was a system check program that Lenovo had preinstalled on the PC.  Perhaps that's what you're dealing with.  Check your system for any pre loaded apps and what time of the day they are set to scan your system.  Then you might be able to disable them or reschedule them for a more convenient time for you.
Hope this helps.  Good luck.
 
JB

michael japan
Please explain "VSTis that load samples to memory".
 

VSTis will get samples from one of two methods, they will either stream from disk after the VSTi is loaded and running, or grab them all when the VSTi is first loaded. *IF* you have VSTis that load the entire sample library when they are initiated, you could be getting into a situation where it is filling up your RAM, and your hard disk is being used as virtual RAM. The best way to monitor this is to look at your system RAM usage when loading CbB... Windows will not let physical RAM fill, and begin using the disk as RAM. Another way to check this would be to first save the project with a new name (so the original is your backup), then freeze a few of the heavier VSTi synths you have going on in your project. Save that new project again, then close and reopen CbB and see if it is faster.

mettelus

michael japan
Please explain "VSTis that load samples to memory".
 

VSTis will get samples from one of two methods, they will either stream from disk after the VSTi is loaded and running, or grab them all when the VSTi is first loaded. *IF* you have VSTis that load the entire sample library when they are initiated, you could be getting into a situation where it is filling up your RAM, and your hard disk is being used as virtual RAM. The best way to monitor this is to look at your system RAM usage when loading CbB... Windows will not let physical RAM fill, and begin using the disk as RAM. Another way to check this would be to first save the project with a new name (so the original is your backup), then freeze a few of the heavier VSTi synths you have going on in your project. Save that new project again, then close and reopen CbB and see if it is faster.

yes, it's weird. I just hung trying to load Ivory (already had Komplete Kontrol Wurlitzer (Scarbee) and Ivory acrashed it. That never used to happen.

Johnbee58
This happened to me just yesterday.  The second time I loaded CbB it took almost a minute just to load the program.  What it turned out to be was a system check program that Lenovo had preinstalled on the PC.  Perhaps that's what you're dealing with.  Check your system for any pre loaded apps and what time of the day they are set to scan your system.  Then you might be able to disable them or reschedule them for a more convenient time for you.
Hope this helps.  Good luck.
 
JB

how does one check for "pre-loaded apps".