Cuely

timecode cue marker
00:00:00:00no audio loaded
MTC
Now—
Drop an audio file here or load one above.
Press Demo tone to try it with a generated track.
Zoom 1–9 drop cueSpace play← → nudgedrag a marker to move itCtrl+Z undo

Cue

Select a cue in the sheet or click its marker on the waveform.

Tracks

KeyNameSeqToken⏻

Each track becomes one MA3 timecode track targeting its sequence. Pressing a track's key drops a cue on it; ▲▼ moves tracks into the 1–9 keys. ⏻ makes a track one-shot: every cue dropped on it gets an automatic off event after the gap you set.

Console settings

MTC output

Streams MIDI Timecode at the show FPS, at the console TC shown on the clock (song offset included). Quarter frames while playing, a full-frame message on locate. On the console pick MIDI as the timecode slot's source.

Cue sheet

CueTime NameTokenFadeOff

Export

grandMA3

Sequences, cues, fades, colours and the timecode show, in one import. Tested syntax for 2.x.

ChamSys MagicQ

One file per track. Select the playback, Cue Stack → View TC View → IMPORT TC TIMINGS → Make Cues. Fades go in the comment; release events are left out.

Avolites Titan

Whole show at console TC plus one file per song from zero. On the timeline: Tools → Import Markers, then snap triggers to the markers. Match HH:MM:SS:FF and the frame rate.

ETC Eos

Browser → File → Import → CSV. Makes event list 1 with one event per cue (time + action Cue list/cue) and creates the cue lists and empty cues. No fades or release events.

Reaper · Daslight · others

Daslight has no marker import; drive its timeline with the MTC output instead and use the cue sheet as the paper list. The Reaper file imports via Region/Marker Manager → Import.

Every export respects the scope in Console settings (whole show or current song).

          

        

      

    

  


  

    How to get it onto the console, and the keys
    

      

        
Route A · One macro (recommended)

        
    
          
  1. Unzip. Copy Name.xml into gma3_library/datapools/macros/ (onPC: ~/MALightingTechnology/ on Mac, C:\ProgramData\MALightingTechnology\ on Windows) or onto a USB stick under grandMA3/gma3_library/datapools/macros/.
    2. 
          
  2. In the Macro pool, edit an empty slot → Import → pick the macro.
    3. 
          
  3. Run it. Plain command lines store the sequences, labelled empty cues and fade times; inline Lua lines then build the timecode show with one track per Cuely track, using the console's object API. Every step logs as [Cuely] in the Command Line History. If a step fails you'll see which one.
    4. 
        

        
Nothing depends on internal handle numbers, so it should survive MA3 version changes.

      

      

        
Other consoles

        
Avolites Titan: the CSV zip contains Reaper-layout marker files (H:MM:SS:FF). On the timeline, context menu Tools → Import Markers, then snap triggers to the markers. One file has the whole show at console TC, plus one per song from zero.

        
ChamSys MagicQ: one CSV per track in the zip. Select the target playback, Cue Stack Window → View TC View → IMPORT TC TIMINGS → Make Cues; every timecode becomes an empty cue to record into. Fades and release events can't be carried by that import, so they are noted in the comment or left out.

        
ETC Eos: a CSV in Eos's own import layout (Browser → File → Import → CSV): a show-control event list (number = the timecode pool #) with one event per cue firing Cue list/cue, plus one cue list per track (numbered like the sequences) with empty labelled cues. Pick SMPTE or MIDI as the list's source in the Eos section. Fades and release events aren't carried.

        
Daslight has no marker or cue import, so there's nothing to write for it; its timeline can follow MIDI timecode, so run Cuely's MTC output into it and use the cue sheet CSV as your list.

        
Route B · Lua plugin / legacy XML

        
    
          
  1. Lua plugin: same engine as the macro, packaged as Name.lua + Name.xml for gma3_library/datapools/plugins/. Import into the Plugin pool and tap it.
    2. 
          
  2. Legacy XML: Name_timecode.xml goes in datapools/timecodes/, Name_macro.xml in datapools/macros/; run the macro, which creates the sequences and imports the timecode file. Same layout the common Reaper→MA3 converters write, but it carries legacy internal handle numbers, so check events landed on the right sequence.
    3. 
        

      

      

        
