Kore 2 multi processor support

When is Kore2 going to support multi processors?
It seems crazy that I am able to use more NI instruments and plug-ins in Ableton Live and Logic Pro then I'm able to in Kore2.
NI support suggests the work around of using multiple instances of Kore2 in my host workstation. Yea that works but makes owning a Kore2 controller pretty pointless.

 

Hopefully if there is a Kore 3 there will be multi processor and 64 bit support. Both are needed badly.

When you have multiple instances of Kore open, the little Kore Controller Icon at the top of the software will be yellow when that instance is the focus of the controller. You can scroll through all of the instances that are open with the contoller as well.

But this still doesn't help if you have one large KSD with lots of stuff in it. I am always pushing 1 of the core's on my 8 core processor to the limit. And it sucks because the other 7 cores are just sitting there doing nothing.

 

Me too. But I do think it's probably more of a challenge to make Kore multiprocessor compatible compared to ordinary hosts, the analogy with Live and Logic doesn't hold up well really. Yes Kore is a host in that it "hosts" other plugins but functionally it uses them in a very different way - you may have several plugins but they are not all in neatly demarcated tracks that can be assigned to different cores, they are usually integrated into one "super instrument" with each plugin playing and processing audio simultaneously.

If you think of Kore on the level of a complex instrument rather than simply a host, how many instrument plugins are multi processor capable? The few I know of such as CoFX Blue that have multicore aware versions often have lots of problems too (so much so that I had to go back to the single core version) - the technology may be a few years old but all the bugs do not seem to have been ironed out when it comes to multiprocessing and audio apps.

 

I hope NI has went back to the drawing board with Kore,and are thinking of different ways to make it work with modern day processors.Cpu's are going to just become more powerful and faster,with more multi core this,and that,so they need to rethink the design.

 

Latency

From various discussions and considerations of processor architecture the single factor or compromise seems to be Latency as a result of buffering shared between cores. The cores need to be synced reliably and while an audio thread could be distributed, it is done with a compromise in latency. This compromise is acceptable for DAW, but eventually less so for instruments.

There is no rule or standard for how fast is fast enough. To an extent this is based on perception limits for humans which are not themselves fully understood or characterized. But the fact is, a thread running on a single core is least latent.

The trade off is familiar from DAW when setting buffer size. Do you need lots of tracks with a higher buffer size to ensure audio delivery without artifacts, or a few tracks running with a smaller buffer size?

I know of 1 developer that decided MP support is a waste and not possible under 10ms. This was a few years ago and with the intel i series maybe this has come down to 8ms. We all have our own preference for what is acceptable to perform with. For me, I strive for less than 5ms and select technology in the form of platform, interface and software that can provide this.

I think MP support is possible under 10ms, but perhaps for a very specific MP architecture, audio driver and computer. Something an end user or developer could explore for a custom setup in linux. But to provide a system in software that will work for everything out there; perhaps not currently possible. Answering this question would require a lot of work.

With that said, giving Kore an MP preference switch as it appears in other NI software would let users decide what is acceptable for them.

jonathan adams leonard