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: (e.g. macOS Ventura 13.3)
- Version of AbleSet: (e.g. 2.2.3)
- Version of Ableton Live: (e.g. 11.3.3)
Hi there,
Had an issue utilizing the Jump Ahead function for sections. Twice now, i have experienced the Jump Ahead function randomnly glitch and not jump smoothly, thus getting the entire band off time – wondering if it is a bug?
Love this feature but will probably stop utilizing it until fixed. Apologies for not filling out the values to troubleshoot. My band laptop is not with me at the moment but i believe i am up to date on all versions necessary
Hey @totpband,
Thank you for reporting this.
Once you have the band laptop with you, could you let me know which jump mode you’re using and what Live’s global quantization is set to?
It would also help to know how you trigger the jump (tapping the section, a MIDI controller, OSC, etc.), whether it’s a single or multi file project, and what exactly happened when it glitched.
I’m looking forward to your reply!
Hi there!
Here are all the specs:
macOS Monterey 12.7.6
Ableset 3.1.1
Ableton 12.2.7
Global Quantization is 1/4
Triggering via sections ( “Intro >>> Verse” ). skipping a section labeled Big Intro. attached a screenshot below!
It’s not every time, and i am not sure how to recreate it, but it has happened twice during a live show at the exact same spot + behaving the exact same way. it jumps to the proper section but it almost “hiccups” by a beat or so (for lack of better analogy) thus getting the rest of the band off time.
Hey @totpband, thank you for elaborating! This issue was fixed in AbleSet 3.1.5, could you try updating to the latest version and checking if that fixes it for you as well?
I’m looking forward to your reply! 
Hi! thank you for the info – could you clarify what the issue was / how it was fixed?
appreciate the elaboration for my own piece of mind in ensuring this won’t randomly happen again at future shows!
There was an issue that caused AbleSet to think the playhead was still at the end of the previous section after the jump, so it triggered the same locator jump again a 2nd time.
got it! thank you so much for the insight!