I am noticing that if I create a small project and add a plugin to it (any plugin seems to do this - instrument or effect - I tried several, even the EQ plugin from the DAW Essentials collection) the plugin will use 100% CPU according to Waveform's built-in CPU Usage window. This is not reflected in Activity Monitor, which shows all of Waveform using less than 25% CPU on my quad-core 2010 Mac Pro).
If I add a second plugin, each of them will use some fraction of 100% such that they total to 100%. A third and again they divide it up, but at all times, if there are any plugins in the project at all, they seem to think 100% of the CPU is in use.
This is only happening in the window when it is open - the small indicator along the top of the main Waveform window is showing less than 10%.
Is this normal/expected? I don't seem to remember it being like this in past versions.
I am also noticing that the interface seems to become less responsive rather quickly compared to past versions (which is why I started looking at this to begin with) and I had a (new to me 3rd-party) plugin overload the CPU when there were no other active plugins in the project, so trying to pin down where the issue is with this.
I did just update to Waveform 12.0.5.3 just before this, but I don't know if that is related or not.
The new plugin I was testing when this came to light is Unfiltered Audio Silo (Plugin Alliance). This same plugin can easily peg the CPU under Studio One as well depending on the settings (which tells me it is a rather demanding plugin that can really stress the system if you crank it up), but unlike in Waveform, the interface remains fully responsive when it happens.
I'm on macOS 10.14.6 if that makes any difference.
CPU Usage under W12
-
- KVRAF
- 2457 posts since 9 Oct, 2008 from UK
Waveform's built-in CPU usage always shows 100%. It's 100% of what it's using. It'll divide that 100% up among all the things it's doing, but you'll still need to look at your operating system's CPU usage display to see how much your machine is using.
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.
-
- KVRian
- Topic Starter
- 524 posts since 16 Mar, 2017
Ok, thanks, I guess I wasn't accurately remembering how that was reported then. The fact that the UI starts becoming unresponsive as quickly as it does is still something of a concern, but I suspect that was probably the case in WF11 also. I had a similar problem with Studio One at one point until I realized that hardware acceleration of the UI was turned off; turning that on fixed the problem for S1.