Import from grandMA3, grandMA2, Reaper and CSV

What this does: reads a timecode show or a cue list from another tool and merges it into the open show as stacks and cues. Exports a track’s cues as CSV.

Every import merges into the open show. None makes a new show.

Which way in

File	Dialog	Open it with
grandMA3 timecode show (XML)	Import show	File → Import Show (grandMA3 / Reaper)…
Reaper project (.rpp)	Import show	The same
Reaper Region/Marker Manager CSV	Import show	The same
grandMA2 timecode show (XML)	Cue import / export	File → Import / Export data… (⌘I)
TimecodeMate or Reaper markers with {Stack} tags	Cue import / export	The same
Helm CSV, MA2 timecode events, plain Reaper markers	Cue import / export	The same

Other ways into Cue import / export: Build → Import Cues…, Tools → Cues → Import cues…, and Import / Export data… in Sequence Options.

Both dialogs need an open show with a track selected on Build. Without one the menu does nothing.

Before you import

• No undo. ⌘Z does not take an import back.
• No backup is taken first. The import saves the show at once.
• To be safe, export a show package first: File → Export Show Package… (⇧⌘S). Or check File → Restore from Backup… has a recent one. See Backups and show packages.
• Nothing reaches the desk. Push to the desk afterwards.

Import a whole show

The Import show dialog previews a grandMA3 timecode show or a Reaper file before anything changes.

1. Open the show. On Build, select the track the import is for.

2. File → Import Show (grandMA3 / Reaper)…. Or Import show… in the Cue import / export dialog.

3. The file picker opens. Pick the file. (Cancelled? Click Choose file….)

4. Read the preview. Set the options below.

5. Read the summary: Import adds N cues (m into existing stacks), s new stacks, t new tracks, k tempo markers.

6. Click Import. The toast starts Imported n cue(s) · ….

• grandMA2 XML is refused here. Use Cue import / export instead.
• Import stays greyed when nothing would be added, for example every event is already there.
• A grandMA3 XML or .rpp picked in Cue import / export opens this dialog. A Reaper marker CSV picked there does not.

grandMA3 timecode show

On the desk: Export Timecode 3, or Export Timecode 1 Thru 10. MA3 writes one XML per timecode show to gma3_library/datapools/timecodes. Copy it to the Mac.

MA3	Lands in Cues as
Timecode show / track group	A track. Per group: New track ”…”, any existing track, or Skip this group.
Track on Sequence N	One stack per sequence, named after it. Tracks of one group on one sequence share it.
Event time	Offset + time range start + event time
Cue destination Sequence 9.Cue 1.5	Desk cue 1.5 on that cue
Go+ / Go, Goto, Top, On, Off, Kill	The same command
Flash + its release	One Flash cue, hold = release − flash
OffsetTCSlot	A new track’s offset
Executor (Page 1.Exec 101)	Stored on a new stack as 1.101

Each sequence row shows n (d desk cues, f flash) and where it lands: New stack "…" · seq 9, or Existing stack "…".

Preview options

Option	Choices
Track per group	New track ”…” · an existing track (the selected one says (this track)) · Skip this group
Per sequence	Merge into a matching stack (same desk sequence or same name) · New stack
Place MA3 time 0 at	The MA3 offset (…) · The target track’s start. New tracks always start at the MA3 offset.
Sector for new stacks	Default Lighting

• New stacks use Manual numbering, so each cue fires its MA3 number.
• Merged into an existing stack, the MA3 number is set on each cue and wins over the stack’s rule.

Desk sequence numbers

• New track: its sequence start is the lowest MA3 sequence. Sequence 9 stays 9.
• Existing track: a stack keeps its MA3 sequence when the slot is free and at or above the track’s desk start. Otherwise it takes the next free one and the row says why:
  • Sequence n is taken on this track: the stack takes the next free sequence.
  • Sequence n is below this track's desk start (s): the stack takes the next free sequence.
• A merge into a stack that drives another sequence says Pushes to sequence d, not n.
• Re-import: events already in the stack are skipped and counted: · n already there.

