So this is my problem: if polyplex track is armed, the cpu is high. I arm the track for recording: real time cpu goes up above 30% I disarm the track for recording: cpu goes down to ~ 0% I load polyplex: real time cpu goes up above 30% On the other hand I can give a more precise description of the problem now : Ok, I will check them, however t seems I don't have problems with my current settings.

If this is the case, i will be happy, but still curious what is that first cpu spike with 33%. If I load Polyplex, Then load U-he Repro-5 and play some notes, the overall cpu goes down to 5%. Is there some workaround to lower this 'default' cpu usage? So as a simple user, I question: is this a bug in Polyplex, or is this its usual behaviour? I can use Polyplex without problem, so i can't talk about overload, but if I populate my project with other tracks and instruments, I'm sure cpu will be maxed out. I could say Monark as another positive example, though it has a bigger cpu footprint than Razor, around 10% in Reaper's real time cpu.Īnyway - in the Polyplex case 33% for real time cpu is too high in my oppinion. There are other Reaktor Synths, where I can't see this bad behaviour,įor example the real time cpu in Reaper goes up to 3% after loading Razor. So This is my problem: simply loading PolyplexĪnd without using it the cpu goes high immediately. Hardware: Intel i7 Cpu (4 cores) 2,8 GHz 32Gb RAM This is not Reaper's fault, I see exactly this happening in Fl Studio.įorm and Rounds had the similar behaviour, though the CPU usage was lower, say 15-20%. I don't hit any key on my keyboard, just load Polyplex in Reaper,Īnd see the Real Time CPU goes up to 33% and stays around 33%. Because the main problem is the following:

Cpu overload fl studio