Contribute
Several of these tools exist because somebody put a laptop on a mirror port and read a protocol nobody had bothered to document. That only works for kit I can get my hands on, and there's an awful lot I can't. If you've got one of the devices below, a capture of it just working is worth more than any bug report.
Read this before you capture anything
A packet capture isn't 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 through it before you send it, and assume anything in it is something you're choosing to disclose. Captures I accept are stored privately and are never published or committed to a public repo. If a capture is behind a published protocol document, the document gets published and the capture doesn't.
Nothing gets uploaded from this page. You tell me what you've got, and if it's something I can use you'll get a reply with a one-time link.
These are specific: each one names hardware I don't own, or traffic I can't generate here.
Control traffic from any Dante-enabled preamp I haven't got on the bench, which is 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 I need.
Yamaha MBCShure ACNDante control
Discovery and telemetry from receivers I 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. And receiver discovery on a network with mixed vendors, where two vendors' discovery protocols share a segment: the case hardest to reproduce here.
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 I 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 I haven't validated against, which is 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 I don't own, especially a full preset recall round-trip.
Analog Way TCP controlAWJ
If it's a Dante network, strip the audio first
A Dante capture is almost all audio. One of mine was 1.7 GB, 99.9% of it audio flows, which is far more than any file transfer here will take. Filtering out the audio ports took it down 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 you send it. It makes the capture smaller and quicker to work with, and takes out the one part most likely to be a client's actual show.