Free forever·no account, no tracking, no third-party requests ·open data, free API
showstack / field

The field card

Everything here is something you type or read while standing in a venue with somebody waiting. It is one page, it works offline once this site is saved, and it is ordered the way you should actually work rather than alphabetically.

One rule before any of it. Run the command, then read what it actually says, then decide. Almost none of the time wasted in a machine room goes on running the wrong command. It goes on running the right one and not reading the output.

Work in this order

Bottom-up. Each step is cheaper than the one after it and rules out more.

1

Physical

Link light. Both ends. Then the cable, by swapping it for a known-good one.

Thirty seconds, and it rules out the largest fault family there is.

2

Addressing

Address, mask, and whether the two devices agree about which network they are on.

ipconfig / ifconfig on both, then arp -a. Most of the rest of the faults live here.

3

Reachability

Ping. Then trace, if it crosses anything.

Now you are testing the path rather than guessing at it.

4

Protocol

Right universe, right port, right multicast group, subscriptions actually joined.

Everything pings and nothing outputs: this is the layer.

5

Software

Versions, licences, firewall, the application itself.

Last. Reinstalling first is forty minutes you will not get back.

The four commands to know by heart

With what the output means, which is the half that gets skipped.

What is my address?

Windowsipconfig /all
macOSifconfig
Linuxip addr

IPv4 address, subnet mask, default gateway. A 169.254 address means DHCP failed and the machine named itself.

IPv4 addressWho this machine is.169.254.x.x means nobody answered the DHCP request.
Subnet maskHow much of that address is the network.A mask that disagrees with the other device is the fault.
Default gatewayWhere anything non-local is sent.Blank is normal on a show network, and fine.
Physical addressThe MAC — the hardware identity.This is the number the switch actually learns.

Four lines, and only four. Everything else in that output is noise while you are standing up.

Can I reach that device?

Windowsping 10.0.0.50
macOSping 10.0.0.50
Linuxping 10.0.0.50

Replies with a time. "Destination host unreachable" is your machine giving up locally; a timeout means it left and nothing came back — different faults.

Replies, times low and steadyIt is there and the path is healthy.
Replies, times all over the placeThe path is congested.That is jitter, measured. Write the number down.
Request timed outIt did not answer.It may still be there and firewalled. Not proof of absence.
Destination host unreachableYour own machine does not know how to get there.Check your mask before you touch anything else.

Ping proves reachability, not correctness. A node that pings and does not output is a normal Tuesday: the address is right and something above layer 3 is wrong.

Where does the traffic actually go?

Windowstracert 10.0.0.50
macOStraceroute 10.0.0.50
Linuxtraceroute 10.0.0.50

Each hop with its time. A hop that suddenly jumps by tens of milliseconds is the one to ask about. Stars mean that hop declined to answer, not that it is broken.

One hopNormal on a flat show network.
Several hopsSomething that should be local is being routed.Somebody has put a router in the path. That is the finding.
Stars, then it continuesThat hop declined to answer.Not a fault. Plenty of devices refuse to reply and forward perfectly.
Stars, and it stopsThat is where it dies.Now you know whose problem it is before the conversation starts.

What is on this network?

Windowsarp -a
macOSarp -a
Linuxip neigh

Every address this machine has spoken to recently, with its MAC. The first three MAC pairs identify the manufacturer, which is often enough to name an unlabelled box.

Two IPs, one MACOne device answering to two addresses.
One IP, changing MACTwo devices claiming the same address.The classic: intermittent, both affected, either works alone.
Nothing at allYou have not talked to anything yet.The table only lists what this machine has recently spoken to.

This is layer 2, and it finds the duplicate-address fault that nothing at layer 3 can name.

The rest, worth knowing exist

Look these up. Knowing there is a command for it is the useful part.

Which way out is it using?

Windowsroute print
macOSnetstat -rn
Linuxip route

The default route. Two default routes — a wired show network and wifi — is the classic reason traffic vanishes into the wrong interface.

What is listening on this machine?

Windowsnetstat -ano
macOSnetstat -an
Linuxss -tulnp

Local address and port. 0.0.0.0 means every interface; 127.0.0.1 means loopback only, so nothing else can reach it however good the cable is.

Is that port open on the far end?

WindowsTest-NetConnection 10.0.0.50 -Port 5568
macOSnc -vz 10.0.0.50 5568
Linuxnc -vz 10.0.0.50 5568

Succeeded or refused. Refused means something answered and said no; a timeout means nothing answered at all, which usually means a firewall rather than a closed port.

What multicast groups has this machine joined?

Windowsnetsh interface ipv4 show joins
macOSnetstat -g
Linuxip maddr show

sACN groups look like 239.255.x.x. If a receiver has not joined the group, no amount of correct sending will reach it.

Is the name resolving?

Windowsnslookup device.local
macOSdscacheutil -q host -a name device.local
Linuxdig device.local

The address it resolved to. On a show network with no DNS this is expected to fail — use the address.

How much can this link carry?

Windowsiperf3 -c 10.0.0.50
macOSiperf3 -c 10.0.0.50
Linuxiperf3 -c 10.0.0.50

Bitrate and retransmits. Retransmits on a supposedly quiet gigabit link mean a duplex mismatch or a failing cable, and they will ruin audio long before they ruin a file copy.

