A1R

A1R Cue

Automatic voice/cue triggers — A1R fires your Drum Rack cue samples in time, hands-free.

Coming soon in A1R ULTRA A1R Cue turns A1R into the brain of your cue system. It watches the setlist and bar count, then automatically sends MIDI notes to a Drum Rack of your own cue samples — announcing the next section and counting you in — so nobody has to place cue notes by hand.

How it works

A1R sends MIDI to a virtual port named "A1R MIDI". A track in Ableton (named "Cue") receives it, plays your Drum Rack cue samples, and routes the audio to whatever output feeds your in-ears. Everything runs on the server, so cues keep firing during a show even with no browser open.

Timing

Setup (once)

  1. Virtual MIDI port "A1R MIDI". On Windows, install loopMIDI and create a port named exactly A1R MIDI (set it to autostart). On Mac, nothing to do — A1R creates the port itself at launch.
  2. Drum Rack "A1R CUE". Build a Drum Rack with your own cue samples, one pad per cue, and name each pad after the cue it plays (see below). Save it to your User Library.
  3. Track "Cue". Create a MIDI track named Cue. Set MIDI From → A1R MIDI, Monitor → In, drop in the A1R CUE Drum Rack, and route Audio To the output that feeds your in-ears (e.g. a dedicated interface output).
  4. In A1R (logo popup → A1R CUE, Ultra only): confirm the port shows green, fill the mapping, hit Fire test, then turn the toggle on.

Pad names

Name your Drum Rack pads to match:

Mapping

In the A1R Cue box, map each cue name to the MIDI note of its Drum Rack pad, one per line:

chorus = 60
verse  = 62
1 = 36
2 = 38
modulation = 48
stop = 50
loop = 52

Matching is tiered for numbered sections: Chorus 2 uses a CHORUS 2 pad if you made one, otherwise falls back to CHORUS. Case and extra spaces are ignored. If no pad matches, A1R stays silent for that cue.

Because the routing is your own track → your own output, the cue can go straight to the in-ear mix (even when Ableton owns the interface via ASIO). Nothing is injected into Ableton's master.