Example Setups
Real-world TimecodeLink topologies with sample IP addresses and default ports.
TimecodeLink is flexible — you can run it on the same machine as your DJ software or put everything on separate boxes. Here is one common multi-machine layout you can adapt to your venue network.
2 CDJs + TCL + Resolume + BEYOND
A small-club rig. Two CDJ-3000 players share a flat Ethernet subnet with three computers: one running TimecodeLink, one running Resolume Arena for visuals, and one running Pangolin BEYOND for lasers.
- CDJ-3000 #1 —
192.168.1.11— PRO DJ LINK on50000-50002 UDP - CDJ-3000 #2 —
192.168.1.12— PRO DJ LINK on50000-50002 UDP - TimecodeLink host —
192.168.1.20— receives PRO DJ LINK from the CDJs, sends OSC to Resolume on9000 UDP, broadcasts Art-Net timecode on6454 UDP - Resolume Arena host —
192.168.1.30— listens for OSC on9000 UDPfor track-change triggers (e.g./resolume/layer1/clip1/connect) - Pangolin BEYOND host —
192.168.1.40— chases Art-Net timecode on6454 UDP(broadcast — no target IP needed)
Only OSC receivers need an IP configured in TimecodeLink — Art-Net reaches every device on the subnet automatically. All addresses here are examples; use whatever scheme matches your venue network.
Related
- OSC Triggers — the protocol Resolume listens on
- Art-Net — the protocol BEYOND chases for timecode
- PRO DJ LINK — how TimecodeLink reads the CDJs
- MIDI Time Code — alternative timecode delivery over MIDI
Ready to Sync?
TimecodeLink bridges your DJ software with show control systems using professional timecode output.