Hello,
 
Updated to Jamaica Plain and can't continue to work on my current project because of heavy performance problems.
 
No such problems before on Ipswich with the same project.
 
As soon I start playback, the first cpu core goes up to 100% and I only hear stuttering. Deactivating all fx and virtual instruments does not help. Removing all tracks and clips does not help.
As I removed the virtual instruments, there are about 35 and most of them Kontakt5, it becomes better. But this is not a solution.
 
Ok.
My cpu is a quad core, and in stop state all 4 cores are on about 25%.

As I start playback the first cpu core goes up to 100% and the other three down to 5%.

It seems it only uses 1 core in playback. Maybe there are something wrong with multicore-engine in Jamaica plan.
 
I tried some of my other bigger projects that all worked in previous versions of Sonar, and they all have the same problem.
 
I've started with an empty project, put in 30 empty Kontakt5 instances without loading any sampels to it and the problem still there. No audio data, no midi data, no fx, only 30 empty Kontakt instances and cpu core #1 goes up to critical load as I start playback.
 
I've tried to delete my aud.ini, but still the same problem.
 
I will call this as a Bug!
 
I'm not able to work on my current project with this Sonar Jamaica update and have done a rollback to Ipswich, that works normal and without such problems.
 
-Markus
 
 
 
 
 

Out of curiosity, did you rescan your plugins?

See if dynamic track arming is checked in Preferences. 
 
Look for this in your AUD.ini
 
ThreadSchedulingModel=
 
This variable goes in the [Wave] section and controls the interaction of the main audio thread and worker threads on multiprocessor systems when the Use Multiprocessing Engine option is enabled. Depending on the system, a particular model may result in less glitching and better overall performance. The values are as follows:
0 = Same as previous versions of SONAR.
1 = (default) Better thread balance. Model is more efficient and can provide cycles for other tasks.
2 = Additional worker thread is created. This may result in improvement with Quad processor systems or higher. Not recommended for Dual processor systems.

Not seeing this sorry. Have you installed everything inside CCC including the new plugin updates?
 
Try...
 
Upgrade everything in NI service centre. Remember you should run the NI applications standalone at least once after upgrade before you use them in Sonar.
 
VST Reset and rescan:
https://www.cakewalk.com/Support/Knowledge-Base/2007013315/SONAR-X3-Full-VST-Rescan-Recommended-for-Upgraders
 
Otherwise you need to find out what the problem plugin is (start in Sonar safe mode and remove them one by one, or add them in one buy one).
 
I would also uninstall mix control (whatever version you have), reboot, reinstall mix control 3.6 from Focusrite website. Then on mix control restore factory default and clear all settings. If you are using legacy Windows firewire drivers you shouldn't be! Also update your firmware and drivers everywhere inc BIOS.
 
Consider running chkdsk /R and a defrag.
 
Finally try running Sonar as admin (or vice versa if you are already doing it) to see if it makes a difference.
 
Ta.
 
p.s.
 
Oh and temp disable antivirus and network adapter.

hockeyjx
Out of curiosity, did you rescan your plugins?

Yes, but didn't help.
 
 

NB Not just rescan, reset and rescan (all in my link above) - thx.

@John
tried all ThreadSchedulingModel Options, all the same problem.
 
@Doktor Avalanche
 
Yes, installed everything in CCC. And yes, I've done reset and rescan.
 
It's not only related to NI Kontakt5 only. Other samplers like MachFive3 or EW-Play causes similar problem, not as heavy as with Kontakt, but same behavior.
And again, the problem occurs in empty project without any fx-plugins loaded, without any audio or midi data, only about 30 or more empty instances of Kontakt5, Machfive or EW-Play.
 
No problems with VSL-InstrumentPro sampler, but this is VST3, my other samplers are VST2. And the problem also don't occur with synths like Z3ta or Rapture.
 
And I'm sure it has nothing to do with Focusrite Mix Control, I'm on 3.6 btw.
Rollback to Sonar Ipswitch and all works without problems. Update back to Jamaica Plan and again the same problems.
 
It's very simple:
IPSwich, no problem.
update to Jamaica, problem.
back to IPSwitch, no problem.
again update to Jamaica, problem again.
 
The fact that it worked ok when i go back to Ipswich shows me, that it has nothing to do with any of my plugins or my system. The only thing that changes is the update of Sonar to new Jamaica Plan.
 
In Jamaica Plan there are changes in code to "Synth Streaming Multi Processing" and maybe this changes causes the problems. This new synth streaming engine should reduce the cpu load on playback, but here it increases the load.
 
-Markus
 
 
 
 

You may be right, but there's a big BUT to this...
 
I've had similar issues with the Saffire after upgrading Sonar. The above process I've listed fixed it. Please don't be too sure that you know what the issue is, rule out other issues first...
 
I'm afraid just because the previous version of Sonar works, you cannot rule out the that there isn't an issue with your environment or plugins in the latest version of Sonar. It may appear entirely logical, but all software has dependencies, Sonar simply may be making other programmatic calls that it didn't do before (perfectly legit), or the plugin maybe behaving differently under Sonar... and think about it, I have a Saffire and Komplete as well yet not experiencing these issues.
 
I strongly recommend you at least attempt my suggestions above (I have since edited the post #4 to be more complete).

Mdages,
Doctor A may have a point.  I also have the Saffire40 and Komplete and I'm on the Jamaica Plains update so far without a hitch.  
I've run Kontakt5 in bunches over the last two days and I'm not experiencing what you see.  Is it possible that it's an isolated issue?  
Have you reported it to the Bakers???

FWIW, I loaded 10 instances of Kontakt 5 - 16 Out, and lowered my buffer to 64 samples. This got my lowly Q9550 idling with its first core up around 65% and the others around 40%. Starting playback had little effect - maybe adding another 5% to the first core. Enabling Dynamic Arming added another 5-10% under playback.