Hi,
I observed some strange behavior: I have sections flagged with +LOOP, so loop is automatically activated when reaching this section. Usually we manually deactivate loop when going to the next section.
However, when something goes wrong during the loop = we stop playback, manually jump to the next section, and restart playback again, loop brackets are not deactivated - despite I activated “disable loop when jumping” in the settings menu. Even more irritating: despite loop is activated (yellow button in ableton and indicator showing in ableset), it actually does not loop the next section but continues playing through the song. Is that intentional, or a bug?
Best,
Sebastian
Hey @Sebastian,
Thanks for the detailed description.
Let me break it into the two parts:
1. Why the loop isn’t disabled
“Disable Loop When Jumping” is designed to act on a jump that’s queued while you’re looping during playback: it escapes the loop so the queued jump can be executed instead of waiting for you to leave the loop manually.
In your case playback is already stopped when you jump, so there’s no active loop for the setting to escape. The loop bracket set by +LOOP simply stays where it was. That part is expected behavior.
You can see the setting explained here: Disable Loop When Jumping
2. Why the loop seems active but doesn’t loop
This is most likely the same root cause. The loop bracket might still be positioned around the section with the +LOOP flag, which might now be behind the playhead after you jumped forward. Live only wraps back to the loop start when the playhead reaches the end of the bracket from inside it — if you start playback past the bracket, it just plays straight through. So the loop button is lit (the loop is enabled globally), but the bracket might not be at your current position, which is why nothing loops.
The practical workaround is to turn the loop off and on again.
In case this doesn’t work on your end, could you please create a Log Package right after reproducing the issue?
You can create a log package by opening AbleSet’s icon tray, clicking the gear icon, and then selecting “Create Log Package”. Please make sure to include your project files as well (just the .als files, no audio needed). To send the files, you can upload them to AbleSet’s support inbox.
I’m looking forward to your reply!
Hi Agustin,
thanks, very helpful - I think that is exactly the behavior I am observing - very well explained. However, it is quite irritating for the majority of our band (and me until your explanation) that the loop indicator stays “on” even after leaving the loop bracket, so they are a bit nervous if this is some kind of malfunction, somebody accidentally hit loop or similar, even if it is simply expected behavior as you explained. Especially as we do not see the actual Ableton session in a live concert situation with the exact position of the loop bracket, but a canvas/ableset surface where we cannot see if we actually are within a active loop section, or if there is an active loop section before the actual playhead position which does not affect the subsequent playback.
Isn’t there a way to reset the loop indicator in Ableton and ableset in such cases to avoid irritation? Specifically when playing somewhere else outside of a loop bracket? First, to me me it seems impossible to decide if it is just what you explained, or really a malfunction or accidental hit of loop button in such situation. Furthermore, I cannot imagine a situation where it is useful to keep the loop indicator “on” even after leaving the active loop bracket. Or add an option into the settings “always deactivate loop when playing outside an loop section” or similar.
Following-up: I couldn’t reproduce this on my end.
Could you send a short screen recording of the whole sequence? Ideally showing both the Ableton arrangement and the AbleSet window at the same time, from the moment playback is running inside the looped section through to restarting playback on the next one. Seeing the exact order of your actions and the state of both windows should make it obvious what’s going on.
A log package with project files included would also help.
Also, what AbleSet version are you currently running?
Are your sections are defined via locators or a Sections track?
I’m looking forward to your reply!
Screen recording is uploaded, showing what I mean: If I leave the loop not by deactivating the loop, but by stopping playback and moving to the next section (e.g. some mistake by the band requiring restarting with the next section….), loop indicator stays on. Then it is quite unclear if this is just a loop indicator relating to a previous section but doing nothing right now, or if somebody accidentally hit the loop button. Had this a few times during shows in the past causing confusion. Only indication is the small bracket in the song progress bar, however, this is way to subtle to be clear in the live context. My suggestion would be to implement an option in the setting menu: “always deactivate loop when playhead is outside a loop section”.
Ableset 3.1.4, Ableton 12.4.3
Hey @Sebastian,
Thanks for confirming the exact steps and versions.
The recording doesn’t seem to have come through on the forum post.
Could you try attaching it directly here again?
I’m looking forward to your reply!
Hey, I’ve uploaded the screen recording to the ableset jumpshare cloud.
Hey @Sebastian,
It looks like you’re using an older version of the loop button. Under the hood, it uses /setlist/loopEnabled to check if you’re in a loop which can be incorrect. The newer version uses /setlist/isInActiveLoop which is only true if the playhead is actually inside of the enabled loop bracket.
Could you try either changing the used OSC value in the dynamic color or deleting and re-adding the loop button so it uses the newer version?
Let me know if this fixes it for you!
as always - genius 
. That’s exactly what I missed - works like a charm!