Optimisations needed for Actions Strings 2, Sequis, Lores

John6455 Member Posts: 7 Member

I've upgraded to Komplete 14 and have been testing the new instruments in the set. I've noticed that particularly Actions Strings 2, Sequis, and Lores have spikes in their CPU or disk activity usage that causes buffer xruns and clicks in the audio.

Using a larger IO buffer helps the situation, but all the other comparable instruments in kontakt run fine with my current settings. This has been tested on 2 systems, one being on MacOS with a i9 10850K, and the other on a win11 system with a Ryzen 7700X, so they are by no means under performing CPUs. I also max out the DFD buffer at 240kB to maximise loading into RAM.

I've noticed issues in the following instruments:

Action Strings 2: Repetitive CPU spikes causing xruns/clicks, particularly at the start of notes, especially triplet figures. Nominal CPU usage is around 10% as shown in kontakt.

Lores: Occasional disk activity spikes causing xruns/clicks. As mentioned I run the highest DFD buffer and this is even an issue on my win11 system using a 980 PRO NVME drive.

Sequis: Lots of xruns/clicks when holding multiple notes, CPU usage between 10-20% and no apparent disk activity spikes.


  • reffahcs
    reffahcs Member Posts: 676 Pro

    What's your audio sample rate and latency settings? Are there any particular presets in Sequis that cause more issues than others?

    I agree it could use they could probably all stand some optimizing.

    I'm on an M2 Ultra, in Lores with "A Gentle Soul" preset. Multiprocessor support set to 16 cores. But barely maxing out a handful of cores and @ 48KHz I can't go any lower than a latency of 160 samples or else I get pops and clicks. Not surprisingly @ 96KHz I have to bump the latency up to 320 samples.

    I don't really have any issues with Sequis though. Using the "New Hope" preset, I dropped my latency down to 64 samples @ 96KHz and had no sound issues.

  • John6455
    John6455 Member Posts: 7 Member

    On MacOS I will typically use 48KHz and 64 samples for a latency of 1.8ms/1.8ms in/out.

    On Windows I will typically use 48KHz and 32 samples for a latency of 1.3ms/2ms in/out.

    I do a lot of realtime processing, so I need the low latency. Those settings are rock solid for everything else.

  • reffahcs
    reffahcs Member Posts: 676 Pro

    Well hopefully NI can make some improvements. Currently it seems Lores needs quite a boost in terms of samples/latency compared to others. I guess because it's playing 3 samples at the same time? It def doesn't seem to be a CPU bottleneck.

Back To Top