Describe the bug
i'm using a secondary midi controller to send commands CC10-13, perfectly emulating the onboard footswitches. unfortunately, this only works when MIDI thru is OFF. When it's on, the footswitches appear to respond to the commands, but they fail to send the Midi message onwards.
To Reproduce
Steps to reproduce the behavior:
Send midi CC10-13 to the BridgeX.
CC10-13 makes FS1-4 turn on, and send the midi messages programmed in, whatever the mode - toggle, momentary, sequential and tap tempo have all worked.
Go to the menu>global>midi>midi thru and turn on TRS in>TRS out
CC10-13 makes FS1-4 turn on, but the programmed the midi messages don't send, whatever the mode - toggle, momentary, sequential. Tap tempo does work.
Midi thru IS working as messages sent from another device are being received further down the midi chain.
Expected behavior
CC10-13 makes FS1-4 turn on, and send the midi messages programmed in, whatever the mode - toggle, momentary, sequential and tap tempo have all worked. Should work with or without MIDI thru.
Screenshots
check the videos I posted on the FB group yesterday and the day before.
Device:
Describe the bug i'm using a secondary midi controller to send commands CC10-13, perfectly emulating the onboard footswitches. unfortunately, this only works when MIDI thru is OFF. When it's on, the footswitches appear to respond to the commands, but they fail to send the Midi message onwards.
To Reproduce Steps to reproduce the behavior:
Expected behavior CC10-13 makes FS1-4 turn on, and send the midi messages programmed in, whatever the mode - toggle, momentary, sequential and tap tempo have all worked. Should work with or without MIDI thru.
Screenshots check the videos I posted on the FB group yesterday and the day before.