Hi all!
 
First of all, some facts about my computer:
 
Windows 8.1, 32 gigs RAM, Intel Core i5-4430 GHz
 
Basically brand new machine, and pretty zippy!  I recently did most of what Sweetwater recommends to optimize Windows 8 for audio.
 
Just getting to know Sonar X3 studio- still confused by some things.  In general it has worked flawlessly.
 
Was recording with some friends the other day.  Recording a tune with a lot of takes, saving the takes.  The way I did this was to create a new track for every take I wanted to keep.  I would mute the take I wanted to keep, create a new track, and try another take.
 
I eventually started to hear some crackles and pops on the recordings.  I am pretty certain that this was due to stress on the processor due to accumulating takes, or possibly the buffer size on the VS-100 driver.
 
Questions:
 
1.  When I mute a track, is that still using the processor?  I'm betting that it is, that the track is still "playing" but that the audio output is muted.
2.  I seem to remember that earlier versions of Sonar had something called "hiding" a track.  Does X3 have that and if so should I use that?  Does that silence the track and put less stress on the processor?
3.  I'm guessing that I should be using the comping/take lanes feature.  I haven't really tried this so I don't really understand it.  Should I go this route?  Does it use the processor less?
4.  Here's what the current setting on the VS-100 driver is:  6, which gives 4 zeros for real time, and 6 for stability.  So, stable with a bit of latency.  Is there a better setting for that?
5.  Is my fundamental assumption about processor us wrong?  Could something else be doing this?
 
Sorry for the long post, and thanks for any help!

Len Rabinowitz
1.  When I mute a track, is that still using the processor?  I'm betting that it is, that the track is still "playing" but that the audio output is muted.

Still uses CPU.  Try the "A" Archive for unwanted tracks

Len Rabinowitz
2.  I seem to remember that earlier versions of Sonar had something called "hiding" a track.  Does X3 have that and if so should I use that?  Does that silence the track and put less stress on the processor?

You can still hide tracks, Right click on the track header and select 'Hide Track."  They still play and take CPU though.

Len Rabinowitz
3.  I'm guessing that I should be using the comping/take lanes feature.  I haven't really tried this so I don't really understand it.  Should I go this route?  Does it use the processor less?

If you are doing a lot detailed comping you might want to learn the new functionality. 

Len Rabinowitz
4.  Here's what the current setting on the VS-100 driver is:  6, which gives 4 zeros for real time, and 6 for stability.  So, stable with a bit of latency.  Is there a better setting for that?

Make sure you are monitoring on your VS-100 outputs while multi-track recording for lowest latency.  If you are just mixing then this isn't too important.

Len Rabinowitz
5.  Is my fundamental assumption about processor us wrong?  Could something else be doing this?

Unless you have more than twenty or so audio tracks I would be looking somewhere else for the clicking problem.  Don't use any audio FX while recording (Disable with the 'E' shortcut while tracking).
 
I'm not too comfortable with the Sweetwater recommendations when using Windows 8. 
 
Glen

Thanks for the detailed response!  A few follow ups:
 
1.  Once you have archived a track I assume it can be unarchived?
2.  If I use the comping feature, do you know whether that still uses the CPU if I have ten takes of something?
3.  I was using some plug in effects, and it did occur to me that uses the CPU.  I assume physical external effects would be OK?
4.  I am curious what your issue with the Sweetwater recommendations for Windows 8 is?  Do you have any other recommendations?  This is also my home computer, so I don't think I can totally streamline it.  When recording I do disconnect from internet and disable virus protection.
 
I appreciate your help.  Thanks!

Len Rabinowitz
1.  Once you have archived a track I assume it can be unarchived?

If you have saved the project you should be able to unarchive by clicking the 'A' button.

Len Rabinowitz
2.  If I use the comping feature, do you know whether that still uses the CPU if I have ten takes of something?

Yes, but I really don't think this is where your issue lies.

Len Rabinowitz
3.  I was using some plug in effects, and it did occur to me that uses the CPU.  I assume physical external effects would be OK?

External effects shouldn't cause any additional load on your computer.

