There is an issue in Redux that really annoys me, and it is that over a period of time Redux will increase the amount of CPU it consumes. I use Bitwig studio, and if this turns out not to be a Redux bug, but in fact some sort of a Bitwig bug, then I will take this up with the Bitwig devs, but it only happens on Redux, so I assume it is Redux that is the issue.
- Add Redux as instrument.
- Load some sample into Waveform (I used noise).
- Assign some macros to some parameters (I used volume, pan, and Digital Filter cutoff).
- Close the Redux GUI.
- Modulate the Redux macros from within Bitwig (I used some manual automation and some LFO).
- Add a clip in Bitwig that plays a Redux note.
- Loop it (in Bitwig).
- Play (in Bitwig).
Redux will start off fine, playing nicely, but go and have a cup of coffee. Seriously, it may take up to 20 minutes, but over that time the amount of CPU Redux consumes will sloooooowly creep up, until finally Redux will be using 100% of a core and will click, pop and distort like no tomorrow. However! Here’s the kicker: Once you’ve got it to click and pop like no tomorrow, the CPU will immediately return to normal (low, maybe 5%) as soon as you open the Redux GUI. Go ahead, press the GUI button when you get it to click and pop.
I’ve uploaded my project file that contains the automated Redux instance. It’s all done for you, just open the project and hit play. It’ll loop away, and all you have to do is wait.