High CPU Performance on Mac
-
@problema what CPU usage are you talking about? The DAW meter or the activity monitor?
The UI shouldn‘t have any impact on the DAW meter as this is only monitoring the audio thread so if it goes up there‘s something that is stalling the audio thread which shouldn‘t be there.
-
@Christoph-Hart thanks for the reply!
When the UI is on the screen:
- Reaper CPU usage also increases in Activity Monitor from 20% to 85%.
- Energy Impact for Reaper in Activity Monitor increases from 20 to 80.
If DAW meter is only monitoring the audio thread what could stalling it when UI is opened?
-
@problema Have you deferred your ui script?
-
So you‘re talking about the activity monitor, right? Because then the numbers are fine but if the DAW gets laggy you need to check what you‘re doing that causes too many repaints.
-
@Christoph-Hart yes, about activity monitor.
It's been almost a week since i try to solve this High CPU Performance.
I exported VSTi without UI, knobs and code but the issue was still there.
I turned off every modules in this instrument and find that problem is in Parametric EQ.This VSTi has 10 Samplers with 12 Parametric EQ and if i turn off 9 EQs, the CPU Performance becomes around 30% instead of 80%.
Here is a thread where Dan Korneff solved this issue with Parametric EQ High CPU Performance on Mac installing the new IPP version, so i updated IPP but the problem is still here.
-
@d-healey how can i do this?
I deleted all the UI, knobs and code and there nothing changed.
The issue with high CPU performance appears when i use several Parametric EQs. -
@problema Doesn't seem to be a deferred script issue, seems like it's the EQs as you've discovered.
-
Have you disabled the spectrum analysers for the EQs? If they all run a FFT at 30fps you‘re burning a lot of unnecessary cycles.
-
@Christoph-Hart you’re a real wizard, now everything works as It should!
Thank you very much for the help!
I checked it before, but when I opened the HISE project, the spectrum analyzer blue light was turned off, even though the EQ spectrum analyzer was on.
That must be why I didn’t find the solution. -
@problema Ooops, you're right. I've pushed a fix that shows the correct state of the button now.