Documentation
Cue2Live drives Ableton through a Remote Script, which the app now installs and keeps up to date for you.
~/Music/Ableton/User Library/Remote Scripts/Cue2Live whenever the installed copy is not from this build, so updating the app updates the script. Nothing to copy by hand.
Cue2Live. Restart Live after a first install so it picks the script up.
SongName_ hh:mm:ss (e.g., Glycerine_ 04:26).stop or autostop (case insensitive).Song Pool: Search bar provides quick lookup for audibles.
Cue2Live talks to Ableton over a local TCP socket. As of 1.6 there is no port to configure: the Remote Script asks macOS for a free port on 127.0.0.1, publishes it to ~/Library/Application Support/Cue2Live/server.json, and the app and the iOS Bridge read that file on every connection attempt.
Because the number is discovered rather than typed, two rigs on one machine cannot clash, restarting Live is picked up without touching anything, and the Ableton socket is never exposed to the network — iPads reach Live through the iOS Bridge instead. The status line reports the port it found.
Indicator lights reflect connection status to Live.
Detecting means no script has published a port yet — usually Live is not open, or the Control Surface slot is unset. Waiting means the socket is up and the handshake is in flight. Connected to Live means the session is live.
Pick a transport, then play the control you want to use — the button is the target, not the trigger.
Cue2Live to map from the iPad, or from a controller merged in through the Bridge's MIDI Thru.D#2 above Note - CH 10. Unmapped transports read "Not mapped".The UI will show setlist movement, but transport/mapping are handled inside Ableton and remain decoupled from the app being open.
Requires Cue2Live on the Mac, which installs the Remote Script for you. Playback will pause every 30 seconds unless licensed via the macOS app.
Available on the App Store; no additional setup beyond licensing. iOS / iPadOS 16 or later.
Can connect to one laptop over USB/Ethernet or two laptops over ethernet using a network switch.
Both Bonjour and Manual mode connect to the iOS Bridge on each Mac, which relays to Ableton. Wired interfaces only unless Allow Wifi Connections is turned on — a stage rig should stay off wifi, and the app will not quietly fall back to it.
Behaves like the macOS app; MIDI maps must originate from macOS.
When two laptops are synced, the music note turns green; changes mirror bidirectionally via the iOS bridge.
Zero-config discovery of the iOS Bridge on each Mac (macOS 10.15+). Nothing to type: the port comes from the advertised service.
Open the assignment sheet from the note icon to reserve the A & B slots. 2.0 lists the machines it has discovered — select one and press Set as A or Set as B, rather than typing hostnames in by hand.
Uses Contact Cards (IP or .local name). Assign primary/secondary and connect both. For networks where mDNS is blocked.
The port on a contact card is the iOS Bridge's listen port — 51515 unless you changed it in the Bridge's menu bar item. It is not Ableton's port, which the Bridge finds on its own.
Create from the globe icon in Setlist View. Save descriptors for quick reconnects, and turn on Autoconnect to have them dialled for you.
With Transport Over MIDI on, transport is sent as MIDI rather than as a command. As of 2.0 that MIDI travels over each machine's own connection to its iOS Bridge, and the Bridge emits it on a virtual CoreMIDI port named Cue2Live that Ableton binds to.
No Audio MIDI Setup work is required. The RTP MIDI session from 1.x is gone — you no longer create a network session or name it cue2live-mac-A / -B. Routing is exact because each frame goes out on the socket that already identifies the machine, so a prioritised transport reaches one rig without the other hearing it.
On the Mac, map from the Cue2Live port in Cue2Live's MIDI Map window. An action with no mapping still works — it falls back to the command path.
Opened from Preferences. Primary and Secondary each list the mappings that machine reported, kept apart per slot — the two rigs are never driven by one set. The lists are read-only: mappings are authored in Ableton by the macOS app and pushed here on connect.
User Button: name it, pick Note or CC, a channel (1–16) and a value (0–127), then Apply. It appears in the transport column while Transport Over MIDI is on, and sends only the MIDI you assigned — there is no transport fallback, so an unassigned button does nothing. It follows the same routing rule as transport: everything when synced or when "Send Transport Ctrl to Unsynced Device" is on, otherwise the prioritised machine.
The compact layout stacks the same controls into one column and moves the transport to the right edge. Everything on iPad is reachable on iPhone.
Background helper app that every iPad connects through, in both Bonjour and Manual mode. Bundled inside Cue2Live since v1.3, runs on macOS 10.15+, displays connection status in the menu bar and supports auto-launch.
It finds Ableton's published port itself and re-reads it on every attempt, so a Live restart needs no action here.
The port iPads dial, set from the row in the menu. Default 51515; if it is already taken the Bridge falls back to another and advertises that.
Only Manual mode needs the number — Bonjour clients read it out of the advertised service. Change it when mDNS is blocked on your network or something else owns the port.
The Bridge publishes a virtual CoreMIDI source named Cue2Live, emits the iPad's MIDI on it, and — for any input ticked in the MIDI Thru submenu — forwards that hardware's traffic onto the same port.
A Remote Script only hears the one port set in its Control Surface slot, so this is what lets a playback tech's controller and the iPad drive the same transport mappings.
The Cue2Live macOS app has a button in v1.3+ that opens the bridge.
It is opened along with the macOS app by default; can be disabled via the “Auto” toggle in Cue2Live. "Enable On Startup" in the Bridge's own menu keeps it running independently of the app.
Bar count -- Set # of midi clips to create.
Beats Per Bar -- Set # of beats per clip. (4 for 4/4, 3 for 3/4, etc.)
Will work on whichever midi track is selected, not just the midi track it is placed on.
Requires the first session clipslot of selected midi track to be empty to work.
The plugin will not delete the clip if the first clip slot is occupied, but will throw an error.
A utility plug-in that decodes linear timecode (LTC) so you can view the timecode that is playing within your DAW.
It reads timecode; it does not generate or chase it. Nothing is written back to the host transport.
Timecode — HH:MM:SS:FF, or
HH:MM:SS;FF with a semicolon when the incoming stream
is drop-frame. Reads --:--:--:-- when there is nothing
to decode.
Detected rate — 23.976, 24, 25, 29.97 and 30 fps,
with NDF shown for non-drop 29.97.
Status — No signal,
Locked, or Locked (reverse) when the
source is running backwards, as it does when a playhead is
scrubbed.
Input level — shown in dBFS, so a feed that is too hot or too quiet to decode can be spotted at the plug-in rather than guessed at.
The macOS download contains both formats. Copy them to:
Audio Unit —
/Library/Audio/Plug-Ins/Components
VST3 — /Library/Audio/Plug-Ins/VST3
Windows VST3 —
C:\Program Files\Common Files\VST3
Decoding is done by libltc 1.3.2 licensed under the LGPL v3 or later. Source and documentation are at github.com/x42/libltc.