grandMA3 limits

• Not yet tested with a real grandMA3 export. Check the preview against the desk.
• Skipped and listed as Skipped: Temp ×2 · Toggle ×1: Temp, Toggle, Go-, Load, Pause, rate and speed commands. Tracks that target a Sound, Preset, Group, Master or Timecode are listed by name.
• Not imported, counted per show: marker tracks and fader subtracks. Skipped: 2 marker tracks, 3 fader subtracks.
• Names instead of numbers: a renamed sequence (Blue Wash) matches by name and takes the next free sequence. A named cue (Intro) keeps its name as the label; its desk cue is blank.
• Events with no cue (Off, Top with no destination) import with no desk cue. In a new Manual stack they never reach the desk.
• Frame rate: the preview warns when MA3’s rate differs from the project’s.

Reaper

A .rpp project, or a CSV from Reaper’s Region/Marker Manager → Export. Everything goes on the selected track, in one stack.

Reaper	Lands in Cues as
Marker	A cue at the marker, named after it. No name: Marker n.
Region	A cue at the region start. No name: Region n. Optional second cue at the end, <name> end.
Project tempo and tempo envelope	Optional: the track’s beat grid
Project start	Optional: place Reaper 0 there

Preview options

Option	Default
Into stack	New stack, named Reaper markers, sector Structure. Or any stack.
Markers → cues	On
Regions → a cue at each start	On
Add a cue at each region end	Off. Greyed while Regions is off.
Place Reaper 0 at	This track’s start, or Reaper’s project start when the project has one
Use the tempo map as this track’s beat grid	Off. Greyed when the file has no tempo. Shows the opening tempo and meter and how many tempo changes carry a meter change. Reads Replaces this track's beat grid. when the track already has one.
File tempo (bars.beats times)	Shows only for a CSV in bars.beats. 120 by default, 20–400.

Reaper limits

• Tempo ramps become steps. The tempo holds through the ramp and jumps at its end.
• Time signatures become meter changes. Each one starts a bar on its tempo change, as in Reaper. See Meter.
• In x/8 the BPM counts eighths. Reaper counts quarter notes, so a 6/8 section at Reaper’s 120 reads 240 BPM in Cues. The speed is the same.
• The tempo map replaces the track’s tempo changes and bar markers. See Beat grid and tempo.
• Not imported: audio, media items, item positions, take markers, marker colours, markers inside nested blocks.
• A CSV in bars.beats (3.1.50) is read at the typed BPM, in 4/4. Export in seconds or timecode for exact times.
• Re-import into the same stack skips cues already there. Into a New stack it makes a second stack with every cue again.

Cue import / export

The Cue import / export dialog has two tabs: Import and Export.

Import a cue file

1. File → Import / Export data… (⌘I).

2. Stay on Import. Pick the Format.

3. Set the stack or sector (see the table).

4. Optional: First cue starts at, hh:mm:ss:ff. Every cue shifts so the earliest lands there. Blank keeps the file’s times.

5. Choose file…, or paste into Or paste CSV.

6. Click Import. The toast reads Imported n cues, with any skipped.

Format	Stacks	Reads
TimecodeMate / Reaper (with stacks)	Made from {Stack} tags in each name. Sector for new stacks sets their sector.	#,Name,Start,Color. A name like {Lighting Main} 1 Hit <Go> [fade=2]: stack, desk cue, label, command, fade, delay. Other […] is the cue command.
Helm CSV	Each row goes to the stack in its StackName, made in the row’s Sector if it doesn’t exist. Rows with no stack name go to the stack you pick.	Every column the Helm CSV export writes
Reaper markers	All into the stack you pick	#, Name, Start. Time and label only.
MA2 timecode events	All into the stack you pick	Time, cue and command. Cues are named Cue n.
MA2 timecode XML (stacks)	One new stack per MA2 timecode track	See below

• A grandMA3 XML or .rpp picked here opens the Import show dialog.
• Any other .xml switches the format to MA2 timecode XML.

grandMA2 timecode show

1. On the MA2, export the timecode show as XML. Copy it to the Mac.

