Same experience as mdages after JP update on an existing project, constant playback stutter/crackle with the first core red-lining. Additionally, after attempting an EQ adjustment in a VST then stopping and closing the project, clicking save prompted an application error. Error report submitted through the in-app debugger (CWBRN-40143).

bronsoncox
Same experience as mdages after JP update on an existing project, constant playback stutter/crackle with the first core red-lining. Additionally, after attempting an EQ adjustment in a VST then stopping and closing the project, clicking save prompted an application error. Error report submitted through the in-app debugger (CWBRN-40143).

Please try post #3 & #4 and list your hardware/software here.
Thanks.

Sure, why not.
 
Problem did not exist prior to JP.
 
Dynamic arming not enabled, Thread Model was at 1, tried at 2 (Preferences/Advanced - Audio - Configuration File)
 
Did the VST reset, set to rescan every startup. No joy.
No antivirus. Don't really want to defrag my trim enabled SSDs (x3, OS, Samples and Audio). Windows is pretty good about monitoring for bad sectors since the early 2000's and I haven't seen any recommended checks at boot.
 
13 track project in Sonar Platinum (JP), the only VI is AD2, heavy on the Slate VTM/VCC with Amplitube and Bias, Waves L1 on the 2 buss for grins and giggles. Eleven Rack with latest 1.1.10 driver. All onboard audio devices disabled including HDMI.
 
8.1 Pro (x64)
Processor: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 CPUs)
Memory: 16384MB RAM
Card name: AMD Radeon HD 7800 Series
Display Memory: 9958 MB

Merely an observation: I notice that the users that don't seem to have the issue is using Win7, except Doktor on Win8.1, while the OP is using win10 German and the other user with the issue is on Win8.1 with a AMD graphic card.

@Doktor A
I've put off the Focusrite interface and tried with another one (M-Audio) and with Asio4All, always the same problems. And at last, tried to use WDM instead of Asio. But same results. So I'm sure the problem isn't related to the audiointerface.
 
As more instances of a sample like Kontakt, Machfive or EW-Play I use, as heavier the problem.
In stop mode, the load is fairly balanced on all cpu cores. But soon I start playback, even on an empty project with only 30 empty K5 instances, the first core goes up to 100% and the other cores down to about 5%.
 
-Markus

ASIO4ALL should be completely uninstalled and PC rebooted.. Very good at conflicting with existing drivers.

Also have a go with latencymon I also suggest. There's a new version just released. Also find out which process are maxing out with task manager or process explorer.

Doktor Avalanche
ASIO4ALL should be completely uninstalled and PC rebooted.. Very good at conflicting with existing drivers.

I've installed ASIO4all only for this test and uninstalled it after that.
 
As a note. My DAW computer runs very good every day and with every previous version of Sonar Platinum. My other DAW program, Studio One, also runs without such problems.
When I put in all my Kontakt instances in VSL Vienna Ensemble Pro it runs without problems.
The only program that causes the current problem is the Jamaica Plan update of Sonar.
 
Ok, I've opened the task manager of windows and now it becomes strange.
Windows task manager shows about 50% load on each cpu core, a little bit higher on core 1 that's normal, and complete load is equal distributed over all cores.
But the performance meter in Sonar shows 100% on core 1 and about 5% on core 2-4.

 
The same on cpu graph in process-explorer. Core 1 is slightly higher than the other ones, but this is normal.

From Windows side there seems no problem with heavy cpu load on core 1, only inside of Sonar. The overall cpu load on the system is about 50% and Sonarplt.exe is on about 40%.
So, there is no process that maxing out the cpu in an unusal way. The problem seems not the cpu, the problem seems any kind of multiprocessing of audio inside of Sonar.
 
And btw, tried different latency settings from 128 up to 1024. With lower latency I got Audio-Dropout error as soon I start playback, even on an empty project with no audio or midi data, only a bunch of Kontakt instances.
 
It's very obvious that this has to do with latest changes on code in JP regarding Synth Streaming Multi Processing.
 
regards
Markus

Hi
I am wondering If your problem has anything to do with mine .
You may have updated but I cannot as I get a box saying Files corrupted,obtain a new copy of the program.
As you will see on my thread.
There maybe a flaw in the update.
We will have to wait for a reply on this ,so we will have be patient AAAAAAAAAAAAAAARGH!!
 
All the best
John

JFI, I ran heavy orchestral session last night using multiple instances of Play running EWQLSO without a single hitch.
This is under Win 7.