Spoken cues for live production.
A cue list that calls itself. Add a cue, type the line, and hear it spoken on the beat, with count-ins that call the standby and the 3, 2, 1 for you.
See it call a show.
Three and a half minutes, from your first cue to count-ins, zones and timecode. The cue calls you hear are the app's own voice.
Count-ins that call themselves.
Drop a block above a run of cues and every one of them gets its standby and countdown, timed back from the cue.
Type the words, then @ and when.
A count-in block is one line: what to say, and when to say it. The app voices it before every cue below, in its own voice so the crew can tell a countdown from a call.
Thirty seconds to {label} @30One call, 30 seconds outStandby {label} @4.3.2.1The standby, then 4, 3, 2, 1@1.2.3.4/120bpmA musical count-in, on the beat@10..1Ten down to onePress the ? beside the clock for the full syntax.
Set it once per section
A block applies to every cue below it until the next block. Stack two together and both apply: a thirty-second notice and a 4, 3, 2, 1 on every cue.
Stop one, keep the rest
An End block stops the cascade, either everything above it or just the block you pick, so the countdown can carry on after the notice stops.
See the cascade at a glance
Every block has its own colour, striped down the cues it covers. Drag a block to move it; the stripes follow.
Locks to the clock you already run.
Run on the internal clock or wall time, or follow the show clock coming from the rest of the rig.
LTC, MIDI timecode, or a CLX leader.
Feed LTC into any audio input, take MIDI timecode from a console or DAW, or follow a CLX clock leader on the network, over multicast or straight to the machine. Packets that carry a send time are corrected for network delay.
Cues and count-ins fire against whichever clock is driving, and the display dims if the leader goes quiet, so you know before the show does.
One show file, Mac or Windows.
Build the show on one machine and run it on another. The same show file opens on both.
macOS
The full desk: build lists, edit timecode, and run the show from a laptop at the production table.
Windows
Native on the machines already racked in most venues, straight from the Microsoft Store.
Offline
Voices are generated on the computer, so the show runs with no network and nothing leaves the machine.
More than one caller
Open the same show file on several machines and lock them to the same LTC or CLX timecode. Every position hears its calls on time.
Built for the booth.
Everything a caller needs on a show night, and nothing that gets in the way of the next cue.
Timecode cue list
Every cue carries a timecode position. Run on the internal clock or lock to an external timecode source and let the show call itself.
Manual GO
Standbys and go cues fire on the line when you say so. Timed calls cover the moments that cannot slip during a run.
Scriptable cues
Embed Lua in any cue to send OSC, Art-Net, MIDI, or UDP alongside the spoken call. A d3 module ships built in; MA3 is in development.
Clear output
Voice tuned to cut through a busy front of house or a backstage monitor. Cues are understood the first time.
Zones
Send each group's calls to its own output: band in-ears, crew comms, front of house. Zones speak at the same time.
Portable show files
Load and save show files for repeatable runs across venues. No cap on the number of lists or cues.
Count-in blocks
Standbys and countdowns timed back from each cue, written once per section and colour-coded down the list.
Two voices
Pick one voice for cues and another for count-ins, so a countdown never gets mistaken for the call itself.
Spreadsheet in, spreadsheet out
Import a cue sheet from CSV or ODS, count-in blocks included. Leave a block's time blank and it attaches above the next cue.
Any room with a cue sheet.
If someone is counting down to a moment, the call can come from here.
Theatre
Call lights, sound, and scene changes from one list. Fewer tabs, less paper, one voice the crew can rely on.
Conventions
Make venue-wide announcements, call attendees back to meeting halls, and flag start times without chasing a PA operator.
Concerts
Cue lighting looks and band changes on count. Performers and operators stay on the same beat.
Broadcast
Keep cameras, audio, and graphics lined up through live segments without overloading the talkback.
Ceremonies
Graduations, awards, and keynotes stay on schedule with clear calls for entrances, playback, and transitions.
Arenas & installations
Halftime moments run on tight windows, and permanent installs repeat the same run every day from a saved file.
A caller you can count on.
The reasons it holds up on a show night, not just in a demo.
The show runs without the internet
Doors open whether or not the venue Wi-Fi does. The cue list and its voices live on the computer and fire from there.
Timecode is a first-class citizen
Cues are positioned on a clock, not buried in a checklist. Lock to external timecode and the running order takes care of itself.
Scripting where you need it
Lua on any cue means the spoken call and the rig fire together — no second operator waiting for a nod.
One file, every position
The whole show is one spreadsheet file. Hand the same file to every machine that calls, and nobody runs an old version of the running order.
Cross-platform by default
macOS and Windows are both first-class, and a show file moves between them unchanged.
Nothing to learn on show day
Add a cue, type the line, set the time. The interface is the cue sheet a caller already reads.
Speaks to the rest of the rig.
The spoken call is the front end. Underneath, each cue can talk to the rest of the room.
- Cue triggering
- Manual GO on the line, timed calls, and timecode positions driven by the internal clock or an external timecode source.
- Timecode sources
- Internal clock, wall clock, LTC on any audio input, MIDI timecode, and a CLX clock leader over multicast or unicast UDP.
- Count-ins
- Timed spoken calls before each cue, with lead text, counts, ranges and tempo-based counts, cascading, stackable, and stoppable per block.
- Protocol output
- OSC, Art-Net, MIDI, and UDP sent from a cue's script at the same instant the call is spoken.
- Lua scripting
- A full scripting hook on any cue, for conditional calls, rig commands, and anything a plain cue line cannot express.
- Console & server modules
- A d3 (disguise) module ships built in. A grandMA3 module is in development.
- Show files
- Load and save complete cue lists, then reopen the same show in another venue or on another platform.
- Zones
- Route groups of cues to separate outputs on the audio interface, all playing at the same time. Several machines can also run one show file, locked to the same timecode.
Frequently asked questions.
The things people ask before their first show file.
What does Show Caller AI do?
It calls your cues out loud. You build a cue list, type the line for each cue, and the app speaks it — fired manually on the line, on a timer, or at a timecode position. It is a spoken cue notifier for stage managers, show callers, and anyone running a room from a cue sheet.
Which platforms does it run on?
macOS and Windows, from the Mac App Store and the Microsoft Store. The same show file opens on both.
Can cues trigger lighting, video, or audio systems?
Yes. Any cue can embed Lua that sends OSC, Art-Net, MIDI, or UDP alongside the spoken call. A d3 (disguise) module ships built in, and a grandMA3 module is in development.
Does it work offline?
Yes. The voices are generated on the computer itself, so a show runs with no network connection at all.
Can a crew share one cue list?
Yes, as a file. Save the show and open it on each machine that calls; lock them to the same LTC or CLX timecode and they call together. There are no accounts or cloud sync.
Is there a limit on cues or cue lists?
No. Create as many cue lists and cues as the production needs, and save each one as a show file you can reopen anywhere.
What are count-ins?
Count-ins are coloured blocks in the cue list that speak timed calls before each cue below them. Type the words, then @ and when: Thirty seconds to {label} @30 calls once at T-30, and Standby {label} @4.3.2.1 says the standby then counts 4, 3, 2, 1. Blocks stack, cascade until the next block or an End, and use their own voice. New in version 12 on macOS and Windows.
Can it follow a CLX clock leader?
Yes. Choose CLX as the external source and the app follows a CLX leader's clock over multicast or unicast UDP, correcting for network delay when the leader stamps its packets. LTC and MIDI timecode are supported too.
Can cues follow timecode?
Yes. Each cue carries a timecode position and fires when the clock reaches it, driven by the internal clock or an external timecode source.
Ready to call your show?
Build the cue list once. Let it call itself for the rest of the run.