Adjusting Locators Causing glitch?

Support
1

Describe your issue 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: macOS 15
  • Version of AbleSet: 3.0.11
  • Version of Ableton Live: Lastest version of 11

Hey all! take a look at the video below. I updated to the newest version of Ableset. I’m adjusting space between songs in our set right now and have come across bug where if I move the locator to cut down on a bar on lead in time ableset will glitch the end of that song leading into the one I adjusted the locator on for some reason.

It essentially jumps back to the beginning of the song that I just finished and then 2 seconds later finally jumps to the net song I just adjusted the locator on. Am I doing something wrong?

Let me know if theres any other context I can provide. Here’s what I’ve done so far:

Collect all and save - closed ableton and ableset and re-opened

Tried renaming the locator to STOP … when I did this it jumped right to the next song, but changing back to “SONGEND” reintroduces the previous bug.

VID: https://drive.google.com/file/d/1KdXzKsOwv84KsYKOL4bd1LD_AMaIfZqe/view?usp=drive_link

2

Hey @mattjvisuals,

Thanks for the detailed write-up and the video!

In your video, your set the locator is named SONGEND, but AbleSet expects it written as SONG END — with a space, all caps. That’s the exact name AbleSet looks for to mark the end of a song and jump to the next one.
Could you try renaming those to SONG END and let me know if that solves the issue?

You can also see this in action in the official tutorial.

If that doesn’t fix it, could you please create a Log Package?
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!

3

yes! Thanks for the reply. I’ll try this today and get back to you. Sent some logs over to support@ that may not be necessary now if I can reproduce the issue with SONG[space]END I’ll send another log package!

4

Hey! Just coming back to close the loop, it was the SPACE that solved this :melting_face: … “SONG END” instead of “SONGEND” … thanks for the help!

5

Heya, just signed up to report that i am experiencing the same issues to detrimental effect, and i’m currently on tour in Europe with a fairly large band and use Autostop rather than Song End, and also experiencing glitches. I dont know if this is a new bug or the same bug found otherwise, but i just had it die on me at a show.

In rehearsals it was immediately noticeable that Ableset had a hard time reacting to real time edits as markers were being adjusted often, leading to asynchronous files/markers between the A and B machines and therefore causing Ableset to bug out and not know what to start/stop. That part’s pretty obvious, and not a bug i dont think since Ableset is looking for the same thing. Anyway, i eliminated that variable by making sure to only ever have the same files and markers all the time, transferring files between computers and all the standard Playback and backup stuff.

But, that hasn’t really helped. Making too many edits to Clips themselves, whether it be Audio or MIDI, also seems to bug out Ableton and/or Ableset, causing erratic behavior such as songs misfiring (selecting Song A, hitting play and hearing the intro for Song F, for example), even when you make identical edits on both machines, like for example removing 1 bar from a MIDI clip or snipping off the last beat of a baked click track (real world example, happened today.)

Today, like i said i snipped off the last beat of an audio clip on A machine, did the identical edit on B machine, made my Ableset setlists, made it through line check just fine, saved it all, shut down, came back for sound check, everything worked fine. I’ve done this numerous shows with no issues. Start the set, all’s going well, and then suddenly halfway through the set hitting play on Song F fired off Song C, so i stopped, went to start of song, and got no response at all. Then in randomly played the intro to a third song. Band went on to play their next song without click and i restarted everything, and it came up with the same problems. Pulled the controller and manually spacebar’d the rest of the set.

Now, like i’ve said, i experienced this behavior in rehearsals with asynchronous files or marker placements, but that’s not what happened nor what i had. Same file, same edits, same locators, same everything.

Maybe it’s Ableton freaking out, idk, but it’s worth reporting

edit: specs 2x mbp m3’s running ableton 12.4 and mainstage, pa1u for midi on din & rtp, dadcore256 for audio. ipad mini for controller, previously was an older ipad.

6

Hey! Sorry to hear that man. I know the pain of playback issues live and I don’t think there’s a more stomache sinking feeling. First recommendation would be to edit your post or reply and add every single specific version / detail there…what 2 specific machines…what 2 specific versions of ableton … what 2 specific versions of Ableset. For me I was actually not using the correct spelling / spacing for “song end x songend” … doesn’t seem like that’s your issue tho. That fixed the marker move for me where Ableset wasn’t following my marker edits.

drop your specs here so Leo and his support team have that and can maybe jump in a little faster. Best of luck!

7

thx, i’ll edit. i definitely have them named the same, i ran into that issue early on and solved that one on my own haha. this may have been a fluke crash, but the consistency of ableton and/or ableton freaking out and erratically deciding what to play after multiple edits to songs is definitely not a fluke, it’s repeatable.

8

My gut tells me it’s something to do with the way you may be sharing over Ableton project files. I had this issue on a massive project for a cover band we ran redundant for. I think I remember it having to do with slight differences in the projects. After that even if I’m just nudging a tempo track a bar or two I’ll collect all and save…delete off B computer, and transfer the project over to B after every / any edit on A … I think you said you were doing that tho. Can you replicate the issue now? If you have the same sessions you can spin up?

9

yeah precisely what i’m doing. i consistently run into this issue when i edit on the fly, so my procedure is to always edit on A machine and remove B from the equation until i can collect all and save, and then replace the entire project folder on B machine after edits. In other words, the B machine’s files are constantly getting replaced with the A machine’s files so as to always run the same file.

that’s what is so baffling about this crash - i don’t have asynchronous files. the only single edit i made was exactly one bar of silence snipped on both, identically, to a single audio clip, which i have had to do on the fly a number of times and never had it die on me like that.

and there’s not much i can do to test until next show from a bus other than go through A line by line in the session to prep to dump to B when i see it next.