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.