Hi,
I'm using a similar setup to @smcvey.
For the same reasons , Hold 2 switches for +1 seconds is not practical for live or creative use
Not to mention going back from LOOPER mode to STOMP mode , PRESET MODE it takes 3 times longer.
My setup is not with an IPAD but with a Mac.
And instead on the Mongoose I use and old "Art x-11 midi foot controller", 5 switches plus up/down (+5/-5) for preset changes
It can only be used for preset change, because it is the only thing the Art switch is sending
Logically this leaves the STOMP-I/O-CONTROLLER for "STOMP MODE" and/or LOOPER control
But..
It seems to be that Amplitube only receives MIDI messages from the STOMP's MIDI in if NOT on Integration mode, when Selecting "Stomp I/O #1" Midi input.
Is that right of I'm missing something here ?
Then ...
When setting MIDI input to "Stomp I/O #1" disables "LIVE MODE" and the looper control.
Requiring to MIDI-map #1, #2 and #3 switches to the loops.
Not #4 because you loose global/play stop.
You can start "looping" with #1, continue with #1, and press-hold to stop it
The same with #2 and #3
But ...
The Switches send Midi change messages, 0 and 127 (press/release) and alternatively +10/0 when press hold,
Amplitube's Looper seems quite confused with that, ...me too
I did also tried connecting Amplitube to the "Mac MIDI Bus"
Then redirecting/patching, all hardware interfaces (STOMP and the ART controller with a USB-MIDI adapter) to the "Mac MIDI Bus".
I do that with 3rd party applications/software like "MIDI patchbay", "MidiPipe".
But its the same thing , loosing "Live Mode" and a confusing "Looper mode"
NOTE:
The LOOPER was one of my main excuses to buy the STMOP I/O
All in all I'm Still happy,due to the amazing value provided by the bundled AT4 deluxe, and Better I/O quality than my previous iRig UA)
But I thought it was going to be more flexible in the MIDI setup
Now I'm thinking/looking around for "another MIDI foot switch" to control the looper, and leave "STOMP-I/O" always in "STOMP MODE"
But its going to be harder because it has to send control changes (0...127) instead of "Patch/Preset" change.
Software might help with re-mapping MIDI events ... but could make it less reliable and configuration prone.
And what about the "Tuner" ? , candidate for EXT1/2 of the STOMP controller?
Suggestions, Ideas ?