Getting some weird behavior recently from the MIDI section for +PAUSE. There’s been no change to the Ableton files, and I feel like it started around the last AbleSet update, but can’t be sure on that.
Quick context: on each Ableton file, I have one measure play, and a +PAUSE command on measure 2 - and the normal behavior is the playback pauses at 2, we hit play, and the playback resumes.
Now, however, it is inconsistently acting differently. Sometimes, and I haven’t found a pattern yet, the playback will pause just before measure 2 (at least visually) and when pressing play, the song restarts at measure 1. So, we end up with a repeating loop of measure 1 to 2 when hitting play. To complicate things, it will sometimes correct after a random number of loops, and sometimes works correctly right away - again, haven’t found a pattern to that.
Any thoughts on what might be happening, or what I can try? Again, no changes to the Ableton files, no update to Ableton, update to AbleSet 2.7.1, and possibly a macOS update in there.
**Edit to add that I’m also having inconsistent behavior where Autoplay (on) doesn’t work, and Auto-jump to next song (off) still jumps anyway
It dawned on me that I could install previous versions of AbleSet, so I tried both 2.7.0 and 2.6.7, and the issue still happens, so can rule out that bit at least.
I think it’s related to timing issues, since AbleSet is standalone application communicating with Ableton, there is great chance of micro delays.
Especially that AbleSet warns when you set global quantization to less than 1/4 that it is too short.
Not saying that longer quantization is a solution, just bringing related case.
I’ve tried to reproduce this issue on my end yesterday but couldn’t get this behavior, unfortunately. My hunch is that for some reason, after pausing, AbleSet fails to reposition the playhead and set the correct starting position.
Could you send me a log package along with your project file so I can check if there are any errors when the playhead reaches a pause marker?
Ah, one more thought, do you have Safe Mode enabled by chance? I wonder if that’s causing issues in combination with +PAUSE markers, but I haven’t been able to reproduce it on my end yet, unfortunately.
Apologies, didn’t mean to leave that hanging! Finally got back to it, and I think it’s related to the tracks buffering. When the issue was happening - in hindsight, it had been longer than typical since they were last loaded, so Ableton needed to buffer the tracks. Now that I’ve been able to get in there more frequently, it hasn’t happened, nor have I noticed any buffering happening.
I’m assuming that must have been at the root of it!
