It’s actually more common that you use CC messages to turn things on or off and Program Change to some other more global settings.
No and no. What MIDI messages are you sending from the FCB1010? Program Change or Control Change? You should be using Control Change if you want to use it to switch on/off effects. Program Change are meant to switch between pedalboards or snapshots.
Thanks a lot to your reply! I got a bit further…
I was definitely lacking some background knowledge.
Actually I had to understand first how to program the fcb1010 with the firmware 2.5 to send out cc messages. If someone else is coming across this topic and too lazy to read the manual those links were really helpful:
Now this works just fine as I expected. Then I thought “oh hey cool! Now lets use the Expression pedals on fcb1010 to control e.g. gain in the mod duo!” Unfortunately that does not seem to be that easy. I think I have to use the “Midi to CV” plugin and play around with that?
Snapshot changes and pedalboard changes will come next but as I understood they are set up in the system config?
Thanks for the help!
Cheers
Okay, what I said was wrong again. MIDI can be directly mapped to continious variables. However, the expression pedals from the fcb1010 needed propper calibration before.
You got it all 
even the answers for your questions.
I don’t own an FCB1010, but something that I heard/read a few times is that the expression pedals may be a bit weird with their calibration.
The FCB 1010 is surprisingly sturdy and really road worthy. But many users know that one needs to calibrate them very frequently, if it’s to be used in many different venues.
This is due to the fact that they do not rotate a potentiometer – like most pedals – but instead they have an acrylic plate that goes from transparent (so to speak) to full opaque, and that is interpreted by an optical device which then outputs the value. Therefore, if it’s too humid, too dry, too bright, too dark, if it’s daytime or nighttime (for open air gigs), if the current fluctuates too much, all of these will affect the light crossing that plate and readings will differ.
It is also known that as the FCB units age, this plate might get somewhat opaque due to dirt and it gets hard to reach the 0 value. (Users in coastal areas tend to have problems earlier on.)
That being said, they’re great units (I own a Uno-powered one) and can provide many years of good services. When the plates become too dirty, it is not hard to disassemble and clean them – though one has to be careful not to remove the paint of the dark area.
I’ve got my DuoX lately, and using FCB1010 was quite tricky. Stock FCB1010 has quite a limitation on sending CC messages. All I wanted - was to turn pedals on and off by pushing a FCB1010 footswitch. From the Mod Duo perspective - what is required is to send CC value 0 to disable something, and CC 127 to enable it (or to be exact, looks like you need to send value in range of 0-64 to disable or 65-127 to enable, not sure but it looks so)
However, FCB1010 has only two things to do with CCs:
Assign one CC with a fixed single value to the footswitch:
In this case you will need two footswitches to enable-disable virtual effect pedal in Duo, one to send value 0 and second to send value 127.
Using only one footswitch leads to enabling effect pedal forever and further taps do nothing.
Huge waste of the footswitches, not an option.
Assign two CCs (in the case - the same CC’s) with different values to the footswitch.
At first glance it looks like a solution to the problem - you assign the same CC with 127 and 0 values to the two settings fields, and FCB sends 127 on the first footswitch press and sends 0 on the second.
But actually there is a caveat - FCB keeps track only of the latest footswitch pressed. If you are willing to use only one footswitch on the FCB, you are fine.
But if you will press any other footswitch, it forgets that you already sent 127 on the previous footswitch, and next time if you press the first footswitch - it will send 127 again, and you will have to tap it twice to get 0. ( and it even does not feel consistent - you always need to remember which latest footswich had been tapped to understand what your tap will do)
Basically, if you will tap FS1, FS2, FS1 ,FS2, etc – you will allways get value 127 sent. You will be able to get effect pedal disabled only after tapping pedal twice.
This behavior became so irritating, that people sell custom UNO and EurekaPROM firmware chips that provides other behavior. I even tought that I will throw away all internal electronics to replace it with STM or Arduino chip, but looks like it is possible to solve it inside DuoX, in a quite ugly way.
My solution to this issue is to program FCB1010 to send notes instead, and do conversion to the CC insde of the Duo. FCB1010 at least does send note-on and note-off events, so it is something.
I doubt that [Edepopede] have not solved FCB issues since October, but maybe my examples could be useful for other stock FCB1010 owners that are struggling with this ancient relict as I was.
Here is a pedalboard (with beta plugin for MIDI monitoring) that shows how to get latching, momentary and inverted momentary CC signals out of the note-sending FCB using currently available MIDI plugins. It converts ranges of notes to ranges of CC’s, so with a tuned ranges it probably also can be used for keyboard of some sort as input, like, nanokey or something.
Thanks for sharing your solution! It is pretty cool
Yesterday I received my UNO2 chip, which should unleash the fcb1010 for quite some Midi applications, including stompboxmode. I just realized that I really need an external controler to really make more use of the capeabilities of the MOD Duo, which was worth to me to spend the extra 60 bucks for the chip. I will share some of my experiences here when I get to program it but there is at least one post that was quite promising for me. However, its in german language.
I have an FCB1010 with Uno-v1 chip that I haven’t really used ever.
Any suggestions on how to best use it with the MOD environment?
I managed to get the Uno editor working in wine, but I honestly find programming it so confusing.
Hey Dreamer, the FCB1010 is just like every other foot controller. It’s just a bunch of dumb buttons waiting to be told their purpose. Uno chip gives you stomp style toggle which the original never had.
What do you want it to do?
Maybe have patches on the bottom row and snapshots on the top?
Let me know, I’d be happy to guide or program. Don’t own one now but used one for years
My first inclination is to be able to turn effects on/off, but I’m not sure if that’s even possible with the “stomp style toggle” feature.
I don’t see a purpose to use program change messages, which afaik is the original function of the FCB1010.
I think off hand the top row can be configured for stompbox mode. Ie the toggle between 0-127 so you can turn fx etc on and off.
Maybe use the pc function for snapshots especially if you are using lots of stuff and changing parameters.
Best of both worlds then.
Maybe share a board that you want to control and we can see what we can do
Except I don’t use snapshots or have any purpose for them.
You’re saying I’d have to create separate snapshots that enable/disable specific effects? that sounds extremely tedious and not at all the workflow I am looking for.
Additionally I’m now having trouble getting FCBUnOControlCenter to work, so until then my device is useless anyway 
Ok so I finally have the editor working again (had to downgrade which wine version to use).
So this row of “stomp-box” buttons (can either be top or bottom row. unfortunately not both) can send out CC messages of 0 and 127 and those can (hopefully) be used to turn an effect on/off.
The other row will be unused since I really don’t want to use snapshots to control my effects (and would be totally confusing since a snapshot could turn certain effects on/off while the stomp-button has a different config).
I mainly find this FCBUnOControlCenter very confusing to use since it’s not clear from the UI how you are configuring any given button.
What’s also super weird is that when you click on one of the stompbox buttons the expression pedals change functionality.
So you have to make sure that under each setting you have the identical Expression Pedal settings otherwise they don’t work after enabling/disabling the button.
What do you mean with “did it”?
The video links in this post don’t give any information on how to use it with MOD.
I set the FCB1010 as a stombbox via the foot switches - see video - and then simply assigned in the Mod Duo X, all quite ~simple.
OK Dreamer try FCB1010 | Mountain Utilities
It’s another editor but like a spreadsheet that I used to use when I had one.
Expression pedals need to be set for each button if I remember correctly. Bit of a bind but cool for other things
Don’t forget PC can change the actually patches as well as snapshots
“No support for Ossandust’s ‘UnO’ firmware.” << as I mentioned I do have the UnO firmware.
But as I also mentioned I think I kind of have a row of “stompbox” switches now that should be able to turn effects on/off using CC messages.
It’s unfortunate that most of the device is rendered useless. It would’ve been way more useful if the UnO firmware allowed to have all the buttons as stomp-mode and if it would allow to have multiple pages of those.
I think this is what I originally had in mind when I got the FCB1010, but ultimately it’s much less useful then I’d hoped and I think I should probably just sell it since it’s just a heavy piece of not-very-useful gear.
Sorry didn’t see that. RIPWORX is another editor.
To be honest I don’t own the fcb anymore for a similar reason, plus mine used to buzz really annoyingly.
I did notice the UNO2 chip if you like programming but for me there are better things out there.
Maybe try line 6 FBV as the run midi on USB and have an easy editor
Don’t get a nektar pacer as its a similar frustration
You could always just make one using an arduino, tinsy or piZ? Gutting the fcb.
Plenty of options to consider