Integrations
Exporting to Consoles
How the export window works, and which format your system needs
CuePoints writes your cue list out in the format your console, media server or editing suite expects. Everything starts in the same window, and works the same way whichever target you pick.
File > Export… (Cmd+Shift+E).
The Three Panels
Every export is the same three decisions.
CUE PLAYBACKS, which cue types go. Tick the CuePoint Types you want to export. The lighting operator exports Lighting; the video operator exports Video.
TRACK PLAYBACKS, which tracks go. Tick the tracks. Select All is there when you want the whole show.
Options, how it comes out. This panel changes depending on the format. The one setting almost every format has is Individual File Per Track:
Off: one file containing every selected cue type across every selected track.
On: one file per track, each containing that track's cues.
Which you want depends on the console. Desks that work a show as one cue list want one file; desks that work track by track want one each.
Set Save Exported Files To Folder to where the files should land, then press the export button for your format.
Before You Export: The Offset Trap
Cues are exported with their timecode offsets included.
If your show runs at 10:00:00:00, your cues export at ten hours. Import that into something that starts its own timeline at zero, Premiere, After Effects, CuePilot, and your cues land ten hours down the timeline, apparently missing.
They aren't missing. Either scroll to where the timecode says they are, or set the receiving timeline's start to match your track's offset.
Consoles that work in timecode, grandMA, Eos, MagicQ, Hog, want the offsets and handle them properly. It's the editing tools you have to think about.
What CuePoints Can Export To
Lighting consoles
grandMA2: a plugin carrying sequences, executors, pages and timecode
grandMA3: timecode XML
ETC Eos: ASCII, with cues, pages, timecode items and sequences in one file
ChamSys MagicQ: cuelist CSV
HOG 4: cuelist XML
Avolites: CSV
Media servers and show control
Disguise: cue table text files
Pixera: a live network link, not a file
QLab: AppleScript for QLab 4 or QLab 5
Unreal Engine: a Python script
Editing and post
Adobe CC: XML for Premiere Pro, and via Premiere into After Effects
CuePilot: a
.cuefeedback trackReaper: CSV markers
InqScribe: TAB
Plain files
CSV and TAB: generic spreadsheet exports for anything not on this list.
The generic CSV export has its own options for what goes in each column: put the note or info column to the cue type name or to the timecode, or leave either empty.
Naming And Numbering
Two settings worth knowing about, on the formats that support them:
Allow Cue ID Auto-Renumber lets CuePoints assign cue numbers as it exports, rather than using the ones in your project.
Set Cues to Cue Point Colours carries your cue type colours through to the console, so the desk looks like your cue list.
Exporting Audio And Video Instead
If what you want is a media file rather than a cue list, timecode as audio, or video with the overlay burnt in, that's File > Export Audio File, covered in Importing & Exporting.
Join our Facebook Community
Any other questions? Get in touch