Art-Net (OpTimeCode)
Art-Net is a timecode protocol that carries SMPTE timecode over standard Ethernet or Wi-Fi as UDP packets. LTCast sends it as OpTimeCode packets on UDP port 6454 — the Art-Net standard port. Any device on the network that supports Art-Net timecode input can receive sync without any audio cabling or MIDI interfaces.
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 Art-Net packets are sent: the Art-Net light in the status bar turns amber and reads Needs Pro, and Pre-Show Check warns about it.
Enabling Art-Net output
Open Settings → Outputs → Art-Net TC and tick it. The section expands to show the target list. The toggle only opens the network socket — it does not start any transmission by itself.
Art-Net is sent only while a song is playing: LTCast sends one packet for every new frame, so at 25 fps that is 25 packets per second to each target. While playback is paused or stopped nothing is sent — there is no keep-alive and no repeat of the last frame — so a receiver sees the timecode stop. Art-Net has no "transport stopped" message either; a console simply holds the last value or reports loss of timecode, depending on how it is set up.
Configuring target IP addresses
Each row in the target list has an enable checkbox, an IP address and, when there is more than one row, a remove button. Click + Add target to add a destination, so one LTCast can feed several consoles at once. Untick a row to pause a target without deleting it. The Art-Net pill in the status bar shows how many targets are enabled (for example Art-Net · 2).
Common target configurations:
- Specific device — enter the device's IP address (e.g.,
192.168.1.100). The packet is delivered only to that host. Use this when you know the exact IP of the receiving console or media server. - Subnet broadcast — enter the broadcast address for your subnet (e.g.,
192.168.1.255). All devices on the LAN receive the packet. Convenient when you have several consoles and do not want to maintain separate IP entries, but generates more network traffic.
A new target starts as 255.255.255.255 (broadcast to everything), and an IP address that is not valid reverts to it when you leave the field. That is fine on a small dedicated network. On a large network, or one with strict broadcast policies, replace it with the receiver's own IP address or the subnet broadcast (e.g., 192.168.1.255).
Network and subnet requirements
Art-Net always uses UDP port 6454. This cannot be changed. LTCast and the receiving devices must be on the same subnet for broadcast delivery to work — Art-Net packets do not cross routers. For direct IP delivery, the target device must be reachable on the network (check with a ping test).
On the receiving device, confirm its Art-Net timecode input is enabled and set to receive on the same subnet. On GrandMA2/3, ETC Eos, Chamsys, and most media servers, Art-Net timecode is typically under the network or timecode settings section.
Art-Net does not require pairing
Unlike some protocols, Art-Net timecode is fire-and-forget — LTCast sends to every enabled target and any configured device on the network picks it up without any pairing, handshake, or authentication step. If a new console joins the network mid-show and is configured for Art-Net input, it will receive and lock as soon as the next packet arrives.
Each packet carries the timecode and a frame-rate type: 24 (film), 25 (EBU), 29.97 drop-frame, or 30 (SMPTE). LTCast sends 23.976 with the 24 type, and any other rate with the 30 type. Verify that the receiving console's Art-Net input is set to the same frame rate as LTCast. A frame-rate mismatch causes the console to run at the wrong speed.