CSV setlist export / import

CSV export saves the setlist as a plain-text spreadsheet, giving you a portable backup or a starting point for documentation. CSV import reads a list of audio file paths back into LTCast. The setlist export and import are free; the cue-sheet CSVs at the end of this page need Pro.

Exporting the setlist

Click the ↑ button (Export CSV) in the setlist header. A save dialog appears, suggesting setlist.csv — choose a location and file name. LTCast writes a UTF-8 file with one row per song and these columns:

• # — the song's position in the setlist
• Song Name — the name as shown in the setlist
• Duration — minutes and seconds (or hours:minutes:seconds over an hour); empty if LTCast could not read the file's length
• Offset — the song's own offset as HH:MM:SS:FF, or 00:00:00:00 when it has none
• File Path — the absolute path of the audio file on disk

If the setlist is empty, LTCast shows a message and does not create a file.

Importing from CSV

Click the ↓ button (Import CSV) in the setlist header and select a CSV file. There is no File menu entry for it. LTCast adds each song listed in the file to the setlist and reports how many were added. A file that is not in a recognised layout shows Invalid CSV format.

CSV layout for import

Import reads columns by position, not by header name. A header row is optional and is recognised when its first cell is # or the file has a Song Name column.

• The layout LTCast exports (#, Song Name, Duration, Offset, File Path) — the song name is the second column and the file path is the last column.
• The older layout (#, name, path, offset in frames) — the file path is the third column.

Rows with fewer than three columns, or with an empty path, are skipped. If the name is empty LTCast uses the file name from the path. Only the name and path are imported: durations are read from the audio files themselves, and the offsets in the file are ignored — songs come in without a per-song offset.

Partial import

If some files are not found on disk, LTCast still completes the import and tells you how many songs were added and how many files were not found. Those songs stay in the setlist as missing songs and can be reconnected with Relink missing files.

Cue-sheet CSV (Pro)

Two other CSV exports carry cue data rather than the song list. Both need Pro (a licence or an active trial).

• Setlist cue sheet — the PDF button in the setlist header offers Cue Sheet (CSV) next to the two PDF layouts (see PDF Cue Sheet). For each song it writes one row per cue followed by one row per enabled trigger, with the columns #, Song, Cue, Time, Standby (s), Trigger (cue rows: label only), Label, Note. Times are positions within the song. On a cue row the Trigger column holds the cue's trigger mode as it was set (auto, go or follow; empty if none), which is only a note for whoever reads the sheet — nothing in LTCast acts on it. On a trigger row the Time column holds the trigger's timecode, the Trigger column names the kind of message (MIDI NOTE, MIDI CC, MIDI PC, MSC or OSC) and the Note column carries its channel and data, or its OSC address and arguments.
• Active-song CSV — File → Export to CSV cue sheet… writes the cues of the active song with the columns Cue, Timecode, Seconds, Label, Department, Color; several departments are separated by |. This item is one of the console exports and is hidden by default — see grandMA2 / grandMA3 XML for how to show it.