Nice typo on my behalf then :-)

KPerry
What did you change MixThreadCount to?

Hey KPerry,
 
I have a 6 core machine (6 Physical & 6 logical)
I limited Sonar to 4 of those cores & my glitching all but dissappeared
 
Chuck

Danirustic
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
 

Hey Daniel,
 
Jamaica plain is definitely worse though I was have issues before that but not as bad. It was a bit of a crap shoot - sometimes things would be fine, other times I couldn't get through a session without glitching and dropouts.
 
Chuck

brundlefly
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.
 

 
I will dig into this with tech support - My concern is that if it is a plug in or something else, we need a way to diagnose without the crazy hoops we have been jumping through recently. There have been so many red herrings It has done my head in & almost made me give up. Especially when people are calling out amazing performance & I am seeing a goose egg, especially with a modern workstation - I didn't skimp on CPU or RAM etc.
 
I know in other programs they can put it into a logging mode that identifies the offending plug in & logs it so that the developer can be notified.
Not sure if we can do this in Sonar
 
Chuck

Chuck, based on what on what Brundlefly said, have you tried 6???
Would that have the same results or revert back as when you had zero??

arlen2133
Chuck, based on what on what Brundlefly said, have you tried 6???
Would that have the same results or revert back as when you had zero??

Yes - I tried 6 and it was the same as 0 - CPU Spikes & drops out.
 
so far, 4 seems to be the sweet spot for my CPU
 
Chatting with tech support to get more info & try to resolve this
 
Chuck

There are confirmed issues that effect CPU with JP (first core overloads). It also crashes for me. I just rolled back and if I were you I would do the same, and try the next release. I cannot recommend it in it's current state myself.

Since JP there has certainly been a large increase in performance or drop out related threads and posts, predictable really as this is a big change for Sonar this month...

Thanks for responding Chuck.  Good info.

Hi,
 
Well, what I am doing now is bypasing all fx bins from the tracks that are not used and empty.
 
When I start a new project, I have big templates with a lot of guitar rig plugins etc, before Jamaica, cpu was low until I started to record on tracks,  now is like all the guitar rigs plugins on empty tracks...are eating cpu until I bypass them.
 
Doing that I have a normal CPU usage as before. Thats why I thought it has something to do with the option "Always stream audio through FX". With that option unchecked, it is supossed that if there is no audio on the track, the plugin should not eat cpu.
 
Daniel