I noticed an issue while using Ableset.
When Song End jumps to the next track, if the next song switches from 6/8 back to 4/4, Ableset sometimes runs one or two extra beats before jumping.
This makes the transition unable to land cleanly on the downbeat.
That’s strange indeed!
Before diving deeper, I’d like to rule out a couple of things first.
In the sessions where this occurs, could you check whether each song has an explicit time signature change at its very beginning, regardless of whether it’s 4/4, 6/8, or even if multiple consecutive songs share the same time signature?
It’s important that there’s a Time Signature Change at the start locator on every song so AbleSet and Live stay perfectly in sync when jumping.
If that’s already set up and the extra beats still happen, could you please create a log package so we can take a closer look?
To generate it:
AbleSet → Settings → Create Log Package
You can then send it through our support inbox here.
Hey @L_Lin, please excuse my late reply on this. I’ve taken a look at the project file and noticed a few things that might have caused this late jump. Generally, these issues are caused by Live’s global quantization system. AbleSet just instructs Live to jump to the next song a few milliseconds before reaching the end of a song.
First, the song “VN TRANSITION 2” song starts between two bars. I’d recommend adding a time signature change to the beginning of the song to ensure it starts on a bar:
And third, I’d recommend making sure that there are no section clips between songs, which might confuse AbleSet in some scenarios.
With these changes in place, I was able to increase the global quantization of your project to 1 Bar without having the playhead overshooting the end of the transition song.
I hope this helps. Let me know if it solves the issue on your end as well!
I tested it again following your suggestions, but unfortunately the issue is still not fully resolved on my end.
It might be necessary to ask you to test it further on your side if possible.
For now, I’ve already implemented an alternative workaround so the show can proceed, but I’d still really appreciate your help in investigating this further.