Cue Feature Addon request

Feature Requests
1

I’ve taken a closer look into the new Cue feature. And it’s really cool to have this plugin, it could make my life a lot easier when adding new songs. :slight_smile:

But I would like to request some smaller refinements maybe for the future. The feature, to count in loops is only available if you turn on the whole “Count In Sections”. But I would find it really helpful to have this only available for the loop part. I’ve added sections to all of the songs and no one of the band (including myself) wants to hear all the section names during the performance but we would like to hear the loop guidance. :slight_smile: As a workaround I could delete all sections and only use the loop parts and the parts afterwards but I would love to have the sections still available.

Also, is it maybe possible to recognize the loop state of ableton and give as feedback when it changes? I’ve already done this by adding a script which sends MIDI notes to Ableton for “Loop on”, “Loop off” when the state changes and I have two samples as one shots for this. But I have to make sure, that monitoring is active.

2

Hey @Seb,

You don’t need to turn off count-ins entirely or delete any of your sections. In Settings → Cues → Cues Settings, the section count-in and the loop count-in are two separate toggles:

  • Count-In Sections During Playback → turn this off (stops the “Chorus, 2, 3, 4” section announcements)
  • Count-In Loops During Playback → keep this on (you’ll still hear “Loop, 2, 3, 4” going into your loops)

That should give you what you’re after, loop guidance without announcing every section during the show, and your sections stay exactly as they are.

If you ever want per-song control instead of the global toggles, you can also add these attributes right in the locator/clip names:

  • [c:0] — disable a section’s count-in
  • [c:loop] / [c:l] — enable loop announcements
  • [c:noloop] / [c:nl] — disable loop announcements

Add them to a song locator to apply to the whole song, and override per section as needed.

Reacting to the loop state (instead of the MIDI-into-Ableton workaround)

You don’t need to route MIDI back into Ableton or keep monitoring armed for this. AbleSet already exposes the loop state over OSC as /setlist/loopEnabled (0/1), and a Project Script can react to it the moment it changes:

// Project Script — runs on project load / AbleSet restart.
// Fires whenever AbleSet's loop bracket is enabled or disabled.
onOscChange("/setlist/loopEnabled", ([enabled]) => {
  const isOn = Number(enabled) === 1;

  if (isOn) {
    sendOsc("/cues/say", "Loop on");   // spoken feedback — no Ableton routing needed
    // Prefer your own one-shots? Trigger them here instead, e.g.:
    // sendMidiNote("Your MIDI Output", 1, "C3");
  } else {
    sendOsc("/cues/say", "Loop off");
    // sendMidiNote("Your MIDI Output", 1, "D3");
  }
}, false); // false = only react to real changes, not on project load

Set it up under Settings → MIDI Mapping, OSC & Scripting → Project Script. Using /cues/say gives you spoken feedback straight out of AbleSet with no monitoring dependency — but if you’d rather keep your own samples, just swap in the sendMidiNote(...) lines.

You can also see the Project Script in action in the official tutorial.

Would that work for your use case?

1 Like
3

Thanks a lot for jumping in. :slight_smile: If I set it like this, the “Count-In Loops During Playback” is not active if I disable “Count-In Sections During Playback”. They seem connected to each other, the loop option setting also disappears if I turn off the toggle of the “Count-In Loops During Playback”.

Thanks also for your script advice, that’s amazing and exactly what I was looking for.
I’m looking forward to implement this in our live rig after the festival season. :smiley:

1 Like