I have a MIDI Controller Footswitch that sends MIDI CC with a Value of 127 each time is pressed and it’s ‘momentary’. While I can map it in learn mode, because it sends only 127 it remains engaged in MG3.
I saw the options are INVERT and LATCH or - is there a forced MOMENTARY so that next time a 127 is received on the same CC and MIDI Channel the button is disengaged?
Thanks a lot
Pasha
There are three input modes for any controller
1 (-) Standard (unaltered) functionality
2. (INVERT) for foot controller polarity switch etc.
3. (LATCH) Is for giving momentary controllers like yours an on & off state usage
I would guess that LATCH mode is what you describe here! 
Thanks for reply!
Well… the LATCH mode in MG3 works perfectly when I map the sustain pedal of my M-AUDIO keyboard. However, when I use MIDI COMMANDER (from Meloaudio company now retired from MIDI business) I can program toggle or non toggle mode. When the footswitch has been programmed in toggle mode and MG3 is in - STANDARD mode all works fine. When the switch is programmed as toggle off… it does not, whatever state MG3 is… including LATCH.
I think it’s a quirk in MIDI COMMANDER, just only trying to figure out.
I installed a MIDI Monitor to check what’s going on.
It was CC 34 (Breath controller fine) … so I reprogrammed the footswitch to send CC82 (toggle OFF) - Same result, no matter what. MIDI channel is 5. I assume that MG3 listens to all channels.
By testing different modes of MIDI COMMANDER I observed that toggle ON in Custom mode (user programmable) acts differently than toggle ON in other preprogrammed Read only Modes. MG3 ‘feels’ something is different and shows strange behavior (press three times to disengage a button in STANDARD mode) but that’s all within MIDI COMMANDER. Other modes are a mix of BANK PGC and CC toggles. Debug goes on…
Ciao
Pasha
PS : Do not loose time on this: MIDI COMMANDER is no more so do not loose time fixing unless it’s useful for other controllers.
I actually experienced a similar problem with an XTONE pedal. And now I finally ordered a good old FCB1010 here because I heard it’s even more bizarre.
I have previously made some work on making customer controller mappings, but never quite finished it. It’s able to actually draw a visual reproduction of your controller in the patch bay and each button you define can be scripted with Lua. Its not high priority right now, but will eventually arrive at some point.
MIDI COMMANDER has been implemented with DPDT Latch footswitches and with a software that reads the state (Toggle ON) or treats it as momentary (Toggle OFF).
I have a real momentary switch I’ll use into an Arduino project and I know the physical implementation is different… the Midi Commander ones emit a big ‘click’ sound…when pressed, the DPDT momentary one not, only a springy sound, close to silent.
So it’s all in the firmware… Midi Commander was originally intended for AXE, KEMPER and many other guitar pedals to switch FX on / off and relay on the device to interpret and route the CCs. Here’s why preprogrammed modes have toggle ON and BANK/PATCH mixed as well as a LED for each footswitch (that doesn’t light up when Toggle is OFF). Custom Modes were implemented for users with different needs. Close to their ‘out of Business’ they released two FW so that a preprogrammed mode sports ALL CCs with or without Toggles. Unfortunately only Custom Modes allow to mix footswitch with toggle ON or OFF…
It’s up to me now to find a proper setup… or to build myself an MG3 controller 
Sorry as this last post was so out of topic.