Hi all,

Brand new here and attempting to get my FCB-UnO up and running with Amplitube 5. Any suggestions would be extremely helpful as I am very new to this sort of thing. 

I purchased the FCB/UnO Control Center and have so far only gotten through the preliminary steps outlined in the manual, to determine that my  FCB1010 is communicating with the editor properly - which it is. It says that I have UnO v.1.0.4 installed on the unit, and "Patchdump successfully received" in the status bar. 

To connect the FCB1010 to my PC, I'm going through a Behringer U-Phoria UMC404HD interface which has midi in and out. 

I have also downloaded Ej Sheldon's sysex file for Amplitube started going through his steps as outlined in a previous post about Amplitube, and did not get very far at all. When I open AT5 in standalone mode and try his instructions for MIDI-Learn, I noticed that AT5 is not recognizing any midi data from the FCB1010 whatsoever. So when I highlight "Preset Next" and click "Learn" in AT5, then press pedal 10 on the FCB - it just says "Waiting for midi input..." and nothing happens. 

I then tried to get a midi input signal with the unit in Ableton, Maschine and finally MidiView just to see if any midi signal is going through at all, and I'm getting nothing. Which seems strange, considering that the FCB is being recognized in the FCB/UnO Control Center but seemingly nowhere else. 

I imagine its probably something very simple I'm just not thinking of - but again I am completely new to midi foot controllers and this is my first attempt to get one going. 

So I suppose this is really 2 questions - A) does anyone have suggestions for getting my FCB1010 recognized in Amplitube 5, and B) can anyone direct me to some simple steps to program my FCB-UnO for use in Amplitube 5? 

The post i mentioned of EJ Sheldon's is from 2019 and for use in Amplitube 4, so just wondering if there is some updated instructions somewhere for AT5. 

Thanks a ton for reading this lengthy first post! 

In ControlCenter, upload the contents of the FCB and verify that it's actually there. It sounds like that's your main problem. You should probably read the very excellent ControlCenter manual. There's a MIDI MONITOR window in ControlCenter at the lower right when you click GLOBAL CONFIGURATION. That will tell you exactly what is coming from the FCB.

At various times I've used both MIDI Channel 1 and 2. Make sure that the Channel I used in that version matches the MIDI Channel in Amplitube.
Amplitube default is Channel 1. EDIT: My bad, it's OMNI, so it should work regardless which version of my sysex you have.

In Amplitube's Audio/MIDI setup dialog screen be sure that you've selected the Behringer's MIDI Driver at the bottom of the dialog.

The file for AT4 works fine with AT5, nothing has changed in Amplitube where MIDI is concerned except for them making it more of a PITA by eliminating the "pedalboard" slot bypass Global Assigns, and if there's a way to bypass what were formerly called their "RACK" FX, I haven't found it. Stupid. Also, it's still a major resource hog, so don't be surprised if you have trouble getting the sample rate (determines latency) down lower than 128 samples without glitches. More stupid. Some of the many reasons I no longer waste my time with Amplitube. Wish I hadn't wasted my money on it, the MAX version, no less! Oh well, new, shiny things, GAS.

It does SOUND good though!

Hi,

Sorry, can't help with iOS. I tried Amplitube, BIAS, and some other sims, they all sounded terrible, not at all like their desktop versions.
I think that iOS just doesn't have what it takes to run amp sims.

You could try the Positive Grid Forum:

Home | Positive Grid Community Forum

And the IK Forum:

IK Multimedia • Index page

For help with MIDI on their iOS versions.

Thanks so much for the response @ejsheldon, much appreciated. As I mentioned, my FCB does seem to be recognized by the Control Center - it says "Patchdump successfully received" after I upload it from the FCB. It also shows "FCB_UNO (v.1.0.4) at the top, after clicking the big midi button. But curiously, in the MIDI IN Monitor window - nothing shows there when i press on the FCB pedals. I have also tried this using my Maschine MK3 as the midi interface, in case there was some issue with my U-phoria interface - same results. I use V Drums which connects via midi and this works totally fine, instantly recognized on my PC.  I will continue to try all of the troubleshooting I can think of, but I'm currently stumped!

If the contents of the FCB were received by ControlCenter, when you click on the white square icon between the logo and the display window, you should see the attached screenshot. If the entries are blank, it means that your last Factory reset succeeded, but you haven't succeeded in loading my sysex to the FCB. Open the AT4 -UNO NEW wPrev-Next.lgp file and click the icon circled in red. That should load the file into the FCB.

Ahh, yes! I knew it was something fairly simple my newbie eyes just couldn't see lol. Amazing, thank you so very much EJ - I'm going to go through the rest of your programming instructions now and see how it goes 🤞🏼

So I was able to program everything from PRESET NEXT down to TUNER, but I don't see "STOMP A Slot 1 Bypass" or any of the Stomp Slots to program in AT5

