Strange Heavy CPU Change in Rackspace

[xpansion]

I’m running GP 5.0.40 on 2021 MacBook Pro with M1 Max, 64GB Ram and a 1TB drive. I’m running MacOs Ventura 13.7.2.

I have a couple of rackspaces I put together 3 or 4 weeks ago that at the time of creation were eating almost 50% of the CPU at rest. In both cases, the local rackspaces have no scripts or scriptlets and I’m not running any scripts or scriptlets in the global rackspace either. It was somewhat concerning to me that the CPU was running that high at rest, however the rackspaces were usable and didn’t create any cracks/pops/etc…

While at practice after 2 weeks of gigging with these rackspaces, we went to practice one of the songs and when I started playing, the audio dropouts and distortions were horrible. I then looked at the rackspace in question and it was now showing using 85%-95% CPU at rest. I had made no changes to the OS, configurations, any of the plugins used in either rackspace, etc… Each rackspace has several instances of Korg Triton Extreme. I duplicated the rackspace that crapped out at practice and started removing plugins to see how much CPU each one was using at rest.

I have no idea how much of the CPU each of the instances of Triton Extreme were using prior to this escalation of CPU utilization at rest, however as I removed them from the rackspace, it appeared each instance was eating roughly 4% of the CPU each at rest. I’m baffled as to why the CPU utilization changed when everything underneath it hasn’t, and it is a concern given I had to reprogram that rackspace with different plugins and frankly, not quite the sound I was looking for to get it under control.

I would love some ideas as to why this occurred, and also to why Triton Extreme instances would garner this much CPU utilization at rest. I was lucky that the other rackspace in question had not been rolled into a production song yet, however now I have to either figure out the problem and get it resolved or reprogram it yet again in order to improve the song with the rackspace it is set to replace.

I can provide a copy of the rackspace if that would be helpful.

X

[edm11]

@xpansion

Korg Triton Extreme

I recall a discussion about that plugin here:

Overloaded CPU

In one of my rackspaces I need to use 5 intances of Korg Triton extreme. For the first time of my (short) use of GP, when playing using this specific rackspace I noticed a few cracks/noises randomly and I didn’t know why. Then, I noticed that the CPU usage was between 48 and 56%, much higher than my other rackspaces (typically below 30%). So, do the noises occur due to the CPU usage? Is the kork Triton Extreme vst a CPU “eater”? Any way to solve this? What is the safest level (maximum CPU p…

[xpansion]

I had read that discussion, however it still doesn’t explain the huge jump in CPU usage at rest when I didn’t change anything.

x

[vangrieg]

@xpansion

I can provide a copy of the rackspace if that would be helpful.

I guess one would need Triton installed to use it.

Do you have much in the rackspaces apart from Triton?

[xpansion]

I do, however the only two rackspaces I’ve had this escalating CPU usage issue in has Triton Extreme in it.

X

[tripleB]

I’ve also seen that the Triton Extreme can use up CPU to >40% in the past on my M1 Pro. I’ve also not been able to determine where this comes from. First I thought there are differences between AU and VST

What I tried so far:

• replace AU by VST3. Slightly lower CPU usage. However, when changing back similar CPU values
• Valve emulation on off - nearly no difference

Mainly I’m using the Triton classic at the moment, which has also a slightly lower CPU usage, and I’m more familiar with (I still own a ‘real’ Triton classic pro )

Edit: simple test: load either AU/VST3 and open COMBI A000 “The Piano” - the CPU varies from 20…40%

[dhj]

You should report this to Korg