Guides3 min read
REAPER Markers to a Theatre Cue Stack: Import and Cue Sheets
Exchange REAPER markers and regions with CueSync Theatre tracks, keep cue numbers and fades intact, and export PDF, CSV or USITT cue sheets.
CueSync TeamShow Control Engineers
Stop Retyping the Audio Department's Cue List
On musical theatre, corporate keynotes, cruise productions and timecoded concert tours, the playback engineer or sound designer usually builds the timeline first in REAPER — laying out stems, click tracks, SMPTE LTC stripes and scene markers. Without a clean interchange path, lighting, video and stage management end up retyping hundreds of timecodes into spreadsheets and consoles by hand, and the first cut in tech breaks every sheet at once.
CueSync treats REAPER markers, the Show Editor timeline, CueSync Studio and printed paperwork as views of one cue list.
How CueSync Reads Console Tokens Inside REAPER Marker Names
A REAPER CSV row only carries a start time, an optional end time, a colour and a name string. To keep cue metadata lossless across departments, CueSync parses the same bracket tokens lighting programmers already write into REAPER sessions:
| Marker text in REAPER | Result in CueSync's Show Editor |
|---|---|
Chorus (100) | Sets cue number to 100 and cue label to Chorus |
Chorus <4/3> | Records a 4 s up / 3 s down fade in cue notes (and carries it into USITT ASCII / grandMA3 sync) |
Chorus [Flash] or [Temp] on a region | Marks the region span to release at its end time |
Chorus {Call Macro 1} | Parks the console command string in cue notes for review without executing blind strings |
Chorus ^Front Truss^ | Records the target sequence and offers per-sequence track splitting on import |
Ordinary parentheses and angle brackets that do not match a token — such as Blackout (stage left) — remain untouched in the cue name. Unreadable rows (for example a 29.97 drop-frame label like 00:01:00:00 that does not exist on a drop-frame ruler, or a frame 28 in a 25 fps project) are reported by name rather than quietly placed at 0:00.
House Clock vs. Session Time: One Origin Rule
CueSync deliberately omits an "import offset" dial. Instead, frame-stamped timecode labels (01:00:10:00) are read as positions on the house clock and have the project's venue origin subtracted once — the exact rule incoming live timecode uses. If your show stripes Act I at 01:00:00:00 and your venue origin is 01:00:00:00, a marker at 01:00:10:00 lands ten seconds into the Part. Plain seconds (93.5) and MM:SS.mmm values are session-relative and land as written.
Need to check frame conversions or drop-frame offsets before you import? Open the browser-based Timecode Calculator to convert between 23.976, 24, 25, 29.97 DF, 29.97 NDF and 30 fps.
Sending Changes Back: REAPER CSV, Cue Sheets and USITT ASCII
Edits made during tech travel back out from File → Sync, Import & Export:
- Export Reaper Markers… writes
CueSync Markers.csvfor a chosen Part, preserving cue numbers and fades inName (12) <2.5>form, spans as REAPER regions, and cue colours in theColorcolumn. - Export Cue Sheet… generates seven tailored paperwork layouts — Operator list, Calling script (with
STBYcalls and optional scriptPagecolumn), Running order, Department, Lighting, Media and Sound — in PDF, HTML, CSV (formula-safe for Excel) or Markdown. - USITT ASCII 3.0 (available on the Lighting layout of a Theatre Show) writes a clean console cue skeleton with
Up/Downfades,Followontimes and! timecodereference comments for desks that import USITT ASCII.
Further Reading
Frequently Asked Questions
Does importing a REAPER CSV create console actions automatically?
No, and deliberately so. Imported markers establish cue numbers, names, colours, start positions, region spans and notes (including any <fade> or {command} strings found in the marker label), without inventing live protocol actions you have not reviewed. You bind actions on the output lanes in the Show Editor afterwards.
Which REAPER ruler formats can CueSync read?
Seconds (93.5), minutes and seconds (MM:SS.mmm or H:MM:SS.mmm), and frame-stamped timecode (HH:MM:SS:FF or drop-frame HH:MM:SS;FF) converted at your project frame rate. Musical bars.beats (such as 5.1.00) are refused by name because a CSV carries no tempo map — switch REAPER's ruler to a time or timecode format before exporting.
Can one REAPER marker file split into separate Lighting and Video tracks?
Yes. When markers in the CSV carry more than one colour or name more than one ^Sequence^, CueSync offers to split them into separate department tracks (such as Act 1 · LX and Act 1 · Video) while keeping single-track import preselected if you press Return.
How do I send a timecode marker CSV to ChamSys MagicQ, Hog 4 or Avolites Titan?
Use Export Desk Timecode CSV (MagicQ, Hog 4, Titan) rather than Export Reaper Markers. A REAPER export includes GO and follow cues at their authored positions because DAW markers fire nothing; the desk CSV writes house-clock HH:MM:SS:FF frames only for timecode-fired cues and holds back pyro, laser, flame and CO2 lanes unless switched On.
What paperwork formats can CueSync generate from a Theatre show?
File → Sync, Import & Export → Export Cue Sheet writes Operator list, Calling script, Running order, Department, Lighting, Media and Sound sheets as PDF, HTML, CSV or Markdown, plus USITT ASCII 3.0 for the Lighting layout of a Theatre show.
Keep Reading
- Guides
grandMA3 Session Sync vs MSC and OSC for Theatre Calling
Move a Theatre cue list between CueSync and grandMA3 without re-storing looks, and choose when Session Sync, OSC or MIDI Show Control fits.
- Guides
How to Chase External Timecode with a Cue Stack
Most guides cover generating timecode. Following someone else's is the harder half — locating, re-syncing, and deciding what happens when it stops.
- Guides
Where Should Your Show's Timecode Come From?
Reaper, QLab, the console's internal clock, or the live performance itself: four architectures, how to choose, and where a hardware generator fits.