CDJ-2000nxs2 metadata issue

[trickofdjequip]

Hello. Today we trying 1.9.0 version in full show. 2x2000nxs2 wired into switch and connected with win11 laptop at FOH through cat6 100m. Almost all the time metadata not going. ~15 minutes later metadata is loaded on 1 track.

full show.pcapng.zip

This is wire shark file writing full show.

Also our Dj have issues with 2000nxs2. Player did no react on bottons. May be this help you.

[fiverecords]

Thank you for the capture — a full show Wireshark trace is incredibly valuable. I analyzed all 37 minutes and found three bugs in STC that together explain everything you experienced.

Bug 1 — Double notify causing doubled CDJ traffic
STC sends its bridge status (0x55) from two different sockets simultaneously. The CDJ registers each source port as a separate subscriber and sends status updates to both — your CDJs were sending 10-13 status packets/sec instead of the normal 5. When STC's internal socket changed at ~minute 10, the old subscriber was never cleaned up, so ghost subscribers accumulated. This extra load contributed to both CDJs freezing for 22 seconds at the 15-minute mark.

Bug 2 — Port 65535 (invalid database port)
When STC queries a CDJ-2000NXS2 for its database server port, the CDJ sometimes returns 65535 (0xFFFF = "no service available"). STC's validation has an off-by-one error that accepts 65535 as valid, then tries to TCP connect to port 65535 — which fails. In the capture I can see 5 failed connection attempts to CDJ1:65535 at the 15-minute mark.

Bug 3 — Zombie NFS connection blocking metadata
This is probably the main reason metadata didn't work. STC opened an NFS connection to CDJ1 at startup that went idle immediately. For 10 minutes (0:16 to 9:36), both sides exchanged TCP keepalive probes every 10 seconds on this dead connection — 120 retransmission pairs. The CDJ-2000NXS2 has limited NFS connection slots, and this zombie connection was occupying one, blocking actual metadata requests from going through. CDJ2 also had NFS retransmissions with exponential backoff (2s, 4s, 8s, 16s, 32s) at minute 13-14 where STC wasn't acknowledging NFS data.

All three fixes are straightforward and will be in the next build.

One question: in the capture I also see StageLinQ discovery broadcasts (UDP port 51337) from STC at 1 packet/second throughout the session. Did you have StageLinQ configured as input on any engine? If not, that's unnecessary broadcast traffic on the CDJ network — we've also fixed this so StageLinQ now stops automatically when no engine uses it.

[fiverecords]

Please check the new version

[trickofdjequip]

Did you have StageLinQ configured as input on any engine?

no, I don't use it.

Please check the new version

I'm check new version 16.04 on CDJ-3000 and 18.04 on nxs2. ofc i'm recording wireshark captures.

Also I have one improvement request: my DJ have over 3000 tracks in collection (sic). For events he make playlists. In .xml file this look like order of track ID:

<PLAYLISTS>
    <NODE Type="0" Name="ROOT" Count="2">
      <NODE Name="TEST" Type="1" KeyType="0" Entries="5">
        <TRACK Key="57"/>
        <TRACK Key="59"/>
        <TRACK Key="61"/>
        <TRACK Key="63"/>
        <TRACK Key="65"/>
      </NODE>
      <NODE Name="2003 - Absolution" Type="1" KeyType="0" Entries="0"/>
    </NODE>
  </PLAYLISTS>

Can you integrate playlist import into track map? ofc with track order.

test_playlist.xml

[fiverecords]

Good idea, this is implemented for the next release.

When you import a rekordbox XML file that contains playlists, STC will now show a dialog where you can either pick a specific playlist or import the entire collection. If you pick a playlist, the tracks are imported into the Track Map in playlist order — so your DJ can prepare the setlist in rekordbox, export as XML, and you get the tracks in the right order for pre-programming timecode offsets, triggers, and cue points.

Thanks for the XML sample, it was very helpful for testing.

[fiverecords]

It wasn’t difficult with the base I already had, so there’s a new release with the playlist import feature.

[trickofdjequip]

Laser speed release! I trying this with my dj's collection.

So, At the upcoming show, even if there are no problems, I will still be writing Wireshark captures. May be you need another data?

[fiverecords]

Thanks! Let us know how the playlist import works with the collection.

And yes, a capture from a clean show is very valuable — it lets us verify the v1.9.1 fixes are working correctly under real conditions. If you can:

• Wireshark on the STC machine, capture on the CDJ network interface
• Let it run for the full show (or at least 30 minutes)
• Save as .pcapng, no filters needed

Thanks again for testing!