LTCast LTCast
/ What each protocol does
Manual What each protocol does

What each protocol does

LTCast outputs five protocols simultaneously from a single internal clock. You can enable any combination — each protocol targets a different class of receiving device, and they do not interfere with each other.

LTC — Linear Timecode

LTC is SMPTE timecode encoded as an audio signal. It travels on a standard audio cable to any device that has an audio input. Because it is audio, it works over analogue XLR, TRS, or digital S/PDIF connections without any special adapters.

  • Frame-accurate position sync
  • Accepted by audio consoles, video systems, lighting desks, and any device with a timecode audio input
  • The most universally compatible format — if a device accepts timecode at all, it almost certainly accepts LTC
  • LTCast can also decode incoming LTC (Chase mode) and re-broadcast it on all other protocols
LTC audio is a full-bandwidth audio signal. Route it to a dedicated output channel, not to your main mix or speakers.

MTC — MIDI Timecode

MTC is SMPTE timecode carried over MIDI. LTCast sends quarter-frame messages during continuous playback for smooth sync, and full-frame SysEx messages when jumping to a new position.

  • Frame-accurate position sync
  • Accepted by DAWs (Pro Tools, Logic, Ableton), lighting consoles (ETC Eos, grandMA series), and MIDI-enabled hardware
  • Requires a physical MIDI cable or a virtual MIDI port (loopMIDI on Windows, IAC Driver on macOS)
  • Quarter-frame messages: 8 messages per frame, sent during playback at 1x speed or faster
  • Full-frame SysEx: a single locate message sent when stopped or when jumping position

MIDI Clock

MIDI Clock is a tempo-based sync format. It transmits 24 pulses per quarter note (PPQ) with no absolute position information — only the current BPM. Receiving devices follow the tempo and beat division, but do not know the SMPTE timecode address.

  • Tempo sync at 24 PPQ
  • Accepted by synthesizers, drum machines, sequencers, and tempo-aware effects
  • LTCast can auto-detect BPM from the audio file and use that as the MIDI Clock rate
  • Start, Stop, and Continue messages are sent with the transport
MIDI Clock does not carry a timecode position. If you need frame-accurate sync, use MTC instead. MIDI Clock and MTC can run simultaneously on the same MIDI port.

Art-Net — OpTimeCode

Art-Net carries SMPTE timecode over standard UDP Ethernet on port 6454. No special cabling is required beyond a network switch or Wi-Fi access point. One LTCast instance can reach every device on the same network simultaneously.

  • Frame-accurate position sync
  • Accepted by lighting consoles (grandMA2, grandMA3, Hog 4, ChamSys MagicQ) and media servers
  • Travels over standard Ethernet or Wi-Fi — no MIDI cable, no audio cable
  • Configure a target IP or broadcast to the subnet (e.g., 2.255.255.255 for the Art-Net default subnet)

OSC — Open Sound Control

OSC sends timecode as custom UDP messages to a configurable address and port. LTCast includes built-in templates for popular media server software.

  • Frame-accurate position sync
  • Built-in templates: Resolume, disguise, Watchout, or a fully custom address and format
  • Configurable target IP and port
  • Useful when a device accepts OSC but not Art-Net, or when you need a non-standard message format

Comparison

Protocol Connection type Sync type Typical use
LTC Audio cable (XLR / TRS) Frame-accurate Consoles, video systems, legacy gear
MTC MIDI cable or virtual port Frame-accurate DAWs, lighting consoles
MIDI Clock MIDI cable or virtual port Tempo / beat Synths, drum machines, effects
Art-Net Ethernet / Wi-Fi (UDP) Frame-accurate Consoles, media servers
OSC Ethernet / Wi-Fi (UDP) Frame-accurate Media servers, custom software