Pro DJ Link Issue XDJ XZ

[elevate5406]

I’ve wanted to use the XDJ XZ to trigger MTC to MA3. But it seems like the XZ is getting a connection but no metadata is shared between STC and the XZ. STC notices that it is a XZ but other from that there’s nothing more that is useable.
In the bottom right it reads “Pro DJ Link paused” and on the left beneath Ableton link it reads “P1 no track - no Position Data | (IP Address)”
I’ve enabled the Track Map to a specific song but this doesn’t work either.
“DJM: waiting for bridge data”

What should I do?

[fiverecords]

Thanks for the detailed report — the specific messages you quoted are genuinely useful, because together they tell me exactly where this is failing.

What those messages mean

STC is discovering the XZ but receiving no playback data from it.

Device discovery on Pro DJ Link happens over broadcast packets, which is why STC can see the XZ and name it. Everything else — track info, playback position, mixer/fader data — is sent by the device as unicast, and only to peers it has accepted onto its list. STC is not on that list, so:

• P1 no track - no Position Data — the deck was discovered, but no status packets are arriving.
• DJM: waiting for bridge data — the mixer side was discovered, but no fader data is arriving.
• Pro DJ Link paused — the outputs are correctly reporting they have nothing to send, because nothing is coming in.

So the chain is blocked at the very first step. This is also why the Track Map didn't help: the Track Map maps a track once STC knows which track is playing, and right now STC isn't being told that. Nothing you configure downstream can work around it. This is not a mistake on your side.

Three things worth ruling out first

These are quick, and any one of them would produce exactly what you're seeing:

1. How is the XZ playing the music? If you're using it as a controller for rekordbox or Serato on a laptop, the tracks are playing in the software, not on the XZ's own decks — and there may be no deck status to publish over Pro DJ Link. To have the XZ act as a Pro DJ Link player, it needs to be playing standalone, from a USB drive with rekordbox-analysed tracks (or via Link Export).
2. Is rekordbox running on the same computer as STC? It binds the same network ports, and the two will compete. If rekordbox is open, close it entirely and restart STC.
3. How is the computer cabled to the XZ? Which port did you use? There are reports of odd behaviour when the XZ's link ports are all patched into the same switch.

If none of that changes it

Then this is very likely the same underlying issue I'm currently working on for the CDJ-2000NXS2: the device doesn't accept STC's network identity, so it never starts sending unicast data. Discovery works, everything else stays silent — which is precisely your symptom set.

I don't have an XZ, so I can't reproduce this here. What would genuinely move it forward is a Wireshark capture:

• Connect the computer to the XZ as you normally would, and start capturing on that network interface.
• Start STC, let it run for a minute or two with a track loaded and playing on the XZ.
• Stop the capture and attach the .pcapng here (or email it if you'd rather not post it publicly).

That shows me exactly what the XZ is and isn't sending, and what it makes of STC's announcement. Packet captures are how every hard problem in this project has actually been solved — I don't guess at protocol behaviour, so a capture is worth more than any amount of speculation from me.

No pressure or timeline on this at all — only if and when you have the time and the gear in front of you. Either way, thanks for reporting it with this much detail.

[elevate5406]

Hi, I've managed to get a capture.
https://drive.google.com/file/d/1C_PvbbuzepUjPrghbOhyogsNgOjB_Iz6/view?usp=sharing

I Hope It Helps.

If you need another one, feel free to ask.

[fiverecords]

Thanks for the capture. Looking at it, it seems STC and the XDJ-XZ are not on the same network — the PC shows up as 169.254.220.211 while the XDJ is at 192.168.0.108, and I don't see any traffic between them. Could you check the IP settings on both ends so they're on the same subnet, and try again?
Also, if you have the official PRO DJ LINK Bridge, a capture of it working with your XDJ would help me a lot — it would let me see how it communicates with this hardware and check if there's anything else that needs adjusting on my side.
If it still doesn't work after fixing the network, send me a new capture and I'll take another look.

[elevate5406]

Hi, I've got news.
I've managed to get the XZ working by changing the IP Address of the PC to the Subnet of the XZ. Now I'm at the exact problem with the NXS2, where the PDL view doesn't really work (Waveform isn't shown). Timecode triggers though. The Audio also doesn't work as good. Like mentioned with the NXS2.

Here's another Wireshark Capture after the IP Change: https://drive.google.com/file/d/1EXgDqWKoWx7-aPoGOtv_W23-LdBHQbVr/view?usp=sharing

Also, now the XZ comunicates with the Pro DJ Link Bridge Software.

Are there anymore things I can do to help you?

In the meantime, I'm trying to figure out how get the Trackmap working.

[fiverecords]

Thanks again for the captures — they've been really helpful. I'm attaching a test build with some changes based on what I found in yours. No need to change any settings, the defaults are fine for your setup.

If you can, load a track on both decks, play around with them for a minute or two, and take a new capture like before. That will tell me whether the two-deck handling and the track data requests are behaving better now.

And if you get the chance to capture the official Bridge working with the XZ (with a track loaded and the waveform showing), that's still very useful for comparison.

STC.-.V1.9.11-Beta19-.WIN.zip

[fiverecords]

The XZ changes are in the release that just went out, so you can move off the
test build.

What your captures showed, for the record: the XZ announces itself as a
single device but sends deck data for two player numbers, and STC was only
tracking one of them because discovery ran off the announcement alone. It now
picks up the second deck from its data stream. Separately, the track
information requests were being sent with an identity belonging to the XZ's
own other deck, which the unit silently ignores — that was why the waveform
stayed blank. Both fixed.

Whether the track data now comes through on your unit is the part I can't
verify here, so if you get the chance to run it with a track on each deck I'd
like to know. And that capture of the official Bridge with the XZ is still
welcome whenever convenient — it would let me compare directly rather than
infer.