Export for QLab
In the Cues view of the Tech tab, Export for QLab turns the cue sheet into a cue list for QLab 5 — scenes, lighting, mic, sound and projection cues in running order, with the audio, images and video each one plays. The same export is on the Reports tab as Cue List for QLab. Anyone who can open the cue sheet can download it (the board operator is usually run crew); changing its settings needs cue-editing access.
Being rolled out: this is switched on account by account. If you don't see it on your cue sheet, it isn't on for your account or company yet — ask support to turn it on.
What you download
One folder, named for the show: your media in audio and video, the cue list, a script called Build in QLab, and a READ ME. CueCall doesn't write a QLab workspace file — the script builds the cues inside a workspace you open in QLab, using QLab's own scripting.
1. Consoles
- Lighting cues: choose how QLab tells your console to go — an ETC Eos console over OSC, another console over an OSC message you write, MIDI Show Control, empty QLab Light cues, placeholders only, or leave lighting out. A lighting cue sends its own number: LX 12 fires cue 12.
- Blackout cue: a lighting cue with no number can't tell the console anything, so it becomes a placeholder. The exception is a cue described as a blackout: enter the console cue your blackout lives in (often 0) and those cues fire it.
- Mic cues: placeholders only, an OSC message per mic to your mixer, a command that runs on the QLab Mac with the mic numbers, or leave them out. A mic swap is always a placeholder — nobody can do one from a console. A cue that names a mic group sends one message for each mic in it.
- Mic levels: if your mixer takes a level over OSC, add a level message and say what value Low and Loud are on your mixer. A mic cue marked Low or Loud then sends the level as well as turning the mic on. Left blank, the level appears in the cue's name only.
- Mic groups: the show's groups can be edited here too. A cue naming a group with no mics in it yet is listed under what needs attention.
- Audio output patch: name the patch from QLab's Workspace Settings → Audio that every sound cue should play through, and each Audio cue is assigned to it when it's built. A sound already in the workspace keeps the patch the operator gave it; a name the workspace doesn't have is listed in the script's report. Network and MIDI patches are chosen with the lighting and mic settings.
- Video stage: name the stage (video output) from QLab's Workspace Settings → Video that every projection should play on, and each Video cue is assigned to it when it's built. A projection already in the workspace keeps the stage the operator gave it, and if the workspace has no stage by that name the script's report says so. Left blank, QLab uses its default stage.
- Fades: each projection takes the previous one down, as a cut or as a crossfade of the length you set. Set how long a projection-out or a sound fade-out takes when the cue doesn't say, and whether every sound fades in. Every fade-out stops what it faded once it ends, so nothing is left running silently.
- Timing: a still image never finishes, so an auto-follow on one would never start the next cue. It's exported as an auto-continue — once the image has faded in, or straight away, as you choose — and listed so you know.
- Cues timed into a song: a cue whose trigger is Timestamp (say 1:32) fires itself that far into its song. In QLab the song's sound cue becomes a Timeline group holding the song and every cue timed to it, each with its time as a pre-wait, so one GO runs the whole number. The time is measured from the sound cue in the same scene that plays the cue's song, or, for a cue with no song, from the last sound cue before it. Pick the song in the cue's Into song field, which appears when the trigger is Timestamp. When you switch a cue to Timestamp it starts on the song the sound before the cue plays, and a cue already saved with no song keeps that choice; a sound cue counts as playing a song when it is linked to it or its description is the song's title. Times like 1:32, 1:32.5, 92s or 1m 32s are understood (a bare 1.32 is ambiguous and is left for you); a cue with anything else ("bar 48"), or with no song playing in its scene, stays a manual GO and is listed under what needs attention. A cue that auto-continued into a timed cue no longer continues — it would otherwise start whatever came after — and both are listed so you can set the chain again in QLab. Choose Leave them for the operator to keep every timed cue as its own GO with the time in its notes — the export then says how many cues that covers, so a production set this way never wonders where its pre-waits went.
- Layout: a group per scene, a divider per scene, or one flat list; CueCall's cue numbers, 1-2-3 numbering, or none; department colours; and whether fly, deck, automation and spot cues appear as placeholders. QLab doesn't continue out of a group, so when the last cue of a scene auto-continues into the next scene, use a divider per scene or one flat list — with dividers the chain carries straight through. With a group per scene, those cues are listed under what needs attention.
Until someone chooses otherwise, lighting and mic cues are placeholders, so a first export never sends anything to a console.
2. Media
- Automatic: a sound cue linked to a song plays that song's Minus Vocal track — the music with no vocals, since the cast sings live — or, if it has none, its Performance track. With neither, it looks for a file named for the song (or for the cue's description) — track numbers, file extensions and punctuation don't matter, so "03 Triton_s Court.mp3" matches "Triton's Court". Guide-vocal, piano-only and full-mix tracks are never picked automatically, and if two files match equally the cue is left for you to choose — unless exactly one of them is that song's own file, which is then taken. A file picked this way says "check it's the show track". In the file list, a file a song uses shows which song and which kind of track it is, so two files with the same name can be told apart.
- Projections: a video cue plays the projection its description names ("Projection: Eric's Ship" plays the projection called Eric's Ship), looking in its own scene first and then across the show; failing a name, it plays the scene's projection when the scene has exactly one. A projection belongs to a scene through its scene on the Projections list or by being assigned to the scene.
- Choose a file: pick any audio file for a sound cue, or any image, video or projection for a video cue, from the files on the show. The same choice is on the cue's own form, as Plays
- Upload: if the file isn't on the show yet, upload it from the cue's row. It's added to the show's files (under Sound or Projections) and linked to the cue in one step. Uploading needs file-upload access as well as cue-editing access.
- Nothing: for a cue QLab doesn't play — a number the band plays live, say — so it doesn't go out with a rehearsal track attached.
- Needs a file: a cue with nothing to play is still built, and is listed so you can fix it.
The package only carries files you can open yourself. If a file is restricted to roles you don't hold, its cue shows as needing a file in your export.
3. Download, then in QLab
- Download package: everything, media included. Without media is the quick one when only the cues changed.
- Save to a folder: in Chrome or Edge, writes the same folder straight to a place you pick — no ZIP to unpack and no size limit. It skips media that is already there, so it's also the quick way to update, and if it's interrupted, saving to the same folder again picks up where it stopped.
- Big shows: one ZIP carries up to 1GB of media. Past that, use Save to a folder. In Safari or Firefox, download the package without media and then each file from the list in the dialog.
- Build: unzip on the Mac that runs QLab, open a new workspace in QLab (File → New Workspace), double-click Build in QLab and press Run. The first time, macOS asks whether Script Editor may control QLab — choose OK. The script names the workspace and asks before it changes anything.
- Save where it offers: the script saves the workspace into the package folder. Keeping the workspace beside its audio and video folders is what keeps the media linked when the folder moves to another Mac.
- The report: it finishes with a summary and a CueCall build report listing media it couldn't find, cues that need a look, cues QLab marks as not ready, and what's left to set up in QLab — the network or MIDI patch for your console, levels, the projector.
When the cues change
Download again, replace the files in the folder, open your saved workspace and run the script again — it offers Update
- Changed to match CueCall: cue numbers, names, notes, linked files and console messages. New cues are added in place.
- Left alone: levels, video geometry, patches, colours, and any cue you added by hand.
- Timing: a pre-wait, a post-wait, a fade length or an auto-continue you set in QLab is kept. The exception is a cue whose timing was changed in CueCall since the last build — then CueCall's timing is applied to that cue, and only that cue.
- Fade levels: a sound that fades in starts silent and fades up to the level it had when its fade was made; a fade-out ends silent. These are set once, when the fade cue is made — if you change a sound's level later, change its fade-in to match.
- Removed cues: a cue deleted in CueCall is disarmed and labelled [REMOVED], not deleted, so nothing you set on it is lost.
- Cues that change kind: if a placeholder becomes a console message (or the other way round), the old placeholder or message cue is replaced. Audio, video, fade and light cues are never deleted.
- Your own notes: each cue's notes end with a line like [cuecall:…], which is how an update finds the cue. Anything you type below that line is kept; leave the line itself in place.
What you need
QLab 5 on a Mac. Your QLab licence decides which cue types it will run — a cue it won't run shows a red X in QLab, and the build report lists it.
QLab® is a registered trademark of Figure 53, LLC. CueCall is not affiliated with or endorsed by Figure 53.
More in Master Cue Sheet (Tech Tab)
- Master Cue Sheet (Tech Tab): Cue Types — Tech cues are organized by type, each with its own color and prefix:
- Master Cue Sheet (Tech Tab): Master Cue Sheet View — The master cue sheet displays all cues organized by scene:
- Master Cue Sheet (Tech Tab): Filtering & Search — Narrow down the cue list for specific departments:
- Master Cue Sheet (Tech Tab): Finding Duplicate Cues — In the Cues view of the Tech tab, Find duplicates lists cues that were entered more than once: the same department on the same script page (or, when a cue has no page, in the same scene), sharing a…
- Master Cue Sheet (Tech Tab): Import Cues from the Script — In the Cues view of the Tech tab, Import from Script reads the cue notes already written in the show's script — "LX 4: dim to blue", "MICS ON 1-6", "PROJECTION: Bull Pen", "Auto Continue" — along…
- Master Cue Sheet (Tech Tab): Mic Cues & Mic Tracking — In the Cues view of the Tech tab, and in the Cues panel beside the script, one mic cue holds everything a single GO does to the mics — the way a prompt book writes "ON Mabel, Frederic · OFF 1, 2".
- Master Cue Sheet (Tech Tab): Mic Groups, Levels & Cue Timing — In the Cues view of the Tech tab, the Add Cue and Edit Cue forms carry the parts of a cue that say how it runs, the way a prompt book writes them.
Try CueCall
Your first two shows are free for a full year each, with every feature and unlimited users. Pricing is per show, not per user.