Global MIDI Controls and AmpliTube 3.5

So it’s been over a week since I posted about AmpliTube 3.5 and MIDI control. I had planned to post more sooner but my personal and professional to-do list just never stops. I wanted to do a little writeup on single-source multi-target control of AT3.5 (next post or so) but got a little distracted by all the other MIDI options within AT3.5 and the quick realization that I had no clue what half of this stuff was even for.

One aspect of my pedalboard are these two oddly placed switches kind of lower and between what would normally be bypass switches for the pedals.

Preset Browser Switches
Preset Browser Switches

My intention was to make these preset browsers but never tried to do so until this writeup. I have spent a lot of time in the MIDI Control Preset window where I never saw the option and obviously never really looked at the Global options. Getting to the Global options is simply a matter of clicking the MIDI button in AT3.5 then selecting the Global button in the top left corner.

Global MIDI Control Window
Global MIDI Control Window

I’m glad to see that AT3.5 has two specific pre-configured entires for preset changes. If you recall from my previous post “Quick Guide To Using External MIDI Controllers with AmpliTube 3” all I need to do is highlight the Preset Next entry, click Learn then tap the next button on my controller. Repeat for the previous button and we’re ready to change presets at the simple tap of a foot.

Other Fixed Options in Global MIDI Control
Other Fixed Options in Global MIDI Control

So next my eye is drawn to the Volume, Wah, and Wharmonator entries. Probably because I want to try and exploit them in unintended ways (it’s a personal tic). I can’t help but wonder what happens if I use two volume pedals in series? Ok sorta dumb I know, but what if I run a parallel config like signal chain 2 and have a pedal on each, what happens then? If I use two different Wahs, does it alter both? Let’s find out what’s going on here.

So after training the volume in signal chain one, anytime I drop a volume pedal, and regardless of which slot I move it to, the volume control just works. Pretty nifty. A huge time saver for a commonly used pedal. Dropping a second volume in-line defaults the control to the first volume in the series. That makes sense. Setting up a parallel config and placing a volume in stomp A and stomp B results in only the pedal in Stomp A responding to the controller. This makes a little less sense to me but I get it. Ok Wah time. I set the Wah row to learn in Global MIDI control and tap on a pedal. Good to go. Returning to the stomps I run the same tests as the volume and get the same results. I’m not terribly surprised to get the same results.

This all may sound like a bunch of overkill but I was just curious to learn the primary intent of the global ‘default’ controllers and now know it’s just for your first matching pedal in the chain (and behind the scenes AT3.5 scans Stomps A through B in slot order order making no distinctions between serial or parallel configs.) Obviously any deviations from this single pedal approach are best handled by MIDI Preset control setups as covered in the previous post but part of me wouldn’t mind a ‘cascading’ approach to control the first ‘non-bypassed’ Wah in the chain should I want to use two flavors in the same preset. Just a thought.