Unfortunately one or both of the commands themselves are likely corrupted
It could even potentially be the mode!
This was an unfortunate case for some commands/modes made in very early versions or that were downloaded from the online library before we updated to 1.6.x (we deleted all existing shared content to avoid this from happening as often)
My first suggestion is to delete the commands from the button and your device and recreate the commands from scratch using the new 1.6.x app version available in the app store.
If that doesn’t work try remaking the mode from scratch, this would be rare to happen it is usually a command issue.
Hi, thanks so much for the reply. I’ll try and recreate the commands and see if that does the trick. For what it’s worth tho, I have only been using the pedal and software for a week or two, so I am on the latest version already, have my firmware up to date, and have not downloaded any commands (only created my own from scratch. I’ll let you know how it goes once I try recreating them.
Since I had originally posted here, I ended up finding a better way to achieve what I was looking to do without using the “on release” functionality, so it’s not really too critical, but I’m curious to see if I can get it working in case it ends up being something that will be useful in the future.
Hi, I’ve tried creating new modes and commands, and unless my understanding of how it is supposed to work is incorrect, “on release” straight up doesn’t work.
Is my understanding correct that in the screenshot attached, the maestro should send 2 commands on press of the footswitch, and then the same 2 on release? It sends the first 2 commands without a problem, but nothing happens on release. This is a brand new mode, brand new presets, latest firmware etc etc
On release still doesn’t work. It’s the same commands that are being sent as on press, and that works, so it’s not an issue with a bad command or a wrong channel. It’s just not working as I think it’s designed to. Let me know if I’m doing something wrong or if there is a known bug or if I possibly have a faulty unit.