Kontakt 5.3.1 cpu spikes in Pro Tools

First, here's my setup:
Mac Pro (4,1) Intel Xenon 2.26x4, OS 10.7.5, 17GB RAM, 1TB WD Caviar Black (7200 RPM 64MB cache) dedicated sample drive (new, not fragmented)
NI Kontakt 5.3.1 RTAS and AAX
Pro Tools 10.3.8 HD Accel
PT buffer setting: 512 or 1024

Clicks and pops from processor spikes in Kontakt 5.3.1. I had originally thought this was a RAM or disc issue when I posted about this a couple of weeks back. Now I've updated to v5.3.1 and I can see that it's definitely cpu spikes in the Kontakt 5 UI's cpu meter.
Here's when it happens: I initiate Kontakt 5.3.1 as either a RTAS or AAX stereo plugin in a Pro Tools session. The pops and clicks from cpu spikes happen on all NI library instruments but more noticeably on piano instruments like, Alicia's Keys. After moderate to long passages with the sustain pedal depressed I get a cpu spike and a pop or click sound when I release the sustain pedal. This will also happen in the middle of longer legato passages with string libraries, Session Strings, LASS v2.5, Spitfire Mural, etc.
I've tried almost all different settings in the K5's control panel, multi processor threads, sample pre-load, etc. No improvements or change. The cpu's indicator stays low (>20%) then a pop or click will occur and the red cpu overload indicator lights up for a fraction of a second. I don't even see the cpu meter move past 25%.
Any help on remedies would be greatly appreciated.
Thank you,
Mark

 

…anybody?

 

If you're using the latest version of Kontakt in PT10.3.8 you are using the aax version and have no way to select the RTAS version. At least I don't on my system.

That being said it's not unusual to get cpu spikes on long passages with sustain pedal down on instruments like piano. I don't have AK but the other NI pianos and they all do it to a certain extent. The system is working really hard at that point. As to pops and clicks - do you have 'ignore pops and clicks' checked inside PT? If so uncheck it and see what happens. Have you tried different settings in Kontakt's cpu overload protection?

I never pay attention to Kontakt's cpu meter. I use Kontakt Memory Server so everything gets loaded into the machine. Voila - no pops or clicks. The only cpu metering I ever pay attention to is what's inside PT.

If you don't know about it PT10.3.9 is out now.

One other thing - how do you have 17 gig of ram? That's a very unusual configuration. Ideally ram modules should be matched sets of the same size or even better all the same size.

 

Thank you for your reply! Yes, I've tried all other settings in Kontakt's setup. It's somewhat relieving to learn that all instruments will hit cpu spikes under certain circumstances. My upgrade to PT 10.3.7-10.3.8 was the first time I noticed it.
I always use the memory server in my instances of Kontakt. Turning it off isn't an option for me since I'll get PT's "critically low memory error" message on VIs larger than 1.5GB.
-Mark
PS- I'm surprised to hear that you cannot run RTAS plugins on a 10.2.8 HD rig! I am able to access all the plugins in the Library>Application Support>Digidesign>Plugins folder as well as the .aax plugins in my Library>Application Support>Avid>Plugins folder. My old RTAS version of B4 II still works well. (I love that VI). 17GB RAM was typing error, I meant 16GB.

 

I didn't say you can't run RTAS on a 10.3.8 rig but just that if you have both RTAS and aax of the same plugin you don't have a choice of which format to use. PT will use the aax format plugin. B4II and Pro53 are special cases as they don't exist in aax but RTAS only (along with vst and au). I just wish they were 64 bit as I could then use them in PT11 via Blue Cat Audio MB7-2 or Patchworks without using jbridgeMac which is unstable as hell.

 

Kontakt 5.3.1 aax will not run New York grand on my system, 10.3.9 PT osx 10.8.5

I get CPU overloads constant, deleting aax and using .dpm rtas solves the problem

 

What's the resy of your system setup - cpu, ram, etc. How many cores, cpu usage and buffers do you have set in PT? Have you optimized your computer setup for PT? The NI pianos run just fine here on both PT10 and PT11.

 

Mac Mini i7 2.6
10.8.5
16GB Ram
256/512 buffer is irrelevant.

How would I "optimize" my computer ?

By the way, as i stated RTAS works just fine, its AAX that hicks up.

 

There's plenty of help on optimization available on the DUC but the major steps are:
turn off wi-fi (it steals cpu cycles)
separate hard drive for PT to record to (never use the system drive)
no 'green' energy saving drives
do not let drives spin down or go to sleep; same for the computer itself - never let it sleep
as far as number of cpu cores and cpu usage you kind of have to experiment with that but a good place to start for cpu cores is 1 less than the number of cores you have; cpu percentage usage 90 to 95%
number of buffers is NOT irrelevant
make sure you have up-to-date drivers for your audio interface and do not use aggregate devices - they cause more trouble than they are worth.
oh yeah - one more - turn off Spotlight indexing; it can and will interfere with drive read/write and PT autosave.

 

Can you explain why the AAX version does not work but the RTAS version does ?

Thank for those tips but they are all implemented already.

 

That the aax version does not work on your system without seeing it in person I can't say as it works just fine here.

 

That is odd, because I just tried it on my mac book pro and it does the exact same thing.

As soon as I try and edit any midi notes up comes and error message.

 

Ok I sussed it.

Having Dynamic Transport and Link Timeline and Edit Selection on causes the error (-6101) to flag when clicking in the midi editor or timeline.

This issue does not exist using the RTAS.

Reporting to NI now.

 

I don't use Dynamic Transport but I do have Link Timeline and Edit Selection selected; that could be why you get the 6101 error and I don't.

 

Can you please try, just record some New York grand and click around in the midi editor which will jump the play head.

 

You know, if you had explained to begin with what you were doing to cause the spikes that would have helped a lot; going piecemeal is making it more difficult. But - no problems here at all. I don't use the MIDI editor available in the track but the one you get when you right click on a MIDI track and select the MIDI editor from the window/menu that opens.

 

I didn't know in the beginning that it was Dynamic Transport that was causing the issue.

Either way it's a bug as so far NI pianos is the only library causing the error.

 

You do know that when you enable Dynamic Transport it automatically disables Link Timeline and Edit Selection right?

 

Yes