Description:
I’m seeing what appears to be inconsistent behavior between the AbleSet UI and MIDI mappings.
Setup:
-
AbleSet 3 (latest version)
-
Ableton Live 12
-
Jump Mode: End of Section
-
AKAI LPD8 mk2 connected through a PlayAudio 1U (via USB Host)
-
LPD8 is routed to HST 1 in Auracle X.
-
AbleSet Control Surface Input is set to HST 1.
-
MIDI mapping works correctly and AbleSet receives the controller input.
Expected behavior:
When I trigger Next Section, AbleSet should wait until the end of the current section because Jump Mode is set to End of Section.
Actual behavior:
-
Clicking Next Section in the AbleSet interface works correctly and waits until the end of the section.
-
Triggering the exact same “Next Section” command from a MIDI controller causes the jump to occur at the next bar instead of the end of the section.
The MIDI mapping is definitely reaching AbleSet because the Next Section button in the interface responds when I press the controller.
So the only difference is the source of the command:
-
Mouse click → waits until end of section

-
MIDI mapping → jumps at next bar

Is this expected behavior, or is it a bug?here:
The more information you include, the better. If you like, you can also attach images or videos.
Please fill out these values to make it easier to troubleshoot:
- OS and Version: (e.g. macOS Ventura 13.3)
- Version of AbleSet: (e.g. 2.2.3)
- Version of Ableton Live: (e.g. 11.3.3)