LTCast LTCast
/ OSC Output
Manual โ€บ OSC Output

OSC Output

OSC (Open Sound Control) is a message protocol over UDP used by many media servers, VJ software, and show control applications. While a song plays, LTCast sends the current timecode as an OSC message on every new frame, giving the receiving application a continuous stream of position data it can act on.

Pro. LTCast sends MTC, Art-Net and OSC timecode only while the session is Pro (a Pro licence or an active trial). Without Pro โ€” the free version, an expired trial or a lost licence โ€” no OSC messages are sent: the OSC light in the status bar turns amber and reads Needs Pro, and Pre-Show Check warns about it. This covers the transport, song and cue messages described below as well.

Enabling and configuring OSC output

Open Settings โ†’ Outputs โ†’ OSC Output and tick it. A target list appears. Each row has:

  • an enable checkbox โ€” untick it to pause that target without deleting it;
  • the IP address of the device running the OSC receiver โ€” use 127.0.0.1 to send to software on the same machine;
  • the port the receiver is listening on (1โ€“65535) โ€” check the target application's OSC input settings for its number;
  • the format template (see below);
  • the protocol โ€” UDP (the default) or TCP (see UDP or TCP).

Click + Add target to send to several receivers at once, each with its own address, port and template โ€” no external OSC router is needed. A new target starts as 127.0.0.1, port 8000, Generic.

Format templates

Each target has a template that decides the address and arguments of the timecode message:

  • Generic (/timecode) โ€” one message to /timecode carrying five integers: hours, minutes, seconds, frames and frames-per-second (a whole number, so 29.97 is sent as 30 and 23.976 as 24). Use it for custom OSC mappings or software not listed below.
  • Resolume Arena โ€” one message to /composition/tempocontroller/timecode carrying the timecode as a text string (HH:MM:SS:FF) and the frame rate as a float. It carries the position only โ€” LTCast sends no BPM or tempo over OSC.
  • Disguise (d3) โ€” the same string-and-float message to /d3/showcontrol/timecode.
  • WATCHOUT โ€” the same string-and-float message to /watchout/timecode.

There is no custom-address template for the timecode stream; use Generic if the receiver can map /timecode. (Triggers are different โ€” an OSC trigger sends exactly the address and arguments you give it.)

Over UDP, OSC is fire-and-forget: LTCast sends the message and the receiver does not answer (unless you turn on OSC feedback). The OSC monitor shows exactly what went out and where. If the target device is not responding, check: the IP and port match the device's OSC input configuration, the device's OSC input is enabled, and no firewall is blocking UDP on the configured port.

The OSC monitor

Every OSC message LTCast sends is listed in the OSC monitor: Settings โ†’ Outputs โ†’ OSC Output โ†’ OSC monitor (or the Show tab โ†’ OSC). Each row is one message to one target and shows:

  • the time, to the millisecond, and whether it went by UDP, TCP or the Arena link (Settings โ†’ Outputs โ†’ Resolume Arena);
  • the destination (IP and port);
  • the address and arguments;
  • what sent it โ€” the trigger's name and timecode and the path that fired it: playback, chase, chase lookback or test fire (the โ–ถ button).

The line above the list shows each target with a light (green: sending; red: the last send failed or the TCP connection is down) and the timecode rate going to it. The timecode stream itself is only counted; click Timecode to list it too. CSV saves the whole list.

A row can carry one tag:

  • Arena col N on ยท 31 ms โ€” when the Arena link is connected to the same computer the message went to, LTCast watches Arena's columns: a column trigger is marked once Arena reports that column on air, with how long it took. No reply from Arena means it did not go on air within a second; Already on in Arena means it was on air already, so Arena has nothing new to report.
  • Same as 0.21 s ago โ€” the exact same message went to the same place less than a second earlier. See why a repeat matters.
  • Held ยท already sent โ€” the same trigger arrived from a second path (for example chase and local playback at the same moment) and LTCast did not send it again.
  • Not sent: โ€ฆ โ€” the message did not leave: the reason is given (TCP not connected, network unreachable, Needs Pro).

UDP or TCP

UDP is the default and what Resolume, disguise, WATCHOUT and most receivers take. Some receivers also accept OSC over TCP, where the connection itself tells LTCast when the other end is gone:

  • TCP ยท SLIP โ€” OSC 1.1 framing. QLab uses this on its OSC port (53000).
  • TCP ยท Length โ€” OSC 1.0 framing (each message preceded by its size). Some receivers, such as CuePoints, offer either; if the manual does not say, try SLIP first.

LTCast connects as soon as a TCP target is set and reconnects by itself if the connection drops; the target's row in Settings and the OSC monitor show whether it is connected. A message due while the connection is down is not sent later โ€” a trigger seconds late is worse than one reported missing โ€” and the OSC monitor shows it as not sent.

What TCP cannot promise. If the network stalls for a few seconds without the connection closing (a switch rebooting, a cable knocked), TCP keeps what was sent during those seconds and delivers it all at once when the network comes back โ€” late. UDP drops it instead. LTCast resets a connection whose queue backs up and reports those messages as not sent, but a short stall can still deliver a trigger late. For a show network you can't trust, prefer UDP unless the receiver only takes TCP; on TCP, a row in the OSC monitor means LTCast handed the message to the connection.

Why a repeated trigger matters

A second /connect to a column that is already playing is not harmless in Resolume: it restarts that column's clips from the top (and a clip set to Toggle turns off). LTCast sends each trigger once per pass โ€” every path that can fire a trigger goes through one exit, and the same trigger from a second path within a second is held back. If the OSC monitor ever shows Same as โ€ฆ ago on a trigger you did not press twice, something else is sending it too.

OSC triggers and the Arena link on the same column. Resolume treats /connect 1 as pressing the column's button, and the button stays pressed until a 0 arrives. Arena then ignores the next press of that column through its web API. Since 0.7.33 the Arena link releases the button before it fires, so mixing OSC triggers (from LTCast or another controller) with Arena-link triggers on the same column works.

OSC message rate

LTCast sends one plain OSC message (not an OSC bundle) to each enabled target for every new frame while a song plays. At 25 fps that is 25 messages per second per target; at 30 fps, 30. The rate is tied to the SMPTE frame rate of the playing song, not to any screen refresh rate. While playback is paused or stopped no timecode messages are sent, except what TC Bridge forwards from an incoming timecode. Most OSC receivers handle this volume without issue, but verify that your target application does not throttle or drop UDP packets at the incoming rate.

Other messages LTCast sends

Besides the timecode stream, an enabled OSC output also sends:

  • /transport/play, /transport/pause and /transport/stop (no arguments) when you press Play, Pause or Stop, by button or by key (Space, Enter, Esc). Panic sends /transport/stop too.
  • /song with the song name (string) and its zero-based position in the setlist (integer) when a song is loaded.
  • Any OSC trigger you have set up in the Triggers panel.

All of these go to every enabled target.