Playback stops when reaching a locator (“No next song”) even though shouldStop is false

Support
1

Hi,

I’m having an intermittent issue where AbleSet stops playback right as the playhead reaches a locator. I can’t reproduce it reliably, but I caught it in the logs.

Setup

  • AbleSet 3.0.11 (plugin 4.0.4)
  • Ableton Live 12.4.3
  • macOS 26.5.1 (Apple Silicon)
  • Relevant settings: autoJumpToNextSong = false, alwaysStopOnSongEnd = false, autoplay = false, jumpMode = quantized

Locators
I use plain locators only, with no locator notation at all: no > or >> sections, no STOP/AUTOSTOP, no SONG END, no leading dot, and no flags. The project has 12 locators (1, I2, VOZ, S, A, B, Plancha, C, Coda, TOMS ENAJENANTES, 2, BRASS), and AbleSet treats each one as a song. Since there are no stop locators and “Always Stop at the End of Songs” is off, I wouldn’t expect playback to stop at any of them.

What happened
In the logged occurrence, the playhead was before the first locator (beat ~188; the first locator, “1”, is at beat 192). When the playhead reached beat 192, AbleSet stopped playback:

01:15:05.288Z  Matched cue: "1" (lastSongTime 191.598)
01:15:05.289Z  Reached song end — shouldStop: false
01:15:05.289Z  No next song, stopping playback.
01:15:05.306Z  Queued song: "last-song"

The log says shouldStop is false, but playback still stops because no next song is found, even though the project has 11 more locators after that one. When I played again from beat 160 a few seconds later, it didn’t stop (“Resetting queued song because we started playback from its start”). So it seems to depend on some internal state, maybe how the current or next song is determined.

I’ve attached the full log file. The relevant lines are 222–228.

Thanks!
Patricio

2

Hey @patopretti, welcome to the forum!

When you don’t use SONG END or STOP locators, AbleSet treats the locator of the next song as the SONG END locator of the song that came before it. When the playhead reaches that locator, AbleSet jumps to the next song in the setlist, but if the previous song in your arrangement was the last song in the setlist, it stops playing.

To get the behavior you described, make sure that all songs are included in the setlist and that they follow the same order as the locators in your Live project.

If that doesn’t help, please send me a log package along with a screen recording of the issue so I can try to reproduce it on my end.

I’m looking forward to your reply! :slight_smile:

3

Hi, thanks for the quick reply!

I checked that: all songs are in the setlist, none are removed, and the setlist is in the same order as the locators (I never reordered it). The repro set doesn’t have any setlist changes at all.

The case is a bit different from the one you describe. It happens when playback starts before the first locator of the project. There’s no song before that locator in the arrangement, so there’s no “previous song”, but when the playhead reaches it, AbleSet still treats it as a song end and stops:

Matched cue: "Song 1"
Reached song end — shouldStop: false
No next song, stopping playback.

Steps with the repro set (three plain locators: Song 1 at bar 5, Song 2 at bar 13, Song 3 at bar 21):

  1. Put the playhead at bar 1 (before Song 1) and press play. Playback stops right before bar 5.
  2. To repeat it, click inside Song 2, go back to bar 1, and press play again.

It doesn’t happen every time. If the last cue AbleSet matched is already Song 1 (for example, right after playing through it), it skips the check and keeps playing, which is why it looked random to me at first.

This affects my real show sets: in some of them the first song starts at bar 5, with an intro or count-in before it. If I press play from bar 1, the show stops when the first song begins.

In case it helps: in the 3.0.11 bundle the previous song seems to be taken from parsedCues.grouped[E-1], which is undefined when the matched cue is the first one. So no next song is found and it stops.

As you asked, I’ve uploaded a screen recording of the repro and the log package through the support inbox. The log from that session is ableset-3.0.11-2026-10-12T19-58-55Z.log, and it shows all three attempts:

  • 20:00:01 play from bar 1 → 20:00:08 “No next song, stopping playback.”
  • 20:00:15 play from bar 1 again → no check, it keeps playing (I stopped it myself at 20:00:31)
  • 20:00:34 click inside Song 2, 20:00:38 play from bar 1 → 20:00:46 “No next song, stopping playback.”

Thanks!

4

Hey @patopretti, thank you for reporting this!

I just released a new beta version that fixes this issue. You can download it here: AbleSet 3.2.0-beta.13

Let me know if this fixes it for you, I’m looking forward to your feedback! :slight_smile: