I recently installed the free version of Kontakt 7 along with some of the free libraries they offer. Just as a general question, is Kontakt known to be a heavy resource using program? I have several small projects using Halion SE and Grove Agent SE, but when I threw a couple of Kontakt instances into the mix the peak meter in the performance monitor almost doubled. The jump surprised me because I really hadn’t assigned much of a part/event to them.
You might need to change the multiprocessing option in the Kontakt 7 plug-in.
In Cubase | Studio setup | Audio System:
… and in the Kontakt plug-in, File | Options:
Already had Cubase set correctly. Changed Kontakt to muti-core but I haven’t noticed any change. Mind you, I’m not asking because the use is excessive by any means, just a lot more than Halion seems to consume. I am not even close to peaking out.
Are you saying turn multiprocessing to off?
I also have peak problems with Kontakt 7 and a few libraries.
You mean that we have to put it on off even if we have a CPU with several cores ?
Try it. Turn “Multiprocessing support (VST3 Plugin)” OFF in the Kontakt plug-in.
This is seperate from the same option in the Kontakt standalone.
You’re not disabling cores, you’re just letting Cubase handle the multiprocessing.
2 Likes
If it’s ON in Cubase and ON in Kontakt, there may be fisticuffs between them trying to apportion control of the cores.
So, OFF in Kontakt, ON in Cubase.
I believe the same principle applies to HALion, etc.
4 Likes
I didn’t know any of this, so I looked at mine and it was set to 16 cores. I turned it to off and you have to restart Cubase. Interestingly though if you try to enable again while in Cubase it warns you not to have it set, so that’s good. Shame the default is all cores in DAW plugin mode.
To be honest I haven’t seen a difference. The library I use which is the shreddage stratus has the performance meter bouncing up although it doesn’t seem to be causing g problems.
Same thing for me, I don’t see any difference after turning off the option in Kontakt : some libraries like (LORES for example) still have huge peak in Cubase 13 performance monitor while playing.
The only solution I found is to increase buffer size in asio settings.
Whats your buffer set to in Cubase - you might just have to raise it when you use shreddage
I go between 64 and 128 with an RME Babyface pro fs. These give me low latency so I don’t want to go higher. Mine doesn’t peak so I can manage it without raising the buffers. It does seem that some kontact libraries are quite cpu hungry. I don’t get it with other plugins, not even with sd3. I have quite a powerful pc as well.