Contribute
Several of these tools exist because somebody put a laptop on a mirror port and read a protocol nobody had documented. That only works for hardware we can get our hands on — and there is a great deal of it we cannot. If you have one of the devices below, a capture of it simply working is worth more than any bug report.
Read this before you capture anything
A packet capture is not anonymous. It carries the MAC address of every device on the segment, your real IP addressing and subnet layout, device names and serial numbers, and — on an audio network — potentially the audio itself. Some of it may identify a client's venue.
So: capture on a lab or rehearsal network rather than a live client show wherever you can, open the file and look at it before sending, and assume anything in it is something you are choosing to disclose. Captures we accept are stored privately and are never published or committed to a public repo. If a capture underpins a published protocol document, the document is published — the capture is not.
Nothing is uploaded from this page. You describe what you have, and you get a reply with a one-time link if it's something we can use.
Not a general call for data. Each of these names hardware we don't own, or traffic we can't generate here.
Control traffic from any Dante-enabled preamp we don't have on the bench — anything that isn't a Yamaha Rio or a Shure QLXD. The vendor's own control app talking to the device is exactly the trace we need.
Yamaha MBCShure ACNDante control
Receiver discovery on a network with mixed vendors — the case where two vendors' discovery protocols share a segment is the one hardest to reproduce here.
Shure discoverySennheiser WSM
Discovery and telemetry from receivers we can't test against — Wisycom, Lectrosonics, and any Sennheiser or Shure generation beyond the ones already supported. A capture of the vendor's monitoring software finding the unit and reading its meters.
Shure discoverySennheiser WSMvendor RF telemetry
An ATEM model outside the tested set, especially one whose UVC multiview enumerates differently.
ATEM UDP
Bulk provisioning against more than a couple of frames at once, which is the case we can only simulate here.
ATEM UDP
A session against an ATEM model not in the support matrix — Constellation, or any 2 M/E frame. The connection handshake plus a few switches is enough.
ATEM UDP
Control traffic from Analog Way frames we haven't validated against — anything outside LiveCore and Midra. The vendor console performing a preset save and recall is the highest-value sequence.
Analog Way TCP controlAWJ
As openrcs: sessions against frame generations we don't own, especially a full preset recall round-trip.
Analog Way TCP controlAWJ
A Wireless Systems Manager or Wireless Workbench session against real receivers, including the discovery handshake at the start. The bridge is written from two captures on one lab network; a third vendor would widen it considerably.
Sennheiser WSMShure WWB
If it's a Dante network, strip the audio first
A Dante capture is almost entirely audio — one of ours was 1.7 GB of which 99.9% was audio flows, far over what any file transfer here will take. Filtering the audio ports out took it to 1.6 MB without losing a single control message:
tcpdump -r raw.pcapng -w control.pcap 'not (udp portrange 14336-14591)'Do this before sending. It makes the capture smaller, faster to work with, and removes the one part of it most likely to be a client's actual show.