Example Setups
Sample IP addresses and default ports for a TimecodeLink rig.
TimecodeLink can run on the same machine as the DJ software or on its own box. Here is one common multi-machine layout to 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.
| Device | IP | Traffic |
|---|---|---|
| CDJ-3000 #1 | 192.168.1.11 |
PRO DJ LINK on 50000-50002 UDP |
| CDJ-3000 #2 | 192.168.1.12 |
PRO DJ LINK on 50000-50002 UDP |
| TimecodeLink host | 192.168.1.20 |
Receives PRO DJ LINK from the CDJs, sends OSC to Resolume on 9000 UDP, broadcasts Art-Net timecode on 6454 UDP |
| Resolume Arena host | 192.168.1.30 |
Listens for OSC on 9000 UDP for track-change triggers (e.g. /resolume/layer1/clip1/connect) |
| Pangolin BEYOND host | 192.168.1.40 |
Chases Art-Net timecode on 6454 UDP (a broadcast, so no target IP is needed) |
Only the OSC receiver needs its IP entered in TimecodeLink. Art-Net is a broadcast and reaches every device on the subnet by itself. The addresses are examples; use whatever scheme your venue network runs.
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: timecode over MIDI instead of Ethernet
Ready to sync?
TimecodeLink turns whatever your DJ software is playing into timecode your show control can chase.