Hello, I'm on a windows 10 laptop.

I just recently re-installed Reaktor 6. It the 'try before you buy' version from R2R.

As soon as I open either the standalone or VST, task manager reports Reaktor as using anywhere between 35% and 50% cpu -- without even opening a patch or ensemble.

I don't seem to remember this being the case when I've had it installed in the past.

Just wondered if anyone can shed any light on why this might be happening... and what, if anything, can be done about it.

For info, I also have a few libraries installed: NI Form, Scratch Mater Pro, Molekular and Polyplex [also R2R 'patched' copies] -- not sure if any of these could be causing a problem, but like I said I haven't even opened them yet and it's still over-using the CPU.

 

Last edited: Apr 28, 2025 at 2:26 PM

3.2 CPU Usage Setting
Reaktor can automatically reduce the number of voices in polyphonic instruments. To do so, follow these steps:

1. Go to Preferences > CPU Usage. The Max CPU usage (%) setting will disable additional voices when the defined CPU limit is reached, allowing you to spare CPU power. In the example below, Reaktor will kill additional voices as soon as the CPU load reaches 60%.
   
2. Enable Automatic Voice Reduction in the loaded Ensemble. You can activate this option in EDIT mode > Properties > Function > VOICE ALLOCATION > Automatic Voice Reduction.
   

3.3 Heavy Reaktor Instruments (Polyplex, Rounds, etc.)
Some Reaktor Ensembles require more performance than others. This is especially the case for new Instruments like Polyplex, Rounds, Kontour, or Molekular. To avoid facing performance issues with these Instruments, you can use the bounce technique, presented below in chapter 3.4. Bounce to audio!

Rounds, for example, is very heavy in terms of CPU consumption, since it consists of 16 synthesizer voices (8 analog emulation, plus 8 digital). Additionally, a voice programmer provides 32 sound slots with morph functions. This sums up to very much audio processing which can be very heavy for your CPU.

Polyplex loads by default with 8 pads, containing 4 samples each, which in turn are sent through their own effect chain. This sums up to 32 effect chains, which is very heavy in terms of CPU consumption. To avoid overcharging your CPU, you can load from the Browser a stripped-down version of Polyplex, in order to use only the Kick or the Snare module for example.


Source & more: https://support.native-instruments.com/hc/en-us/articles/360000228329-Reaktor-Optimization-Tips

 

@Radio It seems that your hints apply to the situation when instruments are already loaded, while the OP specified that the problem happens without even opening a patch or ensemble...

 

Great response. Thanks @Radio. Installing Rounds now. Looks amazing!

 

Yeah, somethings gone wrong here, it's not expected behaviour.

So on any empty ensemble it does this? Does it do the same on an empty rack (a Blocks patch)?

Does the MIDI/OSC show any activity? I'm thinking a possible feedback loop here. Try to disable Event Loops in an empty ensemble, any luck? Not that it should have any loops to begin with, but.

Try a simple ensemble like:



Still the same?

 

Bleh, bad picture, here's a better one with instructions:



So disable structure debug (the bug icon) and disable event loops in ensemble properties.

 

Thanks for the replies. It does it with nothing open at all.

I suspect a compatibility issue with my version of win 10. (which is heavily tweaked).
[EDIT] i shouldn't say 'heavily'... it's been done sensibly and really shouldn't cause any issues... so I'm a bit stumped. Am wondering about giving Reaktor 5 a go.

I just opened my win 11 OS (where I had reaktor installed previously with no issues) and reaktor behaves normally there.

 

Last edited: Apr 28, 2025 at 3:43 PM

oK... SO how weird... just to give it a try, I opened a Debug > event watcher small.ism

as soon as i opened that CPU usage dropped.

Now I can open reaktor, and even with nothing opened, the cpu usage is normal!

It's like it just needed to open something 'native' to settle down, because I'd already tried opening my add-on ensembles and that didn't help.

Thanks all