K 3.01 only using 1 of 4 core CPU

Using a rather large orchestral multi (EWQLSO Gold) kontakt seems to be only using 1 of 4 cpu's,
it's almost like kontakt is ignoring the fact the system has 4 cpu's.

Logic Pro 8.01 (was the same in 8.0) Mac Pro Quad 2.66 4GB Ram OS X 10.4.11

any ideas deas ?

 

Try enabling Multi Core processor support in the Options menue. You only benefit from it if you set the Buffer size of your host sequencer to 1024 otherwise this will slow things down and there will be no benefit from it whatsoever.

 

Matt =)

Sampleconstruct's right. Multicore support has separate settings for plugin and standalone, and it's off by default.

And yes, you'll have to raise your latency for proper core distribution without a crippling amount of overhead.

ew

 

thanks

(hi eric)

ok Im will try that, although it seems odd to have to raise up the latency so high.. thats the one of the nice things aout having a fast system..low latency.

so is this an NI or Apple issue ?

I would guess NI as logics plugins do a good job of cpu distrubution for it's own plugs. ?

 

Personally, I've found it better to only use one thread distribution scheme; if your host is multicore friendly, turn multiprocessing off in Kontakt and use multiple instances instead. YMMV, of course...

As to why Logic seems so much more efficient, it's because it can internally compensate for the additional latency to some degree.

ew

 

I did try using multiple instances, ie one instance of K3 for strings multi, 1 for brass etc but it still seems to load onto one cpu.

it seems very odd that k3 wont distribute it's load across all 4 cores.

raising the latency only improved the cpu usage but made things hard to play and still laboured on one cpu when adding more instruments.

 

my question has been answered by NI support.

Multi Processing does not work for live performance, only playback.

:|

 

Topaz,

"Multi Processing does not work for live performance, only playback."

I'm not sure I understand. How could Kontakt, which is not a midi sequencer, look ahead at midi data from, say, DP or Logic? Why would playback make much of a difference?

 

you will have to ask NI support this, I am only passing on what they told me.

 

It seems like Multiprocessing is not really happening. This is a screenshot from a project - Multiprocessing enabled - Logic Buffer 1024 - 1 multi Instance of K3 with a convoluted Steinway, violins, violas and solo double bass playing on different Midi channels - and two normal instances of Kontakt one with a lead guitar the other with legato celli. Besides that 1 instance of Reaktor 5.1.4, 2 Busses with Space Designers and 1 Bus with Delay Designer.

But also notice the difference between the CPU display from activity monitor (on the right) and the CPU meter in Logic. It doesn't look the same at all so it could also be a Logic or Apple display/CPU-managing-problem.

 

probably they mean it does not work in standalone, or maybe like Reaktor stand-alone, it uses a core for the graphic visualizaion and the other for processing.. this is not reallly multi core support tbh..
if you want to use kontakt in multi core live (or not live doesn't really matter imho) use a vst/au host multicore capable and run multiple istances of kontakt inside.

for multiple istance i mean you have to open more kontakts!

not 1 kontakt with multiple instruments!

this is a logic limit imho also, there are no plug-ins that uses more than 1 cpu for every istance.
this mean also that is better to have 1 powerful cpu that goes 100% than having 4 cpu that goes 25%, cause if you have a kontakt ensemble that consumes 30% you are not able to open it. (that's why also i'm always against multi-cores, they need more programming to make them usable and most applications are still behind, but this is the way they go so...)

probably in stand alone you still open this because of graphic that goes on the other cpu, well in reaktor works in this way and i don't think here is different.