"So I was able to program everything from PRESET NEXT down to TUNER, but I don't see "STOMP A Slot 1 Bypass" or any of the Stomp Slots to program in AT5"

That's what I was talking about here:

"The file for AT4 works fine with AT5, nothing has changed in Amplitube where MIDI is concerned except for them making it more of a PITA by eliminating the "pedalboard" slot bypass Global Assigns".

When Amplitube first came out, it had a decent MIDI implementation. Not NEARLY as comprehensive as Guitar Rig, but decent for the time.
Instead of improving on it, successive updates have actually made it more of a PITA to use. Meanwhile, amp sims like THU have improved on their MIDI control.
Unfortunately, my attempts to communicate with the IK developers about this have consistently been ignored, so I have to conclude that they don't give a rat's patootie about MIDI. 

But it SOUNDS good! :-)

Ah ok I see, so by pain in the ass, do you mean I'm simply not able to switch AT5 pedals off and on with the FCB? And that I'm limited to just switching through presets and using the expression pedals? 

What I'm also finding after doing this programming, is that after I place a Wah or Volume pedal in the chain and try the expression pedals - the entire chain gets immediately reset back to an empty pedalboard. I haven't been able to see the wah or volume pedals moving in AT5 as I operate the expression pedals on the FCB. Not sure what I'm doing wrong.

What it means is that you can't assign GLOBAL bypass to specific SLOTS in the pedalboard (before the amp) section.
You CAN assign BYPASS to specific effects on a PER PRESET basis.

"What I'm also finding after doing this programming, is that after I place a Wah or Volume pedal in the chain and try the expression pedals - the entire chain gets immediately reset back to an empty pedalboard and the Amplitube amp you see when starting with a brand new file. I haven't been able to see the wah or volume pedals moving in AT5 as I operate the expression pedals on the FCB. Not sure what I'm doing wrong."

Not sure what you mean. What EXACTLY (according to the ControlCenter MIDI Monitor) is being sent by the Expression pedal?

In order for the WAH to work:
The GLOBAL WAH BYPASS does NOTHING. Don't know why it's still there. Oversight?
The WAH selected must have a two-position ON/OFF switch (DIME works). Those with ON/AUTO/OFF will not work (plain old WAH does NOT work).
You first ASSIGN MIDI to the ON/OFF. Since the FCB does not have a TOE SWITCH, you need to use one of your 5 STOMPS for this.
The following selection process might appear anywhere on the screen, and is VERY difficult to see. More stupid.
Right Click the ON/OFF switch and select ASSIGN MIDI>BYPASS>LEARN BYPASS. Press the Stomp you want to use.
With the WAH ON, ASSIGN MIDI to the treadle using the Exp Pedal.
Right Click the treadle and select ASSIGN MIDI>WAH>LEARN WAH. Operate the Exp Pedal.
SAVE THE PRESET!

Ok, got the DIME Wah working! But next I tried a volume pedal - in this case the Fender Wah. It does Midi Learn just fine, but when I go to use it and rock the pedal to the top setting (at 127) - all pedals in the chain vanish and the pedalboard is completely reset to empty. This is what's happening in the MIDI IN Monitor:

Are you using a PRESET switch or a STOMP switch?

Upload the contents of your FCB to ControlCenter. Save it as echosoup. Attach it to your reply.

I'm using a STOMP switch when Midi-learning the on/off switch for the volume pedal. Then using the Exp pedal to Midi-learn the treadle. Here are the contents of my FCB

Somehow or other you got ahold of the sysex I made for use with Helix (CC#69 selects snapshots).
Probably my fault, I've used this file as the basis for so many variations over the years, I really should weed out that directory!
Try this one.

I don't know why the procedure should work with one wah and not the other, but if you follow the same procedure you used for the DIME wah, it should also work for any other wah with a two position ON/OFF switch. All along I've been unable to duplicate the problem you're describing, so hope this fixes it.

Ah, this sysex fixed the problem and I can now program the Volume / Exp Pedal as well without issue. Amazing, thank you so much! I suddenly have hope for using my FCB and finally having some fun with it! 

I imagine this will be a whole other can of worms to utilize this set up (FCB + Amplitube) within Ableton 11? 😬

In Ableton you need to set up a MIDI track that receives from the Behringer and sends to the Amplitube Audio track.
Track record needs to be on for the MIDI track.
Be sure to use the VST2 version (NOT VST3) if you want to call presets with the FCB.
In PREFERENCES, mio is my MIDI interface. Yours will be whatever the Behringer calls itself.
The attached screenshot shows the complete setup. I had to use AT4 because, resource hog that it is, AT5 won't even load on this computer.

Just got it working in Ableton!! I can't thank you enough for this good sir. I really appreciate your time and expertise, I see you've helped many on this forum and that is amazing. Props to EJ!

De nada! Rock on!