mettelus
 
DOH! I wish I had known this 6 months ago trying to find the "errant AS" in a project.

Same here!!

Noel Borthwick [Cakewalk]

icontakt
I have several 4 minute-long audio clips that were bounced after being slip-stretched with Audio Snap enabled. I'm not sure if these clips are contributing to the long saving time. As for instruments, my projects don't use huge libraries. All of my projects created from my custom project template that contains many empty tracks and some instruments/effects doesn't take a long time to load (except for the initial launch after a PC restart), but the saving time seems to increase more and more as I record and comp (and probably slip-stretch and bounce) more audio clips.
 

 
Bounce has nothing to do with save times. I suspect you have some audio snapped clips somewhere that you have forgotten about. In platinum you can easily strip out all audio snap markers from a project if you aren't using them.
To do this press CTRL-A to select all clips and then right click on the power button in the audio snap palette. Select "Clear all audiosnap markers" to reset all markers and then save your project. 

 
I just noticed that I still do have some time-stretched-but-not-bounced-with-radius-algorithms-yet audio clips in the project I'm currently working on (I hit Ctrl+Alt+A to locate them). I'll delete these clips (since I no longer need them) and see if the saving time will be reduced.
 
Btw, "PauseDuringSave" reduced the saving time from 60 seconds to 55 seconds.  

Just tried the following with all tracks visible in the TV/CV:
 
 
Deleted all slip-stretched auido clips, then saved the project under a new name.
--> Project folder size decreased from 1.90GB to 1.73GB. Saving time decreased from 55 sec. to 52 sec.
 
Deleted all soft synths (AD2 & two instances of Kontakt 4) without deleting the associated tracks, then saved the project under a new name.
--> Project folder size remained the same (1.73GB - but strangely increased to 1.74GB just after I did the following step). Saving time increased from 52 sec. to 65 sec.
 
Deleted all effects (too many to list), then saved the project under a new name.
--> Project folder size remained the same (1.73GB). Saving time increased from 65 sec. to 70 sec.
 
Deleted all track automations, then saved the project under a new name.
--> Project folder size decreased to 1.72GB. Saving time decreased 70 sec. to 65 sec.
 
Deleted all MIDI clips, then saved the project under a new name.
--> Project folder size remained the same (1.72GB). Saving time decreased from 65 sec. to 52 sec.
 
Unlocked all audio clips and cleared all audiosnap markers (just in case I still have them), then saved the project under a new name.
--> Project folder size remained the same (1.72GB). Saving time remained the same (52 sec.)
 
Deleted all auido clips, then saved the project under a new name.
--> Project folder size decreased from 1.72GB to 1.36MB (Audio folder is 0 byte, of course). Saving time decreased from 52 sec. to 12 sec.
 

From these results, I can say it's the size of audio (perhaps the number of audio clips in Take lanes - which have LOTS of split points) is the culprit of long saving time.

Just did a simple test using the Normal project template.
 
1. Crate a new project.
2. Drag five 4-5 minute-long Wave files from the Browser into the Track view (this creates 5 audio tracks).
3 Save the project. The saving only takes a few seconds.
4. For each track, expand the Take lane and split the clip into LOTS of clips, by simply dragging the lower half of the clip with the Smart Tool, just as you would normally do when comping audio.
5. Save the project again. It takes 5-13 seconds on my system.
 
This is bad news for me who want to keep all the pre-Flatten Comp clips in the project until the mixing stage.
 

The joy in Autosave is when the .cwp get corrupted and the "Copy of......".cwp is valid.
 
This has saved me hours of reconstructing of at least once project per release since I implemented it back in X1.
 
Yes, it would have been better to discover what the source of the corruption but since it's only been about four or five projects I'd rather just carry on by opening the autosave project and overwriting the corrupted project with a Save As.

That is interesting to see data on. I assume the deletion of the audio did the takes as well (in one go). I wonder if flattening comp would help any, since those results indicate that the number of clip pointers during save is a big deal.

My saves, exports and pretty much everything takes longer when I have a mountain of takes and the grows massively with intricate comps in play. I can really say whether Flattening helps at all but I haven't noticed any significant improvement after doing so for most stuff (might be quicker for saves and exports).
 
The #1 thing that improves the speed of EVERYTHING in my project is copying my final, flattened take to a cloned track and archiving the take laden original version.
 
If I do this across the entire project I go from a project that...
 
Takes a second or more to begin playback to a project that starts playback immediately
 
Makes what I THINK is what is referred to as "zipper noise" when jumping the Now Time to another location during playback into one where no noise occurs when doing so
 
Exoprts slowly (sometimes more slowly than real time bounce when Fast Bounce is selected) to one that exports quickly
 
Saves slowly to one that saves quickly
 
Is glitchy to one that is less glitchy
 
etc...
 
This is why I posted a Feature Request recently for us to be able to bulk archive Take Lanes. So you'd Flatten your final or multiple finals and archive all the other take lanes to remove them from processing. This avoids having to do my little "Clone/Archive dance every time I finish a track". Go vote for it.
 
I did however forget to include in that FR something I've been asking for since X2 which is a "Hide Take Lane" feature so I don't have to look at those piles of takes when I've got my finals but don't lose them or have to clone, archive and hide them the old fashion way.
 
Meh. Would make things much easier for me and I seriously think this is the type of stuff that might improve stability for take maniacs like myself... thus less complaints on the forum.
 
Just push it as part of the standard/recommended workflow and I'd bet people would be a lot happier with Sonar. Seriously the improvement is like night and day when I do this stuff... but it's a time consuming PITA especially on large projects.
 
Cheers.

I just saved the current heavy project under a new name, then tried the following:

1. Unarchived all tracks and hit Ctrl+S
--> Took 54 seconds to save.
 
2. Archived all tracks and hit Ctrl+S
--> No change. Took 54 seconds to save.
 
3. Unarchived all tracks, deleted all takes in Take lanes except for final, flattened takes, saved the project under a new name, then hit Ctrl+S
--> Took only 19 seconds to save. (The size of Audio folder in the project folder decreased from 1.89GB to 1.19GB)
 

So, at least from these results, archiving tracks doesn't help at all, and the number of split points (with auto crossfades) in takes highly contributes to increasing the saving time.
 
This is a final blow to me. I have a few workflow-affecting audio recording issues which happen in almost all my Sonar projects but not reproducible in a new, blank project. And Take lanes are inefficiently designed IMO and have some serious confirmed bugs and probably won't have major improvement for at least one year judging from the content of the recent Sonar survey questionnaire and the very small number of heavy Take lane users on this forum. My plan to do all future recording and comping in another DAW and import the flattened takes into Sonar is now DEFINITE.