When I press a MIDI mapped button on my input device, the command executed two times. For example, when I press a button mapped to “Prev. Song” it will jump to 2 songs earlier instead of only jump back 1 song.
The same happens for “Next. Song”, “Prev. Section”, “Next. Section”
Seems to me when I press down the hardware button on my device, it generates a MIDI ON which triggers the first action, and then when I release it a MIDI OFF is generated which triggers the command again.
I am using the latest Live Suite 12.1.1 and AbleSet 2.7.4 on MacOS 12
In the above case, even if my MIDI controller sends a 127 value upon release, AbleSet will only respond to Value 0 (the initial press). You’ll need to work out what MIDI message you want AbleSet to respond to, using MIDI Monitor, then set it as such in AbleSet’s settings.
I have tried various ways. However, what I found out is that the hardware “Go Box” that I am using can only generate resembles hardware keyboard pressing “C-1”, “C#-1” etc. Hence, only MIDI ON (when pressed) and MIDI OFF (when released).
AbleSet translates these as 2 different commands even though the button was only pressed once.
I have another device that can generate MIDI CC, which works fine when I only map the “Value 0” as suggested above.
Can we only process the “MIDI ON” message in AbleSet?
Ableton Live itself doesn’t seem to have the same problem with this hardware
I have a hunch about what might be causing this. I recently discovered that there are two ways of sending a MIDI OFF message: an actual MIDI OFF or a MIDI ON with a velocity of 0. Your “Go Box” likely sends the latter.
AbleSet currently only supports MIDI OFF messages, but it should be fairly simple to add support for MIDI ON with 0 velocity. I’ll keep you posted
