Amplitube 5 high cpu usage issue

AmpliTube TONEX, AmpliTube 5, AmpliTube Custom Shop, AmpliTube Joe Satriani, AmpliTube Brian May, MESA/Boogie®,Orange™, Fender™, Hendrix™, Metal, AmpliTube SVX, and more for Mac/PC

Amplitube 5 high cpu usage issue

Postby nothingness6 » Fri Jan 17, 2025 7:49 am

I recently purchased AmpliTube 5 and noticed that it uses lots of cpu resource. I'm using Studio One and have other guitar amp sims as well. So, I tested it how much each amp sim uses the resource.
It turns out that Amplitube 5 uses it 2-3 times more than other ones. Holly molly.
How do you handle this issue? Is the developer going to optimize it in the near future? Or no hope?
nothingness6
 
Posts: 1
Joined: Sat Aug 19, 2023 2:42 am

Re: Amplitube 5 high cpu usage issue

Postby R0lias-tg » Fri Jan 24, 2025 1:42 am

One thing I've noticed in Reaper is that the CPU utilization for the AT plugin can be dropped by as much as 60% by clicking on the splitter icons when using just a single path. Click on the double splitter, then go backk to the single splitter and the CPU usage drops. Unfortunately you have to do this every time Reaper starts, or anytime you change to a new preset. It might be the same for your DAW.

Using AT5 as the host I don't see a significant drop in the %CPU usage when doing this so it might be a problem with just the VST/AU versions. I've never reported this to tech support since it doesn't cause me problems but you might want to.
User avatar
R0lias-tg
 
Posts: 37
Joined: Mon Jan 16, 2023 10:10 pm

Re: Amplitube 5 high cpu usage issue

Postby neil.cummins1 » Sun Feb 02, 2025 10:20 pm

As a fellow Studio One user and also struggling with even a single instance of AT5 with high CPU load....are you using the Low Latency Monitoring feature within S1(the Green Z) If so,then this will seriously ramp up your CPU load,and this is mentioned in the S1 user manual.

The reason is that the Low Latency monitoring feature(which allows low buffer sizes for recording but high buffer sizes for playback simultaneously),opens a second instance of whatever virtual instrument plugin you're using as a Monitor FX patch...open your performance window in S1 and you should see two instances of AT5 with almost equal CPU usage...which effectively doubles the CPU footprint.

Obviously I'm only speaking for myself here,the workaround I use is to set the Audio device and Processing buffer sizes as low as possible,in my case 64 samples.This gives a barely functional instance of AT5,but anything with an expansive signal chain or dual amps causes my CPU fans to activate,this is even in a project that contains no other plugins.

I have a large range of IK software,and many of the plugins are quite demanding on CPU cycles,so compromises and workarounds are the order of the day until my i7-powered laptop DAW can be put out to grass in favour of something with more cores and RAM.

Hope some of this helps,
Neil.
neil.cummins1
 
Posts: 38
Joined: Sat Apr 18, 2015 4:54 pm


Return to AmpliTube Guitar Amp & FX modeling