Timing hiccup with jumps in large sets

Support
1

I’ve been really digging in recently and trying to see how far AbleSet can take me. I’m working in a church environment where we have around 100 songs, from which we build a set of five-ish songs every week. I love the idea of how much time I can save building the set in Ableton every week by using AbleSet’s set-building capability. So I started playing around with multi-file projects, and just pointing AbleSet to our entire library of individual songs. But I didn’t love the time it took to load each song, and the lack flexibility in transitions when doing it this way.

So I decided to go all in and build a full master setlist project with of all of our songs. It’s a huge project, with more than 5,000 measures and maybe 180 tracks. Ableton remains pretty performant and I haven’t really had any slow-downs or crashes.

But one thing I’ve noticed is that if I build in automatic jumps or try to jump manually to certain song sections during playback, the downbeat of the section being jumped too arrives too early. It cuts the last beat of the previous measure short enough to be noticeable and I’m concerned this will throw the band off. It happens consistently every time. Is this just a limitation I’ll have to deal with when pushing AbleSet to its limits? Or is there anything I can do to try to remedy this?

Please fill out these values to make it easier to troubleshoot:

  • OS and Version: MacOS 15 Sequoia
  • Version of AbleSet: Stable 2.7.5 and Beta 3 (v4)
  • Version of Ableton Live: 12
2

Hey @JoshList,

This might be due to your project’s global quantization setting. When AbleSet tells Live to jump to a given locator, Live always respects the quantization, which might lead to unexpected jumping behavior if the global quantization isn’t set up correctly.

I’d suggest setting the global quantization to 1 bar first and check if that works. If it doesn’t, you can reduce it to 1/2 or 1/4, which should solve the issue.

Let me know if this works for you :slight_smile:

3

You’re a lifesaver, Leo! Global quantization was actually set to none. Must have accidentally hit the keyboard shortcut at some point and not even realized it. Never thought to check it. Setting it back to 1 measure solved it! This was a real headache this Sunday, so I’m happy to have the solution. Thank you!

4

I’m glad I could help!