If the switches work correctly in the standalone version, they will work exactly the same way in a DAW if the signals are getting to the plugin, unless there are MIDI filters being applied. Again IIRC

First - use a MIDI Monitor to make sure that the FCB is actually sending MIDI and that your computer is actually receiving it. If you've recently performed a Factory Reset on the FCB It should be send

Thanks. Maybe OP's FCB has bad LEDs.

uno@fcb1010.groups.io | Files EJ's UNO2/Amplitube.txt "Instructions for Amplitube UNO2" briefly describes the configuration.

I assume that you mean when you press pedal 10 to enter what I called "Stompbox Mode". The configuration I posted has 9 toggling CC switches. It's not at all like my regular UNO Amplitube configuratio

Or you can right click the object (knob,switch etc) that you want to assign and select LEARN from there.

It's a good idea to create a new "Category" for your modified/custom Presets. I call mine "My Presets" because I'm such a creative guy :-) . There's two ways to limit the range when using an expressio

As mentioned previously, spend the $25 for UNO_ControlCenter and read the manual. FCB/UnO Control Center for the Behringer FCB1010 I'm going to be brutally honest here. Once upon a time, computer amp

UNO sysex attached. Set AT to receive on MIDI Channel 1. The main difference between GR and AT is that by default, AT reverses the standard MIDI Toggling CC Values from 0=OFF/127=ON to 127=ON/0=OFF.

If all you need to do is call presets and use the expression pedals, the Factory defaults should work. Set GR5 to receive MIDI on Channel 1. You need a MIDI Monitor to verify that the FCB is sending t

The order of command execution is PC1-PC4; CNT1-CNT2; PC5; NOTE So if: CNT1 = 0 with a Value of 2 AND PC5 = 25 Then the result should be Bank 3 Preset 25 NOTE: Some devices prefer CC# 32 vs CC# 0 for

My point is that it doesn't matter what Mainstage wants if you don't know what you're sending. At least get a MIDI Monitor so you can know that. IIRC from another thread, Mainstage maps incoming MIDI

Though I can't really help you much with Mainstage (PC guy), the stock FCB typically sends PC#s 0-99. It can send whatever PC#s you configure it to send (any 100 between 0-127), but if you haven't rep

My point is that there's nothing us common users can do about it, they don't accept PC messages. At least, none of the ones I use do. The publishers of the SW that I use all seem to include VST3 just

FWIW - I DL'd the trial of FL Studio. It automatically picked up my MIO Interface and I was able to map to the native plugins without any problem. Unfortunately, the trial is not full function in that

Sorry, can't attach those files. Look in the FILES section.

Did you do the Factory Reset? Did you install an editor? IIRC (it's been a LONG time since I had an FCB with the stock chip) the Factory Reset assigns each button a PC# from 0-99. The editor will allo

I found mine (I had it connected to a MIDI Keyboard). The IN light means that it's passing MIDI from your controller (FCB) to the USB connection. The OUT light means it's passing MIDI from USB to the

Is the MIDI Monitor showing that it's receiving? WHAT is it receiving?

Assuming that the cables are correctly connected, the MIDI light should flash when MIDI is actually being sent.