Closed frenno closed 1 year ago
This is a Bridge6 config file with all steps to 3a (Github doesn't let me attach JSON so you'll have to rename the extension)
addressed with v1.1.3
Unfortunately this doesn't seem to be fully addressed in 1.1.3, I tested using the same steps as above plus a couple of other variants.
As far as I can tell, the firmware upgrade was successful (no error messages and the System info shows 1.1.3). I tried doing a factory reset as well but that didn't change anything.
Hmm ok, so it seems that the issue is separate with Go To Bank messages. I had only tested bank up/down, so I'll take another swing at this tomorrow.
Hi @samspencer5991, currently using firmware 1.2.0-alpha.5 and still seeing all the same results as in my previous comment (which was using 1.1.3).
Device:
Describe the bug When using Go To Bank smart message, switch states are not reset when entering a new bank, so the same footswitch in the new bank is activated (including associated message stacks/LEDs).
To Reproduce Steps to reproduce the behavior:
Start with a blank template and Bank Change PC messages turned off to eliminate any messages not set up below.
On Bank0/FS1, add the following messages to the specified stacks:
(a). On Bank1/FS1, add a Toggle On message Go To Bank 0
(a). Navigate to Bank 1 on the device and tap FS1
Expected behavior When a footswitch with a Go To Bank message is pressed, the device should change to that bank and not do anything else. Any input from that footswitch should be ignored until after it is released (and then honoured for subsequent presses).
Screenshots In the screenshot (of the Protokol MIDI monitor), I added a marker in between a/b/c versions. You can see that the different message stacks are triggered depending on Bank Jump times relative to switch press/release/hold.
Additional context