Maybe I'll just have to scrap it and start a new project.

ZeroContrast
Maybe I'll just have to scrap it and start a new project.

If it's not too much trouble, it's certainly something to try.
 

ZeroContracst would it be possible to update your footer with your full specs (similar to mine)?
http://forum.cakewalk.com/editprofile.aspx
 
Please note all DAW's require configuration and optimization, don't expect anything else. The scenario you are describing sounds like a configuration issue or lack of horsepower.
 
Thankyou.

Did you go to Preferences ? Drivers | ASIO panel and look at the ASIO buffer?  If that slider is below 6, you will likely get drop-outs.  I usually set it higher for mixing so that the number is at 1024.  Then when I go back to recording, I set it lower so I don't have latency.

CakeAlexS
ZeroContracst would it be possible to update your footer with your full specs (similar to mine)?
http://forum.cakewalk.com/editprofile.aspx
 
Please note all DAW's require configuration and optimization, don't expect anything else. The scenario you are describing sounds like a configuration issue or lack of horsepower.
 
Thankyou.

I will probably update that info, but the issue isn't lack of horsepower. Of course more power would prevent the dropouts, but the dropouts are not really the issue in question. The issue is the fact that the project is using an increasingly higher amount of RAM that isn't justified by the complexity of it. Even if I had double the RAM it's possible the project could increase its resource usage until it causes a problem on even a higher end machine. If the cause is not determined and dealt with.


I did go and create another project from scratch using my template i mentioned. I put all the same audio clips in with the same few FX and I've even now recorded a few vocal takes and with this new project Sonar hovers just around 130MB RAM total, which is back to normal.
 
The only thing I can think that could have made a difference with the first project is the way I made some changes. My original percussion clips I added were sequenced in FL Studio and I was exporting them as small .wav's. When I wanted to change one, the hihat pattern for example, I just closed Sonar, opened FL, tweaked the hats, exported the pattern again just overwriting the old .wav clip. Then when I opened Sonar again and it loaded the clips the hihat clip would be the new one, Sonar didn't seem to know any difference since the clips are the same length. I've considered that maybe Sonar still had peak info for the previous version since I didn't delete the audio file completely and re-add the new one as a new track. Does anyone know if that could be the case? Maybe there is some project cache that can be emptied and reduce the amount of RAM the project uses.

konradh
Did you go to Preferences ? Drivers | ASIO panel and look at the ASIO buffer?  If that slider is below 6, you will likely get drop-outs.  I usually set it higher for mixing so that the number is at 1024.  Then when I go back to recording, I set it lower so I don't have latency.

I think that is a good call. We do not know anything about the OP's audio interface or drivers. The memory issue could be a red herring. Because I use a lot of soft synths my memory usage is often up in the gigabytes and causes no problems.
 
XP's memory managment is poor compaired to modern operating systems and X2 is only supported on Windows 7 and 8 so some of the memory weirdness may be because of that.

And it's not a Picture Cache issue, just found out about that, thinking it might be the problem, but no, redrawing pictures didn't change RAM usage. (Also deleting the files from the picture cache folder and having Sonar have to recreate them didn't do anything either).
 
And the ASIO buffer is not the issue, I keep it relatively high already.

Okay, so I finally discovered what the problem was. It was due mainly to my lack of knowledge about the complexities of Sonar. I opened the new and old projects in Notepad to see what was the difference that might be making the old one use so much RAM. I saw details about Superior Drummer in the old one, and I remember adding it to do the extra percussion, having issues, and so deleting it to just use it in FL studio. I had deleted the instrument track, but had no idea that the Synth Rack existed let alone what it was for. So while I didn't see Superior Drummer at all, on tracks or console view, it was loading up in the Synth Rack. Deleted it and immediately dropped RAM usage to normal.
 
I'm sure most of you probably know about the Synth Rack, what is the point of it? If I have an instrument there can I then have multiple tracks using it without having multiple instances of the instrument?

From http://www.cakewalk.com/D...Req=SoftSynths.02.html
 
The Synth Rack lets you view, insert, delete, and configure your soft synths. You can also mute, solo, and freeze any or all of them from this view. Each time you insert a soft synth into your project, a new row appears in the Synth Rack with the name of the soft synth and its current preset.
 
 

ZeroContrast
If I have an instrument there can I then have multiple tracks using it without having multiple instances of the instrument?

That would depend on the synth.


 

ZeroContrast
Deleted it and immediately dropped RAM usage to normal.
 

Good news.  If you could add [Solved] to the beginning of this thread's title (just edit the title in your first post) we'll all know that it isn't a general problem with Sonar.
 
I'll let those more knowledgeable answer your synth rack question.