Len Rabinowitz
4.  I am curious what your issue with the Sweetwater recommendations for Windows 8 is?  Do you have any other recommendations?  This is also my home computer, so I don't think I can totally streamline it.  When recording I do disconnect from internet and disable virus protection.

They tend to have evolved from XP recommendations without any consideration to what changes Microsoft has made to the OS. 
 
I run my Win 8 64 machine with Windows as shipped.  The only tweak that I have made is to power settings.  My biggest problems with clicks and pops have come from bit depth mismatches and from trying to run with active (unbounced) Audio Transients.  The real-time Audio Transient code does not play nicely on my computer.
 
Glen

Hay Glen...hmmm...Being new to Sonar x series, and having issues with clips and pops and cpu problems myself with one system, Buying new parts leading to RMA due to those problems indirectly myself.... you have now.....I would say, there are number of causes, routing out the variables to define or solve for X, could take time...So be patient.
 
TO start...The machine needs to be setup right...( I see you used the sweetwater tweaks , there are other tweaks sweetwater mentions that go to extremes from Black Viper's web site, and should be done with care and knowledge there of of how and why),
 
Redundant devices should be turned off to reduce IRQ sharing of your audio interface device, and when possible done in the Motherboard's Bios, so windows does not load the drivers for those things you do not need..(they can be turned on when needed before booting up)..You can view IRQ's listing of shared devices if any, By going to start/accessories/system tools/system information..and check up on the different tabs for info...underhardware you will find the irq listing...check it out...and see what if anything is sharing...that is a primary cause for clicks pops and cpu dropouts and spikes...I was told by Avid techs...
(to reduce variables in driver conflicts in windows turning off things in Bios is better than in control pannel),... and windows OS needs to be tweaked (which you seem to have done to some degree), ..and certain security software or apps need to be turned off, and any automatic updates also turned off, and if possible removed from the startup task in msconfig ....So you do not have to continually turn them off after booting up.
 
if it continues...windows services may need tweaking....(black viper?)....but this is something someone should do with care, and understanding of what is being turned off/disabled or left on / enabled, for their specific setup and software needs, and should not have to be done unless extremes are necessary....and why they should be either or addressed.
 
That is the nut shell of most issues that you can try to address yourself, with guidance if need be..to make sure your system is setup right for mulitrack recordings and playback..with ASIO 2 devices..
 
Sonar Bugs are something else to address, and can only be noted and or solved for by Cakewalk Bakers = when enough people have the same problems, and no solutions found to cure them....sometime workaround go forth...but this is not a solution that should be the cure ...and is usually system specific and or may not solve for X.
 
 After doing a driver update dance, and posting system spec rituals, and event viewer content, and such, or some other form of system spec posting method asked for, for the tech team here, and they are pretty good at helping when it gets seriously out of hand or understanding...as it may be getting to for you?...be patient..
 
So...make sure you have your system setup correctly...if you can....add your system specs and such to your profile to help people see what you have running, without  having to retype it over and over in each post past the first page , if it goes that far into detail, of the threads you may come to post in future....and Possibly be more specific with parts and Motherboard brand cpu memory and onboard devices, and any add on cards,HDD, exernal storage or other (on and or off, and where that has been done)...and take it from there on to continue to post...if it continues there after...if you need help on something ask and see what comes forth from........
 
The needed mead, and hair loss program, is part and parcel of the PC processing state before bliss...I say..So get that mead before hand, and less hair will come out in the end....LOL.
 
It could be just a buffer issue, that needs to be addressed and balanced, or speed stepping in bios was not addressed, or v-tech or something like that......but somehow I feel it is not so simple a solution as Buffers...wink...from my experience.

OK- so, while I may try out the comping feature, it sounds like what actually reduces CPU load is separate tracks that are archived once I am not using them anymore, and just deleting them once I make a final decision not to use them.
 
I figured external effects wouldn't add to the computer load, but best to check.  More stuff to haul around if I am not recording at home.  I think the VS-100 has an internal reverb.  Might be best to use that when recording if I just want an effect there as reference so to speak, although I think anything coming from the VS 100 would be recorded as audio?
 
I did make power setting changes.  As of now all tracks are playing cleanly.  I definitely learned a lot- Thanks!
 

The software is suppose to "multi track"...and "unlimitedly???" depending on the system being used, and parts there in, when setup right.
How may tracks?...is not suppose to cause clips, clicks, or pops, or cpu spiking, crashing, and or system failure...if you fall into the defined spec for the software and parts there of running it.
 
So do not settle for a work around...it is suppose to multi track...if it doesn't do this flawlessly...then something is not right....I say.
 
 
 
 

Sir Les - I'm not saying that system tweaks are not sometimes needed.  What I am saying is that blindly following a list of 'system performance improvement' is neither wise nor necessary.  The right answer always comes down to the specific hardware and software and the right answer is specific only for a particular setup.
 
My laptop took a ton of tweaks to get it to run Sonar well.  That was not the case with my desktop. 
 
Glen

This is not a flaw in the software.  I got it about a month ago.  I had upgraded from X1.  Its a fairly big jump and a fairly steep learning curve.  I did a few simple recordings by myself with essentially no problems. 
 
However this weekend was the first time recording a band and trying some new things.  Much more complex, more takes, and more demanding on the system.
 
Its quite clear to me that the only problems were errors I made.  I am quite sure that Sonar and Windows have successfully handled projects far more complex than this.  I'm not going to go blaming them for what I am pretty sure was my lack of knowledge.  Obviously "something is not right."  That's why I asked for help.  I assume the problem is with my knowledge, not the tools themselves.
 
As of now, all working fine.  Thanks!

Well my desktop listed in my specs had the same problems with dropouts, clicks and pops, cpu spikes, and crashes, since x1 into x2...tweaks got x2a working with issues after pulling every add on device and ****ing the system to exclusivity trying to find the culpret, and x3 screwed up a hole lot of projects I made in 2xa....Software can be buggy..Not saying this is the case..but not overlooking the variable either.....and in witness the bug list is accountable by those updates a b c d and the jumps to new numbers, being made frequently by Cakewalk...Some might call them improvements with added candy?..But the list is with them as noted bug fixes.
 
Just saying..even a desktop like mine..well over speced to their minimum requirements...had issues...Yes it could be something perhaps in hardware onboard is causing ,the problems I have had surely, and others, with Sonar......what that is has to be found out...and sort of like cases coming together to solve for X may help many others steer clear of x brand in future...or it is addressed by the bakers of the software for the future .
 
That is the only way it will be addressed for the most part in all, for cakewalk and consumers buying in?...well could be addressed for some who have these anomalies...laptop or desktop...I say...may not be completely similar culpret, ...but it seems some are having issues of liken , and I am sure the OP has played with his buffers and such...Like I have..with little to no success..
 
That leads us to devices, OS, and Bios...(as the remaining variables)..and if all that has been addressed and more done to stop background apps and redundant services from interfering with the cpu and or devices being used, including hard drives as conflicting drivers are hashed out, if any....then it has to point somewhere towards the software .....by process of elimination!
 
Solving for X can take time...or...one goes out and buys a new system more over the top than the last one, and see what happens..Like I am now doing....not all people can do this type of buying constantly to settle issues...like I can.
 
That was Part my solution for the below over specified system....cause it seems no matter how much tweaks I did, or updated the drivers were, and OS...Sonar x1,x2,x3 and protools 9.0, and acid pro 7, and others, weren't working right out of the box for me...on that system....As some claimed sonar would do with no tweaks.
 
Now I think the MLC micron controller on My motherboard has issues on that board and my ssds and USB 3 were also acting oddly...no way to update the firmware, and updating the SSD drives firmware caused a problem or issue with the onboard controller, that cannot be solved for....So updating can cause problems (it seems)...So one should be mindful of doing so...if all is working...one should reframe sometimes from updating.
 
Just saying it like I see it...as it was, is, has been, my experience with many daws recently and over the years....perhaps I am missing something in the tweaks or install processes?...nah....it's just my bad luck in picking system parts...that should work...but do not, with many DAWs!
 
So yes more mead consumption, and hair pulling will prevail over the issue, so stock up...Amen?...If you have solved the problems with 10 tracks or a few more...try doing 20 or more..and see if the problem occurs again...that would be a fine run at it...I've seen more tracks used in my passing experience ...Just saying it ain't over till you get to the next level of ...