Hi! We have been using ablest for the past few months and have been really liking it. Recently, there have been a few times where while another song is playing the playhead will jump back to the first song in the setlist. I’ve looked all over the forums and tried to inspect the logs myself and it seems to be that ablset thinks it has reached the end of the song even though there is no end of song marker or break in the Sections track. (Timestamp right around 2025-08-26T22:22:34.845Z)
I’m hoping I have just missed something and its an easy fix.
Quick update on this, I have run this particular transition between songs about 50 times and this jump to the beginning of the setlist thing has happened twice in those 50 runs. Both times there is a log message “Time in song is below 0”
If anyone has any advice on what to do to avoid this it would be much appreciated. Thanks!
Hey @Braedenmccann, thank you for reporting this issue! I have a hunch about what might be causing this and will try to reproduce the issue on my end.
To help with troubleshooting, could you email or upload your project file and let me know which song this happens with? Just the .als file should suffice for this.
My hunch is that this is caused by an inconsistency with the Max for Live device. Interestingly, the playhead position reported by Max for Live isn’t always 100% accurate and can deviate from the actual playhead position by around 0.0002 beats. I’m already trying to mitigate this by adding safety margins, but it seems this isn’t working right in some cases.
To confirm my suspicion, could you try removing all instances of the AbleSet Max for Live device from your project and running the song transition a few times again?
I will try this and get back to you. The full ableset log
Package with the ALS session is already in your support inbox.
What I have done to get it to behave more reliably for the last few shows is to load the first few bars of all clips after the jump into ram. There seems to be a disk access issue with the 2500 bar jump at that point in the setlist. After that change I was able to run that transition upwards of 50 times without any jumps back to the top of the setlist.
I’ll let you know if removing the M4L device changes anything.
Thanks!
The transition in question is from rise up to let the church sing. This session does have the first clips of let the church sing loaded into ram but that probably won’t matter to you as you don’t have the samples.
I’m sorry to hear that you’re running into the same issue as the OP. To troubleshoot this, could you send me a log package including your project file? You can create one by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package”.
You can also include a video of the issue on your machine if you like, that often makes it easier to troubleshoot.
If the files are too large to send via email, you can upload them to my support inbox instead.
Hey @leolabs, thank you! I’m loving the app so far, i downloaded the newest beta and the issue seemed to disappear at least. I send the files requested to the support inbox. Hope it makes it easier to find!
I just took a look at it and it seems that your songs are very close to each other. This can trigger a bug in AbleSet 2 where it thinks you just finished an unknown song and jumps to the first song in the setlist afterwards.
This can be easily fixed by adding a few bars (1 or 2 should suffice) between each SONG END locator and the start locator of the next song.
AbleSet 3 doesn’t do this anymore, but it’s still advisable to add a bit of space between your songs to avoid the playhead accidentally going into the next song on the timeline due to global quantization.
