Hi - I’m investigating using Ableset for programming musicals. In this setting, Ableton is always triggered by someone in the pit using a single GO button or footswitch from the start of the show to the end. So the same button will start a song (or section of a song) as well as cue out of vamps and do a quantized jump to the beginning of the next section.
Right now I don’t see a way to duplicate this behavior in Ableset, unless I’m missing something.
Thanks! Very impressive software.
Hey @DHaynes, welcome to the forum!
You might be able to achieve this functionality using a Custom OSC mapping. For example, the OSC command /setlist/playCuedSong; /loop/escape will jump to the next song when the end of a song is reached, start playback when the playhead is located at the beginning of a song, and escape a loop when one is currently active:
Let me know if this works for your use case!
I had considered and tested that and it almost works. The use case where it fails is if there is a Song that begins with a vamp (which is not uncommon). In that case it will play for a single bar/quantize length and then jump to the vamp exit. Maybe there could be a specific OSC for a “Theater GO” that would only try to escape a loop if playback is currently active?
An update to this - I got the behavior to work the way I want with a custom M4L device that triggers different midi notes through the IAC Bus depending on if playback is active. Would still love to have it work natively, though 
I’m looking for exactly this behaviour. I want to move through the live show with only one footswitch. One of the songs start with a +LOOP, so I’m running into the same issue, where it in this scenario will skip the loop.
I’ll look into solving it with M4L, or would you mind sharing your solution?
I managed to get a M4L-device working, which was a great intro project to learn some Max.
I set it up to control the native play and loop, could there be any downside of this instead of controlling via Ableset?
I just released AbleSet 2.8.0-beta.2 which includes a “Go Button” mapping that should cover all cases:
Let me know what you think!
I tested this yesterday and it works exactly as I need it to, thank you for the great work you put into this!
I also work in theater and I am loving the new GO button feature. The only thing it’s missing for me is that I need it to also resume playback if currently in a paused state.
EDIT: I figured out how to achieve this with custom OSC, so I’m all good! (for those curious: “/setlist/go; /global/play”.
My new issue is that the GO button seems to override the “jump mode” setting, so it will escape the loop at the current Quantization setting (1/4 in my case) rather than at the end of the section like I want it to.
Hey @s1ah, welcome to the forum!
That’s a good pointer, and something that should be easy to add. I’ll release it with the next beta.
Regarding your edit, the loop escape’s behavior is separate from the jump mode. If you want the looped section to finish before continuing, you can use the +LOOPFULL flag instead of +LOOP.
I hope this helps
I’ve just been testing this out on the latest beta - it’s great! just what I needed.
My only suggestion would be - currently, resuming after pausing will play from the start of the current section. It’d be great if it could instead resume playing from where the playhead is
That’s a good point, I’ll see what I can do