Keys

        

          Spaceplay / pause
          1–9drop a cue on that track at the playhead (the track's key is shown in the Tracks panel)
          Mdrop a cue on the active track (the last one you used)
          Shift+1–9make a track active without adding a cue
          ← →nudge one frame · Shift one second
          Homeback to start
          PgUp PgDnprevious / next song
          [ ]move selected cue one frame · Shift one second
          Deleteremove selected cue
          Dduplicate selected cue
          + −zoom
          ↑ ↓volume · 0 mute
          Wheelscroll · Ctrl+wheel zooms
          Ctrl+Zundo · Ctrl+Shift+Z redo (every change, including Clear all)
        

        
Shows: a show is a list of songs. Each song has its own audio file, its own tracks and a Starts at TC value: the console timecode where the song begins (song 1 at 01:00:00:00, song 2 at 02:00:00:00 by default, which matches the usual hour-per-song convention). Cue times inside a song are song-relative; the export adds the offset. The whole show exports as one timecode object with one MA3 track per sequence; a sequence used by several songs (a shared Hits sequence, say) becomes one track carrying all of them. Audio isn't saved in the project file, so reload each song's file when you reopen it (the amber dot on a song tab means no audio yet).

        
Colours: each track colour becomes an Appearance pool object (from the slot set in Console settings, one per colour, named "Cuely Red" and so on) and is assigned to that track's sequence and to its timecode track, so the sequence pool, executors and the timecode viewer show the same colour as the marker here. Click a track's swatch to cycle its colour.

        
MTC output: the MTC panel streams MIDI Timecode from the browser's MIDI port (Web MIDI: Chrome or Edge) at the show FPS, carrying the console TC on the clock, so the console's timecode slot can chase this page while you check cues against the real show. Run the console on the same machine with a virtual MIDI port (IAC Driver on macOS, loopMIDI on Windows) or use a USB MIDI interface. Inside the hosted page the browser frame blocks MIDI; save the standalone copy from that panel and open it in Chrome directly.

        
Working together: every show lives in your account and syncs live. Shows → Share invites someone by email; they sign in and the show is in their list. Everyone on a show sees cues appear as they are dropped, who is online, and each other's playheads. Audio files are not uploaded: each person loads the song's file. Undo covers your own changes.

        
Now / Next: the two panels under the transport show the cue that last fired and the one coming up, with a countdown and progress bar; the countdown turns amber in the last 3 s and the waveform shows a badge beside the playhead. The sheet follows the playing cue when Follow playhead is on.

        
One-shot hits: press ⏻ on a track to make it one-shot. Every cue dropped on it then carries an automatic off event after the gap you set (0.01 s upwards), so a "hit" sequence with cue 1 on and cue 2 off needs one key press, not two. The off is drawn as a shaded span on the waveform and exported as a second timecode event (Goto cue 2 by default; Go+, Off, Flash Off or Pause are also available). The off cue can carry its own fade time, and then Off (OffCue) adds a third event that sends Off to the sequence after the off cue, so the sequence's built-in OffCue runs and the playback is released rather than left sitting on cue 2; its delay defaults to the off cue's fade so the fade completes first, and you can set the OffCue's fade time too. The selected cue's panel on the left lets you change any of this per cue, move it between tracks, nudge it, add a delay, duplicate it, or push its settings to the whole track.

        
Fade times are drawn on the waveform the way a DAW draws audio fades: a cue's fade is a ramp rising from its line, a one-shot's off-cue fade tapers the shaded span away, and an OffCue fade tapers after the release mark.

        
Cues don't need a name when you drop them: keep tapping M on the fly and fill in names and numbers afterwards (unnamed cues export as "Cue 3" etc.). Click a cue's time to jump there. Click the waveform to locate; drag a cue's marker along the waveform to move it. The speed menu slows playback (pitch kept) so fast hits land on the right frame. Cue, name, token and fade are edited in place. Go+ needs no cue destination (it fires the next cue); Goto targets the cue number on that row.