Sorry I know I must be known in the ‘office’ now as the guy who gives effusive praise on half the beta updates but you’ve actually solved the biggest problem in the Ableton playback sphere. I’m not joking. The disk dropouts bug has absolutely killed me at points and caused me huge headaches.
Granted I’m using this without an interface plugged in but RAM loading/de-loading works, and I’m not seeing any meaningful spike in CPU usage on 256 samples.
Bravo!!
EDIT: The one thing I have noticed, is if you pause mid-song and then unpause, it’ll restart the song. But adding a locator with +PAUSE still works fine.
Subject: Bug Report (v3.2.0-beta.16/17): Unable to manually override +SKIP on final song sections
Hi Leo,
I’ve been testing Version 3.2.0 beta 16 on a gig tonight—love the new features, setlist updates, and canvas capabilities!
However, I ran into a critical issue on stage regarding the +SKIP tag behavior:
Middle of a song: If a section has a +SKIP tag and I manually click/select it mid-song to override the skip, it works as expected.
End of a song (Last section): If +SKIP is enabled on the final section of a song (intended to jump to the next song), AbleSet will not let me manually select/click that end section to override the skip while playback is running.
Steps & Workarounds Tested:
Rolling back to v3.1.9 restores normal manual override behavior on end sections.
However, because my setlist canvas relies on new v3.2.0 features, I have to stay on the beta for my current rig setup.
Since overriding an end-of-song skip on the fly is essential during live performances when reading the crowd, could you please look into this selection lock on end sections for an upcoming beta build?
Thanks for all the constant updates and hard work!
Thank you for reporting this issue! I just tried to reproduce it on my end but haven’t been able to get the same behavior. Could you send me a log package including your project file so I can take a closer look at it?
You can also include a screen recording of the issue if you like, that often helps with troubleshooting. You can upload everything to my support inbox.
I think I found the issue. When a section is marked as a loop, there’s an element that displays the loop bracket for the section but blocks the mouse from clicking it. I’ll release a fix with the next version.
In the meantime, adding the following lines to your Custom Styles should be a good workaround: