LTCast LTCast
/ LTC scan badges
Manual › LTC scan badges

LTC scan badges

LTCast scans each audio file in the setlist to find embedded LTC timecode. The scan runs in the background after you add files. While a scan is queued, running or failed, a small badge appears at the right of the song card. Once it finishes, the badge goes away and the colour of the start timecode tells you the result.

Badge states

  • Pending (blue ⋯) — the file is queued for scanning; LTCast will scan it shortly in the background
  • Scanning (amber, spinning ⟳) — LTCast is actively reading the file to find LTC signal
  • Error (red !) — the scan failed due to a read error or unsupported format; click the badge to retry

While scans are running, a Scanning LTC n/m counter appears in the setlist header. Empty songs have no audio and are never scanned, so they show no badge.

Start timecode colour

  • Blue number — LTC found in the file; this is its first LTC segment
  • Yellow number — no LTC in the file; this is the start timecode you set by hand
  • Yellow --:--:--:-- — no LTC and no start timecode; chase cannot find the song

What counts as a segment

A single audio file can contain multiple LTC segments. A segment is a continuous stretch of decodable LTC frames. Gaps happen when timecode resets mid-file, when there is silence between two timecode regions, or when the signal is interrupted.

The start timecode of the first segment is shown on the second line of the song card (click it to copy).

Multiple segments in one file are common when a day's worth of recordings are concatenated into a single file. Chase can match an incoming timecode against any of a song's segments.

Rescanning

Right-click the song and choose Rescan LTC to rescan that file (a red ! badge also rescans on click). Use this if you replaced the file on disk with an updated version.

Rescan all

Rescan all LTC in the setlist's ⋯ menu rescans every file in the current setlist variant. This is useful after replacing a batch of files or when you want to verify all scans are current before a show. Other setlist tabs are not rescanned.

What the scan is used for

The scan result is stored with the song in your project, so rescanning is only needed if the audio file changes (relinking a file or replacing its audio rescans it automatically). It feeds two things:

  • Chase — LTCast finds the song, and the position inside it, from an incoming timecode by looking it up in the scanned LTC segments of your setlist songs. A song whose scan found no LTC is found through its Start TC and length instead, if it has a Start TC. See Chasing external LTC
  • The start-timecode chip on the song card

It does not decide how a song plays back. When you load a song, LTCast detects its LTC channel again, separately from the scan.

If a file shows a yellow --:--:--:-- but you know it contains timecode, try rescanning. The scan always detects the channel automatically: there is no per-song channel setting, and it ignores the LTC Track override in Settings → Devices.