Pro DJ Link in a show: overlays, lighting, video and DAWs.

Pro DJ Link stopped being merely the feature synchronising two booth players a long time ago: that same network publishes each track’s state, and a considerable part of today’s show is built on those data. Broadcast overlays, lighting, video and synchronisation with a DAW all draw from the same place.

Reliability varies between projects. There are documented, maintained routes, official routes within another ecosystem, and community projects advancing through research. This guide covers four destinations—Overlays, Lighting/video/DAW, the SC/PRIME family when reliable projects appear, and Rane Four / One—then explains what the network requires from you and which data to consume.

Overlays: the show on screen, served by the network

An overlay is a page superimposed on the broadcast video. The documented way to build one using equipment data involves a local server. Beat Link Trigger includes an embedded overlay server starting on a selectable port (17081 by default) and serving a template: an overlay.html file in a template folder that you can replace with your own, plus a public folder for graphics and fonts accessible under /public/.

The template receives hierarchical variables: players contains each player’s state, master identifies the player controlling tempo, mixers contains network mixers, and collections contains connected rekordbox instances. Each player’s data includes beat within the bar, countdown to the next cue, elapsed and remaining time, the tempo-master flag, displayed pitch, and track data: title, artist, BPM, key and duration.

Two implementation details save hours. First, do not rerender the entire page on every refresh: OBS’s browser plugin does not use double buffering, so the overlay flickers. The recommended route is querying /params.json with JavaScript and updating only changed elements. Second, the server can run disconnected from the equipment network, serving simulated data from two players, so you can design the template before rehearsal. Artwork and waveform URLs and template filters for shortening text or fixing decimal places are also available.

Lighting, video and DAWs: the show around the music

The same state that draws the overlay triggers the rest of the show: Lighting/video/DAW draws on that single source. The reference project describes its purpose unambiguously: connecting professional Pioneer equipment to lighting, video, laser software and audio workstations, generating MIDI events when a CDJ starts or stops, plays a particular phrase type or reaches specific bars. Manual cue automation then gives way to a show interface where markers are plotted on each track’s beatgrid.

Published integration examples already cover common destinations: lighting controllers such as QLC+ and grandMA2, video environments such as TouchDesigner, ArtNet and SMPTE timecode transmission, and Ableton Link synchronisation for DAWs. Distinguish what each bridge does: MIDI and bar-based triggers end up in a lighting or video programme; Ableton Link synchronises tempo, phase and beat between applications. That is musical synchronisation, rather than a guarantee that two machines’ audio is aligned to the millisecond.

At the hardware end, Denon’s own ecosystem offers a documented equivalent: its manual includes Ableton Link integration in PRIME players, with an adjustable offset, and Engine Lighting with SoundSwitch for DMX and smart lights. The table summarises where each route ends up.

The SC/PRIME family when reliable projects appear

The SC/PRIME family has its own interoperability. Start by respecting its official documentation. The SC6000 and SC5000 PRIME manual lists a LAN output for linking players and controlling professional DJ lighting and video, describes Link-port topologies—direct daisy-chaining, through a mixer or with an Ethernet hub—and allows one player to play files from the others. This is complemented by the remote Engine DJ library on the same network and Engine Lighting with SoundSwitch, supporting DMX, Philips Hue and Nanoleaf.

The manufacturer’s functionality is the reliable foundation. Community analysis of the firmware exists and is documented: the Mixxx wiki records extraction of Engine OS from a PRIME 4 and the emergence of associated mapping definitions. However, the same document recommends checking whether the family has already been analysed and acknowledges that some information is read while some is resolved by trial and error. Hence this section’s caution: until reliable, maintained SC/PRIME projects appear, published work consists of research advances, rather than functions on which you can depend for a show.

Rane Four / One: software interoperability rather than networking

Rane Four / One models do not participate in the show network: they are controllers connected to their software through USB, and interoperability depends on an application-compatibility matrix. The manufacturer’s knowledge base is clear: FOUR enables Serato DJ Pro without needing a licence while connected to the computer; it works with VirtualDJ with a Pro licence; and it supports Algoriddim djay Pro 5.2 or later on Mac and Windows, without iOS support. Serato stems are included from version 3.0, with a dedicated pad mode.

Rane One and its MKII version follow the same ecosystem logic, with their own entries in that manufacturer knowledge base. The practical consequence for the show is that, when Rane Four / One is part of the setup, synchronisation with lighting, video or a DAW goes through the controlling software, rather than a network port on the controller itself.

What the network requires: ports, equipment and conflicts

Three network requirements often emerge after the scenery is already assembled.

• Equipment speaking the full protocol. The interoperability project warns that it is not a sanctioned implementation and that XDJ-RX and RX2 do not exchange Link data with other players, as the manufacturer explains: their Link connects to rekordbox rather than communicating with the booth. Models without Ethernet ports do not even enter the conversation.
• Sufficient information. Available information drops sharply with pre-nexus hardware: position and timecode cannot be inferred, and the equipment has neither sync nor master, so beat-based triggers and Ableton Link synchronisation stop working. Streaming tracks without full analysis files also degrade functionality.
• No overlapping ports. Running the interoperability tool on the same machine as rekordbox creates competition for network ports. Separating them across two computers, or using a separate show network, resolves the conflict; the basic setup is explained in Pro DJ Link network configuration.

Metadata/beat/master/playhead in the show

Everything above rests on four data families: Metadata/beat/master/playhead, meaning loaded-track metadata, position within the bar, tempo-master identity and playhead position. The interoperability library documentation describes the same inventory: current tempo, pitch, playback state, the tempo-master player, and the origin and database identifier of the loaded rekordbox track, plus rich metadata including artwork, cue-point locations, beatgrids and waveforms.

This inventory has two documented limits worth knowing before designing a show. With four players in use, the database-server interface is unreliable because the tool cannot occupy an actual player number; the alternative is downloading export files from the players’ NFSv2 servers, which do not depend on that number. Rich metadata also arrives complete only for analysed tracks loaded on the players: without a beatgrid there are no phrases, and without phrases there are no bar-based triggers. Emulating a CDJ for testing provides a reference for the complete tool-testing cycle on that network.

Limits, risks and common mistakes

• Confusing a community project with an official feature. Unsanctioned functionality may stop working after a firmware or hardware update; the project itself warns of this.
• Assuming every model participates. RX and RX2 do not implement the complete protocol, and equipment without Ethernet is excluded by definition.
• Running everything on one computer. Rekordbox and an interoperability tool compete for ports: use two machines or only one of the applications.
• Asking a DAW for something it does not promise. Ableton Link shares tempo, phase and beat; it does not independently align two audio paths.
• Designing around SC/PRIME without a reliable project. Research advances are not a foundation for a show; the stable route remains the manufacturer’s documented functionality.
• Redistributing firmware or credentials. Analyse and document rather than redistribute. This guide provides no legal advice: rules vary by country, and usual practice involves your own equipment for interoperability purposes.

Next step

You now have the complete map: the network publishes state, that state becomes overlays, lighting, video and DAW interaction, and each ecosystem has its limits. If the foundation remains unclear—what the network is, which messages circulate and what you can do outside the official ecosystem—return to What Pro DJ Link is and what you can do outside its ecosystem.