Hi, I know there is another thread talking about bad cpu perfomance on Jamaica update, but in my case it has nothing to do with the number of outputs used or "dynamic arming" during playback.
 
Normally I start from a template that has a lot of tracks with guitar rig (like 12-14 tracks).
Before Jamaica update, my cpus where low...until I started to record guitars and using all the tracks, and the cpu was going higher ecually. If I used all tracks...cpus will go high ecually.
 
Now when there is nothing recorded in any track and without pressing "play", all my cpus are very high, balanced but very high...like if there was audio recorded. Actually it seems sonar doesnt care if there is audio or not..its like guitar rig is procesing "nothing" but consuming full cpu. The only way to make cpu lower, is to bypass manually all the guitar rig plugins on the tracks not used.. But before update, I didnt need to do this, the cpu was low...until I startet to record more and more guitars.
 
I remember having to uncheck the option "Always stream audio through FX", so when the track has no audio..it should not hit the cpu perfomance.
 
I checked and unckeked that option with same results, its like that option is broken?
 
I also unchecked "allow arm changes during playback" without any diference.
 
Any sugestions??
 
Its a shame that now I need to bypass a lot of plugins when not used, I like to have the guitar rig presets in different tracks, and on some songs I use some tracks and on another songs I use another tracks, but all them were always "on".
 
Thanks

There is definitely something funky going on with the multithreading model in Platinum & I have FOUND A SOLUTION !
 
I have been tearing my hair out with dropouts, glitches and a variety of performance issues for a while.
My machine is pretty powerful; HP Z420 workstation, 24 gigs RAM, 6 core Xeon E5-1650 CPU @ 3.2 GHz etc.
dedicated to Audio
I have seen the same problems on multiple different HW; Pro Tools HD Native PCIe card, Presonus Firebox, M-Audio Fast track 400.
Often the glitching will not stop audio playback & will not consistently occur.
My projects are not large - maybe 5-10 instruments, 10 audio tracks & few MIDI tracks
 
I have tried sooo many of the suggestions to help with performance improvement (Many thanks to Doc Avalanche for all suggestions)

• Driver updates
• NVidia graphics manual driver installs
• Rescan of VST plugs
• delete AUD.INI file
• manual tweaking of Dropout threshold, Processor scheduling
• disable Antivirus, onboard sound, networking etc.
• disable allow arm changes during record

 
none of these made any significant difference
 
I analyzed my system with Theysemon DCP checker &  latencymon; there was nothing substantial in the reports that would indicate any specific issue with a driver or device.
 
I ran a huge instrument session in Pro Tools 12 HD and it didn't miss a beat, and got a demo of Cubase & found the same thing - I could run very large instrument projects without the glitching I saw in Sonar.
 
I made a change to the MixThreadCount (Configuration settings)  and BOOOOOM ! problems solved & performance dramatically improved
Check this video out to see what I mean - you can see from the video everytime there was a glitch, my mouse would pause & the counters would pause.
 
http://screencast-o-matic.com/watch/co6UQzhjz8
 
Chuck
 

What did you change MixThreadCount to?

SynapticI made a change to the MixThreadCount (Configuration settings)  and BOOOOOM ! problems solved & performance dramatically improved
Check this video out to see what I mean

Excellent sleuthing. Thanks for sharing this!

Hi, thanks for your sugestion....but the thing is, that this only happens to me with the new Jamaica update!
 
Before the update, my cpu perfomance was totally correct. Its just that now the plugins that are not used, they still eat cpu.
 
Daniel
 
 

Synaptic
 
I made a change to the MixThreadCount (Configuration settings)  and BOOOOOM ! problems solved & performance dramatically improved
Check this video out to see what I mean - you can see from the video everytime there was a glitch, my mouse would pause & the counters would pause.
 
http://screencast-o-matic.com/watch/co6UQzhjz8
 
Chuck
 

 
Watched the video - I'm by no means a hardware/computer expert but it appears odd to me that performance improves when you limit processor usage to fewer threads. Should work the other way round - unless maybe half of them are virtual/hyper or whatever non-physical... or some other process is eating up some of those processing resources ...
 
Here's more info in an older thread: http://forum.cakewalk.com/FindPost/34860
 
I wish there would be official Cakewalk documentation on these settings so we do not have to use trial & error so frequently ...

Spurious ending / in your older thread link.

I wasn't on the forum in '04, so I'm not sure who "Master Chief" at Cakewalk was but he wrote the following in http://forum.cakewalk.com/FindPost/34962 :
 
"When MixThreadCount is set to zero, SONAR will allocate one thread per CPU. By setting it to 1, you are overriding this behavior and forcing SONAR to use a single thread even though you have multiple CPUs. 
Your glitches and dropouts due to enabling MP may be caused by your driver or some plugin not being fully MP capable. Some plugins seem to keep "global" data that is assumed by the plugin code to be accessed by one thread at a time. This isn't true when SONAR 3.1 MP is enabled."
 
I presume this still applies to Platinum, and the default should be zero.
 
EDIT: Just watched the video, and see that it was zero to start; I initially thought Roberts's description was indicating that it had been lowered from some non-zero value.
 
 

Master Chef was - I believe - previous CTO Ron Kuper.

Thanks, Kevin. That name rings a bell. "Chef" would have been apropos, but I double-checked, and it was definitely "Chief". 
 
In any case, I'm curious to know how many others have issues when the default 0 is set for MixThreadCount in Jamaica Plain or any other release. This is the first time I've seen this setting mentioned in all my years around here.