configure midi foot controller to switch Amplitube presets?

[GuruGuitarLessons]

I’m running Amplitube 3 as a VST in Live 8. I’d like to be able to load several instances of Amplitube, each set to a different preset, into separate chains of an Audio Rack, and then use my midi controller footpedal to select chains – in effect allowing me to change presets with my foot pedal.

Here’s the rub though, I’m sending CC info, not midi notes, with my pedal. In the audio rack I can’t enable the midi filtering of CC info.

Anyone know of a way to accomplish switching Amplitube presets with a foot pedal sending midi CC?

[rdevries]

I'm not quite clear on what your problem is: are you able to operate the chainselector in the rack with the pedal?
If so, why would you need further midifiltering?

also,
why not send your pedal cc's to Amplitube via a miditrack so you can learn it to the next and previous preset?
This way you only need one instance of AT-plugin. (btw,i just posted another thread about a different problem concerning preset-changes in AT using a footswitch)
I might be missing the point here.

[UKRuss]

devries is right, just use the pedal to change presets in one instance of amplitube.

Or ig you do want to sleect chains, then you simply need to adjust the range over which the chain slector selects each chain, then map that to your pedal and as you scroll through the CC range it will switch between the chains.

open the chain window and manipulate the green bars to only span one section of the full 128 chain length making sure there areno overlaps, or i think you can right click and choose 'distribute over range equally' somethign like that.

then map to the chain selector on the top and bobs your firkin

[GuruGuitarLessons]

Thanks for your replies. I've learned that I don't need to change the midi filter, I was a bit confused on that. But my problem is this - my pedal does not act like a rotary controller, i.e. it does not send out differing values for one midi CC; each pedal preset can send out one value for a unique CC, that is why I can't use the chainselecter in the rack with my pedal.

Amplitube also does not make it possible to use midi to switch presets when it is running as part of a host application, this can only be done when it is run as a standalone application.

Re: "why not send your pedal cc's to Amplitube via a miditrack so you can learn it to the next and previous preset?" Curious how that works, since Amplitube is added to an audio track. Can you provide more detailed info on how to set this up? Even so, I'm hoping to find a one switch solution, rather than having to hit the pedal multiple in some cases to get from a current preset to the next desired preset.

Best thing I've come up with yet is to load several instances of Amplitube into the effects chain, and map the device on/off for each one to unique pedal presets - then with just two pedal hits, I can turn off the current device and turn on the desired one. Also saves CPU by having only one instance of Amplitube on at a time.

[UKRuss]

Amplitube has a midi learn function. Simply select the 'next' or 'previous' preset selector and midi learn it to a specific pedal. then the pedal will simply scroll through your presets with each touch.

Although you may end up with the same problem that devries has in his other post.

[UKRuss]

ah also, set up a misi track next to your audio track with amplitube on. Then in the midi track selec midi from your pedal port and midi to the audio track with amplitube on, another drop down will apeear indicaiting that the midi will now be routed to amplitube.

arm both tracks and away you go.

[pennywisdom]

Is it possible to use Rig Kontrol 2 to control amplitube?

[UKRuss]

Hmmm, not sure about that. I don't have either to be honest so, not sure.

[phunkphace]

So.... did the problem get resolved of being able to switch presets in Amplitube 3? I know that the plugin has a midi window where you can select global parameters. In there, there is an option to midi learn for next and previous preset, but every time I try to learn, it doesn't recognize the midi messages. I even tried to select the exact cc# that I wanted to map to my MPD32, but it still didn't recognize it. I have a midi track next to the audio track that Amplitude is on and all of that, and I can adjust all of the amp's knobs, but I just want the preset next and previous global parameters to map! Any help would be greatly appreciated, thanks

[auron]

Anyone out there with both Ableton & Amplitube 3 figure out a solution to this problem?

The latest version of Amplitube 3 (with the custom shop) seems to be more stable. A few notes:

Amplitube 3 in standalone mode
--------------------------
If you have a MIDI foot pedal (I have the fc-300) amplitube 3 will accept midi messages but only in stand-alone mode.
You CAN map to midi to change presets (next/previous).
Even though there is this new number bank for presets, sending program change messages hasn't worked for me. Anyone get that to work even in stand-alone mode?

Amplitube 3 within Ableton 8
------------------------
The AU has a history of being more stable, but the new VST works now and I haven't had a crash (yet).
If you want to control your stompboxes via MIDI, within Amplitube you have to use bypass and map the stompboxes, etc to a PARAM.
Then in Ableton, on the VST there is a little arrow that reveals the params. Map those params in ableton to your MIDI controller. You might have to invert the values to get the stomp box lighting up just like your foot controller, etc. but it works.

But the big issue is actually changing the presets via MIDI...from within Ableton.

On the VST there is a drop down list of "Programs" that are numbered and can be mapped to presets very easily.
You just choose a program number from the drop down, then go into the Amplitube window and select a preset. But that drop down menu does not correspond to MIDI "Program Change" messages NOR does it look like it can be mapped to a controller.

The hack solution is to have multiple instances of amplitube like mentioned in other posts where only one is turned on at any one time.

I also have a MPD32 and tried sending program change messages to amplitube which doesn't work.

What we are all trying to do is change Amplitube Presets from within Ableton using a MIDI controller without having to access the computer directly.

I wonder if IKM's foot controller able to do this within ableton?

[Gaetano CAPUANO]

bump anyone working this out?

[rd2rk]

I'm new to Ableton. Been using Sonar X1. In Sonar, Once you have Amplitube working with MIDI in standalone mode, you configure Amplitube as a SoftSynth, insert it in your Audio track, and use a MIDI track to send cc's to the Amplitube SoftSynth. Works great. Is there any way to do something similar in Ableton? BTW this also works with Guitar Rig.

[rd2rk]

To expand on my previous post. Works with PC's to change presets too. I'm using an FCB1010 thru an M-Audio Fast Track Pro to control stompbox on/off and presets, and a Korg NanoKontrol (separate MIDI track) to control amp/stompbox settings.

[dbmind]

Well, I have a FCB1010 and inserting a MIDI track (receiving the MIDI CC's from FCB and) sending signals to the guitar track has worked ALMOST like Amplitube 3 in Standalone mode. Although, preset change was messed.
I know it works cause I got it running well in REAPER. Presets were changed very fine, using MIDI learn function with CC's sending ONE value (of zero) from the specific pedal. But, I need to run Ableton instead of REAPER, in this scenery. That's my main core.

Maybe (of course) there's some different perception of CC's in Ableton and Amplitube. Still searching.

[rd2rk]

In Ableton, using a midi track to send midi messages to an audio track with at3 inserted. You need to send PC (program change) messages, not cc (control change) messages. In at3, load a preset, click midi,preset, and set the value in the "Program Change" box to whatever PC# your controller is sending. Save the preset, done! Repeat for other presets with different PC#'s. To step thru presets, you use the "Global" midi window and assign cc#'s for Next and Pevious. However, this will step thru the presets only in the category that you're currently in (for instance - /amplitube 3/amps/american vintage B/). There's a way to change categories by midi in Guitar Rig, but I haven't figured out how to do it in at3 yet.