Lexington using more CPU? No problems (now crackling) Perf Module CPU is very active...

I have noticed this too. I'm not that happy about it. 

What OS are you guys running?  I have seen a few instances of Win 10 just using a lot of CPU all by itself.  Often the runtime broker using 20% to 60% of available CPU time.  This particular issue seems to happen more often on Windows 10 machines that were upgraded from Windows 7 or 8.x.
 
Seeing much in task manager?

Which version of sonar are you comparing to? Please submit a project if you can repro a loss of cpu perf

Right but what are you comparing Lexington to when you say that its using more CPU?

Hi, Noel. I'll provide some more detail when I can get my brain together. I'm in the middle of something (music related) and not feelin' so hot today so want to make sure I can give proper details.
 
Nothing is screwing up. I just found the activity meter goind way more nuts than I'm used to for such a (relatively) simple project.
 
I'll be back.
 
Cheers.

When you don't have Sonar running, are you seeing any extraneous CPU activity in task manager?  Just trying to rule out the high-CPU issue I have seen on a number of Win 10 PCs (IT is my day job).
 
Bill.

I m still in ipswitch and i ain t moving ....if you guyz wants me to check but the thing is that to do it well we have to have the pretty same specs
Win 8 here i7 4790s

Personnaly i m noticing more dropout for no reason ( dpc latency exellent, 20 % cpu usage ) than previous versions , than x1 for sure with dropouts once a year !

Uhhh... so now I'm getting crackles while recording which I have not experienced since X1 and I replaced my old interface.
 
This is indeed disappointing and I do not have the time to sort it out with support just yet.
 
So is Sonar still being tested with Win7? Has that ship sailed?
 
I really hope I don't lose good takes due to crackles on this project. I have NEVER had to worry about this problem for YEARS. The worst that would happen is I would get an engine stop and even that never happened while tracking (only editing/mixing with playback running).
 
Ugh... guess I'm gonna have to adjust my workflow/buffers/etc to get through this project. Bad timing. I should not have updated yet.

@PaulP...
 
Because previously I was on Foxboro (I had not installed or downloaded any updates in the meantime) and I am an offline installer so the rollback process isn't quite as elegant (and I've never done it).
 
Also I'm balls deep in a session so I can't be futzing with this right now. I should not have updated in the middle of a session but wanted to get access to the Aux Track stuff and (and performance enhancements). Lex seemed to be working well for everyone so thought it would be safe.
 
For now I'm going to have to keep working as is until the next batch of tracks is done then maybe I'll have to use the restore point I created before installing Lex.
 
I just can't be troubleshooting right now.
 
Cheers.

Try running Latencymon in the background, while you are working in Sonar.  It should give you an idea of what driver is using up the resources.  Usually on my system, it is the network driver.  
 
http://www.resplendence.com/latencymon
 
I don't get crackles on my system, until my performance meter (CPU) hits the red.  This only happens when I'm using some rogue 32 bit plugin or instrument on my 64bit system.   What I can't figure out is why only my first CPU core hits the red.  The other 7 cores are under 30%.

Beeps - offline rollback takes less than two minutes. Just run the installer for whichever version you want to use. I have done it a dozen times without issue. The situation you are in is exactly what it is for. 

I have also noticed a bit of performance change in Lexington. The CPU meters jump more than usual and I have had the occasional click or pop that I have not had to deal with in JP.
 
I usually run with buffers set to 128 but needed to increase to 256.
 
The usual culprit that causes the clicking for me is having the gui for Jamstix open. If it is closed then playback at 128 buffer is glitch free with JP and earlier. With Lexington even with the gui closed I am hearing glitches during playback.    
 
Specs in Sig.

I found the same type of issues with Lexington, basically it seems to use noticeably more CPU/resources, than any past iteration of Sonar that I have experienced. After not using Sonar for some time I updated to Lexington to check it out and noticed issues straight away, started a thread Here marked it as solved, but as I continued with the little project adding more stuff the crackles and pops started returning, it was still only a small project, I had to change my buffer settings dramatically to stop it from occurring, never had to do that before. I can run the same project in Studio One 3 and Reaper without issues and with buffers at 128.
 
I moved the project entirely over to Studio One, it has now grown considerably larger and there is no sign of any issues and no need to alter buffer settings. I have always found Sonar to be seemingly heavier on recourses than needs be compared to other DAW's I use, part of the reasoning to check out Lexington was the optimizations, speed increases etc I had read about, but from what I can see things have gone backwards.
 
Further reinforces that my move to Studio One 3 some months back was a good choice for reasons more than just features. But I keep checking in with Sonar (purchased another 12 months subscription), and I read somewhere that Cakewalk were taking the knife to Sonar and cutting out old inefficient stuff, that can only be good, because I think there is a lot of old inefficient stuff in there going back to the last decade if not century. Clean it out, get rid of all the old inefficient stuff, bring it up to todays standards, I don't care what anyone says about benchmarks against other versions of Sonar or other DAW's, the only benchmark I care about is my personal one, and it says Sonar is behind the 8 ball, and that Lexington has stepped backwards. Lets see what the future brings.