• SONAR
  • Saving too often (p.2)
2016/04/27 19:11:27
Chameleon Music
Larry,
Sorry the file defrag didn't help.
 
Other thoughts from past experience:
 
1) Particular VSTs can cause issues - try removing them one by one and see if there is a compatibility issue?
2) Are you using any 32 bit plugins via bridging software? Always dodgy at the best of times!
3) Melodyne has been known to cause hangs in Sonar on some systems.
4) Check the default sample rate against your projects SR - sometimes a mismatch can cause issues.
5) I think the Picture Cache has already been mentioned - temporary files in there can seriously mount up!
 
Can't think of anything else off hand.
 
Mark (Chameleon Music)
 
 
2016/04/27 20:02:40
Anderton
Larry Wilson
I just transferred the bundle to my nearly new laptop and the file works perfectly.  So the problem is clearly in my desktop and the ASIO driver.

 
I can think of two possibilities offhand.
 
  • You hard drive is about to fail.
  • A RAM stick is failing or has failed (check for memory problems).
  • You've filled up your RAM, so the computer is having to do constant disk swaps with your RAM and hard drive. 
 
I guess as a final fallback I can uninstall and reinstall X1.



I highly doubt that will solve the problem, it has the vibe of a computer issue.
2016/04/27 20:04:09
skitch_84
I've been having very long save times as well (not two minutes like the OP, but way longer than usual). I'm running Sonar Platinum. Just one of many performance issues I've been experiencing lately. 

I was tired of my performance getting worse and worse, so I decided to just bite the bullet and build a brand new PC from the ground up. It'll be all put together by Friday night. I'll spend all day Saturday installing all of my software and virtual instruments, etc. If I'm still having performance issues, I'll know it's Sonar's fault and not mine. Haha! 
2016/04/28 10:25:32
Larry Wilson
Thanks guys.  I think its a general computer problem.  Will try to fix.
2016/04/28 11:04:37
eltonechris
Larry,
 
Try one more thing which solved same problem for me. Archive all the tracks and then try a save. If that improves it, then un-archive a few tracks at a time until you find the track causing the problem. 
It might be audio, midi, a software synth, plugin or effect on that track and you might have to just re-build that track only.
 
Just a thought ?
 
Chris.
2016/04/28 11:25:00
pwalpwal
Larry Wilsonbundle

can you clarify whether you're using CWB (bundle) format to save?
2016/04/29 02:58:07
phlosten
Something I have noticed with newer Windows 7 systems that have a reasonable amount of RAM. In a lot of cases the default windows page file setting of automatic will result in your system trying to create a massive swap file that is just unnecessary. If you have a reasonable amount of RAM reducing and fixing the swap file size can make for a more zippy experience. On my 16GB RAM computers I usually fix it at 4GB.
 
Looking at my system now it recommends a page file of 24GB! which is just ridiculous. If you have an SSD that might be OK, but on spinning rust that is a significant bottle neck.
 
I have also noticed that the automatic setting will result in some really poor performance once the primary OS partition starts to get filled with lots of data. ie once you are down around 25% free space.
 
Might be something to play with and see if it makes any difference.
2016/04/29 08:21:48
mettelus
A few quick items for the OP:
  1. Are you running X1d?
  2. If you have saved as a bundle, that will remove audio transient information which can lead to long save times (but seems you have already saved as a bundle). It will also consolidate data on the disk when unpacked as long as the disk is defragmented.
  3. Picture cache has been mentioned, but unsure if it has been cleared (I might have missed this one).
  4. In Preferences->Audio->Sync and Caching (need the "Advanced" button on the bottom to view this), there is a "File System" section. Bumping up both the Playback and Record I/O Buffer Size (KB) to 512 may also help.
  5. Lastly, is your default save as a cwp (project) or cwb (bundle)? Saving as a bundle (frequently) is not recommended unless transferring data to another SONAR machine. Saving as a cwp (project) is a simple file that should be quick (sans transient information).
Barring the above, if the issue is still prevalent, system diagnostics would be in order as mentioned above. Your situation is not common.
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account