High CPU load with Wavelab and Izotope plugins

Hi there,

I have a problem with Wavelab and Izotope plugins, and I suspect they are related to Wavelab, as the same audio with the same (only one) Izotope plugin (in this case the Neuton 4 Advances EQ) does not cause any problem with Adobe Audition - the computer remains silent and performant.

My setup in a nutshell:
Macbook Pro Retina 13" early 2015
macOS Monterey 12.7.1
16 GB Ram
512 GB SSD
Wavelab Pro 11.2
Izotope Music Production Suite 6

The problem:
Normally my Macbook runs absolutely silently.
However, when I load e.g. the Neutron 4 EQ in the master section of the WL Editor, the fan starts to work pretty heavy, the sound of the fan is disturbing (the computer does not get hot, the fan works fine), and the CPU load of WL increases by more than 70% (that of the WindowServer process by approx. 15%). The Neutron 4 EQ window is hidden to avoid generating even more load.

As can be seen in the screenshots, the audio processor load in Wavelab is not high.

At first I thought that my Macbook might not have enough power, so I did a test with Adobe Audition, which I don’t normally work with, and - as mentioned above - it runs perfectly and silently.

Do you have any idea what the problem could be?

Thank you in advance and best regards

Markus Hoffmann

1 Like

I have same very high CPU usage with izotope Ozone 9, Insight 2 and Tonal Balance Control 2 in Wavelab 11 Pro. Maybe someone else could check izotope plugs in Wavelab and share if have similar behavior?

Windows 11 23H2, i9 13900KS, 64gb RAM.

I see the same thing. Even when doing nothing, or if Wavelab is idle, the Izotope plugins seem to consume a lot of CPU. Only if Wavelab has been unused for hours do things calm down. But, play audio for 1 second, and this happens, and it stays that way after stopping playback and using another application for a while.


I’m on a desktop and I also have a similar experience with Necter 4 Advanced EQ. Delay compensation?

When WaveLab is in stop mode, the plugin continues to process, but silent samples. Apparently, this plugin does not do any optimization for this case (some other plugin do).