Setlist order keeps changing anytime I edit the timeline (duplicate or delete time) - also playback is jumping back to first song anytime a song locator is hit by the playhead playing before it

Support
1

Sorry if this has already been addressed, but I couldn’t find it on the forum. But having two weird issues here.

  1. Setlist order / songs that are visible or not keeps changing anytime I edit the timeline (duplicate or delete time). I’ve actually realized this has been happening for me for a long time I just never realized what was causing it. Is there some setting I am missing with my song locators that is causing this? no matter what I do, delete 1 bar or duplicate 1 or multiple, it seems to randomly mess with the song order and showing hidden songs.
  2. playback is jumping back to first song anytime a song locator is hit by the playhead playing before it. caveat, I’m working off of a session file built by someone else, and it appears that the new song locators I have added aren’t doing this. but yeah, almost every other locator will do this. basically if you cue it up and play, no problem, but if you happen to start playback before the locator, so the playhead hits it, it will jump to whatever is song 1 in ableset. I double checked, and it is only happening when ableset is running, so no other midi mapping or anything affecting it. I saw another topic saying it could be related to the max for live plug in, but I removed that and it still happened.

Thanks for any help on this! Also, just curious, I’ve seen quite a bit of fixes and stability with version 3, but it’s still in beta, is there an estimated approaching date for the official release? thanks so much!

  • OS and Version: MacOS Sequoia 15.7.2
  • Version of AbleSet: 2.7.5
  • Version of Ableton Live: 12.3.2
2

Hey Seth, thanks for the detailed message!

About the setlist order / hidden songs changing:

To look into this properly, could you please send us a Log Package to our support inbox?

If you’re able to include a short screen recording showing the issue while duplicating or deleting time, that would be super helpful as well.

You can create a log package by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package”.

Please make sure to also include the project files (no audio needed).

About playback jumping back to the first song when hitting a locator:

One thing to double-check is whether “Set Song Start Time Here” is set anywhere in the project. That option can override Live’s default playback starts at selection behavior.

As for AbleSet 3, there’s no official release date yet, but the latest beta includes quite a few fixes and improvements. If you’re up for it, it might be worth testing.

Let us know what you find, and feel free to send the logs when ready.

I’m looking forward to your reply!

3

Amazing! Thanks for the reply. Will get that stuff uploaded shortly!

1 Like
4

just uploaded the files, lmk if you need anything else from me! as you can see in the back half of the screen recording, I try launching songs by playing just before the locator, and its pretty inconsistent. certain songs will just always jump to song 1, but others will randomly jump to other songs. agian, there are some midi mappings on some of the locators (which I may be able to remove, im checking with the MD to see what he was using those for). But those don’t seem to be the issue because they aren’t mapped to any other functions, and this is only happening when ableset is running.

thanks agian for any help!

5

any update on this? still experiencing it every time I edit the timeline!

6

Hey @SETHBUILDSRIGS,

I haven’t had time to take a close look at this first issue yet, but I can give you an explanation for the 2nd one. The +JUMP locator in itself isn’t really a valid stop locator in AbleSet. It needs to be named STOP +JUMP (or SONG END if you don’t want playback to stop) for AbleSet to correctly detect it.

If a locator is just named +JUMP, AbleSet interprets it as a song locator in some cases, so if you start playback between a +JUMP locator and a new song, it thinks you’ve reached the end of a song and tries to jump to the next song in the setlist which isn’t possible since the +JUMP song isn’t part of the setlist. So it falls back to jumping to the first song in the setlist.

Renaming the locators should fix these unwanted jumps.

This behavior is improved in AbleSet 3, even with invalid +JUMP locators.

7

ahhh gotcha. I have always just done +JUMP to stop and cue up the next song, or SONG END to continue playback to the next song. So I just went through the session and any song that had +JUMP, I renamed to STOP+JUMP. and all of those are doing the correct behavior, but only SOME songs are still firing back to song 1 when I start playback just before the song locator. Thanks!