Import markers from LTC scan

When LTCast scans a file and finds embedded LTC, the scan results can be converted into markers on the waveform. Each detected LTC segment boundary becomes a marker, letting you quickly build a cue list from the structure already embedded in the audio.

Running an import

In the Cues tab, click From markers (the import markers button). LTCast reads the most recent LTC scan results for the loaded file and creates a marker at the start of each detected LTC segment.

This step requires that the file has already been scanned for LTC. If no scan results are available, run a scan first from the transport panel.

What gets created

Each marker is placed at the timecode position where a new LTC segment was detected. Markers are created with generic names based on the scan segment index (for example, "Segment 1", "Segment 2"). After importing, review and rename each marker in the cue list.

Duplicate protection: if a marker already exists at a detected position, LTCast does not create a duplicate — it skips that position.

This feature reads structural boundaries embedded in the LTC signal — it does not detect musical beats or energy peaks. The imported markers reflect where the LTC timecode stream started or restarted in the audio file.

Typical use case

A broadcast recording that has embedded LTC with natural segment breaks — for example, scene changes where the timecode restarted — is a good candidate for this workflow. Import the markers to get a rough cue list that mirrors the production's original timecode structure, then rename and adjust from there.

After importing

Review each auto-created marker in the cue list. Rename them, assign cue numbers, set trigger modes, and add department targets as needed. The imported markers are fully editable and behave identically to markers added by hand.

Previous Cue templates Next Sort & filter cues