What is actually on the wire?

WindowsWireshark
macOSsudo tcpdump -i en0 udp port 5568
Linuxsudo tcpdump -i eth0 udp port 5568

The packets themselves. Filter to the port you care about first — an unfiltered capture on a show network is unreadable within seconds.

Addresses that are a diagnosis

Some addresses are not configuration. They are the machine telling you what went wrong.

0.0.0.0/8This network — Not a usable host address. Seen as a source before a device has one.
10.0.0.0/8Private, large — Sixteen million addresses. The usual choice for a show network with room to grow, and for anything with VLANs in it.
127.0.0.0/8Loopback — The machine talking to itself. Never leaves the network card, so a service reachable only here is not reachable at all.
169.254.0.0/16Link-local (APIPA) — DHCP failed and the device named itself. It can reach others that did the same, on the same wire, and nothing else. This is a diagnosis, not a configuration.
172.16.0.0/12Private, medium — A million addresses. Less commonly used, which is occasionally a reason to pick it — fewer clashes when two networks meet.
192.168.0.0/16Private, small — Sixty-five thousand addresses, and the default on nearly every consumer router — which is why it is the range most likely to collide when a laptop brings its home network habits to site.
100.64.0.0/10Carrier-grade NAT — Your internet provider is sharing one public address across many customers. It behaves like a private range and it is not yours to use on a local network.
224.0.0.0/4Multicast — A group rather than a host. Nothing is assigned this; devices subscribe to it. sACN uses 239.255.x.x, and this whole range needs IGMP snooping on the switch to behave.
240.0.0.0/4Reserved — Set aside and never allocated. If you see one, something is misconfigured or making it up.

169.254.x.x is the one to recognise instantly. It is not an odd but working configuration. It is a device reporting that it asked for an address and got silence: no DHCP server, no link, or the wrong VLAN. The fix is always upstream. Check an address →

Numbers worth carrying in your head

The test is not whether a number is useful. It is whether having to look it up would cost you the moment. Everything else is a calculator, and is linked to one.

Sound

Speed of soundSo about 3 ms per metre. Temperature moves it ~0.6 m/s per °C. 343 m/s at 20 °Ccheck →
Inverse square lawFree field. Indoors the room refills part of it. −6 dB per doubling of distancecheck →
One bit of depth16-bit ≈ 96 dB, 24-bit ≈ 144 dB. ≈ 6 dB of dynamic rangecheck →
Audible rangeSampling at 48 kHz gives 24 kHz of it. 20 Hz – 20 kHz, nominallycheck →

Data

Bits to bytesNetworks are bits, storage is bytes. 1 Gbit/s = 125 MB/s. Divide by 8check →
8 bitsWhich is why one DMX channel has 256 levels. 256 valuescheck →
16 bitsCoarse × 256 + fine. Why a moving head needs a fine channel. 65,536 valuescheck →
Uncompressed 1080p60Will not fit on a 1 Gbit link. This is the whole argument for compression. ≈ 3 Gbit/scheck →
64 channels of 48 kHz/24-bit audioAudio is small. Video is not. People reliably guess this backwards. ≈ 74 Mbit/scheck →

Lighting data

One DMX universePlus a start code, so 513 slots on the wire. 512 channelscheck →
DMX refresh, full universeA full frame takes about 23 ms and cannot go faster. ≈ 44 Hz maximumcheck →
RS-485 unit loadsAn electrical limit, not a DMX one. Over budget works on the bench. 32 maximum on one linecheck →
DMX cableNot microphone cable. It works until the run is long and the rig is hot. 120 Ω, terminatedcheck →
sACN, 40 universesLighting control is tiny. It is the media on the same switch that is not. ≈ 10 Mbit/scheck →

The network

The nine mask octetsA mask is a solid run of ones. 200 can never appear in one. 0 128 192 224 240 248 252 254 255check →
Usable hosts in a /262^(32−26) − 2. The two are the network and broadcast addresses. 62check →
Block sizeThe whole subnetting method in one line. 256 − the mask octetcheck →
169.254.x.xThe single most useful number on this page. It is a failure report. DHCP failedcheck →
Ethernet frame, standardA ping at 1472 bytes finds the MTU problems a small ping walks past. 1500 byte MTUcheck →

Power

Watts to amps, single phase2300 W on a 230 V circuit is 10 A. W ÷ Vcheck →
Watts to amps, three phasePer line conductor, not the total. W ÷ (1.732 × V)check →
Voltage drop limitConventions from installation practice, not one global rule. 3% lighting, 5% powercheck →
PoE+ at the deviceThe port may source 30 W. The difference is the cable. 25.5 W guaranteedcheck →
Everything a rack drawsNear enough all of it. The light and sound leaving are a rounding error. ends up as heat in the roomcheck →

Time

Frame at 60 fpsEvery stage of the pipeline spends part of that same budget. 16.67 mscheck →
Frame at 24 fps 41.67 mscheck →
29.97 drop frameTwo per minute except minutes divisible by 10. Skips frame NUMBERS, not timecheck →
Perceptible audio/video offsetEars forgive early sound far less than late. ≈ 45 ms audio late, 125 ms earlycheck →
A number you have had to look up mid-show?

That is the test this page is built on, and the only way to find them is for somebody to have been caught out. Name it and it goes on the card.