2. ⌘I → Import → Format MA2 timecode XML (stacks).

3. First cue starts at: type the show timecode for the first MA2 event. Every event keeps its distance from it. Blank puts MA2’s 00:00:00:00 on the sequence start.

4. Choose file… → Import.

• Always new stacks, one per MA2 timecode track. A name clash gets 2.
• The executor comes from the MA2 sequence. Numbering is Manual.
• The desk cue is the number in the MA2 cue name, else the step. Cue names are kept as on the desk.
• The stack’s default command is the one most of its events use.
• The desk sequence is the next free slot on the track, not the MA2 number.
• Events with no Cues command are skipped and counted.

Export a track

1. File → Export ▸ a format. Or ⌘I → Export.

2. Pick the Format and the scope: All stacks on this track, or one stack.

3. Click Save CSV…. The default name is <show>-<track>-<format>.csv.

Format	Menu item	Columns
Helm CSV	Track → Helm CSV… (⌘E)	Timecode,Label,CueNumber,StackName,Sector,Command,TargetCue,FadeTime,DelayTime,Notes
TimecodeMate / Reaper (with stacks)	⌘I → Export	#,Name,Start,Color, with {Stack} tags in the names
MA2 timecode events	Track → MA2 CSV…	Timecode,Executor,Cue,Command,Fade
MA3 timecode events	Track → MA3 CSV…	The same. Go is written Go+; Kill is written Off.
Reaper markers	Track → Reaper Markers…	#,Name,Start,End,Length,Color
Paper Cue Sheet (running order)	Track → Paper Cue Sheet…	Timecode,Stack,Cue#,Department,Command,Target,Fade,Delay,Label,Notes

• Every export is one track. There is no project-wide export.
• A Flash cue writes two rows in MA2 and MA3 CSV: Flash On, then Flash Off a hold later.
• Commands: MA2, MA3 and the paper cue sheet write the command the cue fires, its stack’s default included. A Flash default also writes its Flash Off. Helm CSV leaves the command blank for “stack default”, so a re-import keeps the cue on the default.

CSV limits

• Helm CSV is a full round trip. Export, then import: every cue comes back in its stack, with its sector, delay and labels as they were.
• A locked stack takes no rows. Each skipped row is listed as a warning.
• MA2 CSV import does not read Go+, Flash On or Flash Off.
• Reaper markers reads timecode or plain seconds only. For Reaper’s own m:ss.mmm export, use File → Import Show….
• A wrong First cue starts at turns red and is ignored: the import runs on the file’s times.
• Warnings or a failed save keep the dialog open, with the file cleared so the same cues can’t go in twice. A failed save also shows an error.

When it goes wrong

• Invalid parameter: Not a grandMA3 timecode export, Reaper project (.rpp) or Reaper marker CSV. Wrong file for Import show. On MA3, export the timecode show, not a sequence. A grandMA2 XML goes through ⌘I → MA2 timecode XML (stacks).
• The menu item does nothing. No show is open, or no track is selected on Build.
• Cues landed an hour out. Place MA3 time 0 at, Place Reaper 0 at or First cue starts at picked the other origin. Delete the stack’s cues and import again with the other choice.
• … target track not found, group skipped. The track it was aimed at is gone. Pick another target.
• Sequence n is taken on this track …. Two shows share sequence numbers. Read the seq on each row before you push.
• … cues with no number in the file: desk cue left blank. Named cues on the desk. Set desk cues by hand, or renumber on the desk and export again.
• Bar numbers wrong after a Reaper import. A tempo ramp near a time signature. Ramps become steps, so the bars before a time signature can end a little short. The bars from it on are right.
• Times are bars.beats: read at … BPM, 4/4. Set File tempo in the preview, or export the CSV in seconds.
• A Reaper re-import doubled every cue. It went into a new stack. Delete that stack; import into the existing one.
• Helm CSV put everything in one stack. That is how it imports. Use TimecodeMate format for one stack per {tag}.
• The import went wrong and is saved. File → Restore from Backup…, if a backup from before exists. Or import the show package you exported first.