kontakt cpu spiking

I have searched NI forums extensively but found no solution or many recent threads on this issue. My system (6700k, 32gB RAM, SSD x 3, Roland Octacapture, running Win10) seems pretty robust and generally has not issues but for reasons I cannot explain cannot run more than a couple of Kontakt5 instruments without choking. A typical scenario would be 3 or 4 instruments, e.g., Maverick, OTS Modern Nylon, OTS  Strawberry and Vintage organs running standalone resulting in cpu spikes to 100% causing momentary audio dropouts. When not spiking the cpu indicator (in Kontakt) is generally less than 20%. CPU meter in task manager is very low, barely registering and never reflects the spikes which are instantaneous and probably too short to register. I notice that the spikes seem only to happen if I have been playing for awhile, several minutes at least. But once they start they rapidly recur every few seconds. Changing driver settings, even increasing to unplayable degree of latency does not seem to matter. Thoughts??
 
Brian

Some of the Vintage Organs are CPU killers.

Just in case you haven't done this......check to make sure your Octacapture has the latest drivers installed.

Finally have worked through as many alternatives as I can think of to explains this behavior.
It is not Sonar as it happens equally in standalone.
It is unrelated to speed step or any other bios settings.
Unrelated to whether wifi is enabled or not.
It is not a Roland driver issue - the same thing happens with my Focusrite 2i2.
It does not matter if I run multiple instances of single instruments or multiple instruments in one rack.
It only happens with Kontakt. I can run mult instances of Ample AGG, AAS instruments, mult other NI instruments or anything else without problems.
That said, I dont think the problem is Kontakt, per se. I can run large multis without problems, say 5 or 6 instruments with cpu (monitored in Kontakt) usually peaking around 25% and averaging much less UNTIL I throw in an instance of OTS Stratosphere. Once I do that the cpu starts cranking about 40 -50% and if I add a second instance of Stratosphere it will crash within 5 minutes of playing fast dense chords. Interestingly (to me) a second instance of Stratosphere will rapidly develop clicks and drop outs then crash even if two instances of Stratosphere are the only instruments in the rack. I have been experimenting using Cupcake and E Flat presets for each instance every time. They do have effects so other presets may behave better (or worse). I experience no prob running multiple instances of OTS Modern Nylon.
Latency Mon runs green until it crashes, then suddenly red. 
 
In summary, it appears that OTS Stratosphere is the culprit. Also seems curious that it takes a little time to develop. As if Stratos isnt letting go of notes and they eventually build up with a crescendo of clicks and drops before ultimately crashing.
 
Is it possible that there is some parameter in Stratos that I have mistakenly changed or perhaps a bug that causes this behaviour? I would be very interested to know if others can reproduce this problem or if others can run multiple jnstances of Stratos all day with no issues??
 
Brian

I forwarded an issue back then to spitfire , and i narrowed the issues to voices handling in the last versions of kontakts specially when they use in the script the octaver or stuff that when you play one not it play several , so when you start to play chord , it in fact mega chords !!!!

It was confirmed by spitfire and NI is aware ...it s on their side , it was wasn t present before a certain update ....

Can you make a SONAR project using Kontakt and OTS Stratosphere that shows this huge spiking?  I have OTS Stratosphere and I added a couple of instances and loaded those presets you mentioned and fed it some reasonable guitar MIDI files.  Inside Kontakt it was reporting the CPU around 20-25% but nothing crazy.  In Kontakt you can switch the instrument to info mode to see how many voices it's using and how much memory.  Might be a clue there.  Or if you can create a project that reproduces it reliably we could look at it.
 

filtersweep
Is it possible that there is some parameter in Stratos that I have mistakenly changed or perhaps a bug that causes this behaviour? I would be very interested to know if others can reproduce this problem or if others can run multiple jnstances of Stratos all day with no issues??

Try disabling Resonance in the Setup tab, I've found that to be a cpu spiker in any library that has Resonance turned on.