Amplitube is very CPU hungry, and I have a problem with it. There are only 16 internal parameter changes in it. I would have to run multiple instances of Amplitube to control the 8+ pedal chain I want to run.
Now I found that I can map the Midi CC’s in the widget parameter, but it does not sync to the widgets upon preset changes within the application, or even GP preset changes, because the midi CC’s within amplitube are not parameter assigned.
There is no Midi out to sync the midi cc’s on the Amplitube block, so i cant run it into the Local GP port and assign it to the widget to sync it that way.
I may need help with some possible scripting to get this to work
I think even with scripting that is not possible as you are not using HOST-Automation when map Midi CC’s to the widget.
You are simply sending the CC messages to the plugin, this is a one way street.
But I found this in a forum
As a quick step-by-step -
Right click on the element/control you want to automate e.g. volume pedal
Highlight/select Assign Automation>Volume>Param 1
Assign an automation track in Logic to Param 1
Automation can now be recorded/drawn and played back
yes i did try out that parameter mapping, but since im trying to run a long chain of pedals, amplitude ended up being less than optimal since it only has 16 parameters, and the midi cc’s dont sync.
However, TH-U has dedicated parameters for a majority of the pedals in the plugin, and though it only has 15 mappable parameters per in-plugin preset, running multiple instances is no problem due to the low CPU load.
I found that TH-U had less high quality modeling for its effects, but the variety, mapping, overall control, and rock solid leveling made it better in conjunction with Gig Performer
My CPU usage on about 3 instances of amplitude 5 was around 60%. Running a 2023 Macbook Pro M2Max. Its got the cpu juice in it.
I was thinking about chaining the pedals like you have it. I don’t know how you ended up running so many, maybe not running the stereo option within the plugin saves on performance.
When i first got GP, we were in lockdown, so I set myself the task of recreating my analogue board. I was on a mid 2012 MBP at the time, and mono saved a lot of cpu.
For gigs, each rackspace only has what is needed for that sound, 2 or 3 plugins usually, in stereo. Amps in the Global. Ran at 44.1/128 on the MBP.
Now at 48/64 on base M2 Mini. Could go 32 or 16, but why risk glitches.
You will be doubling your cpu use for no perceivable advantage (in a live environment) at 96k/128. Most plugins that would benefit from a higher sampling rate (because of aliasing) do so internally with oversampling.
If you are not using any audio in, just MIDI driven input, you may even feel comfortable with the latency at 48k/256 samples. (at 5.3ms this is less than the action of an acoustic piano)
This would be a massive increase to your cpu headroom.
