Why it behaves like that
40 explainers, arranged as one chain — the mechanism drawn moving, so the rule stays with you after you close the tab. The index tells you what a thing is; the tools give you the number for tonight; this is the part in between that nobody writes down.
They are arranged as one chain, because that is what they are. Something physical becomes a signal, the signal survives a wire, a network and the air, it becomes something in a room, it agrees with other systems about time and space, and it finally arrives at a nervous system — which is the only part of it that was ever the point. The last stage is the machines we built to imitate that nervous system, which is the right place for them.
Experience architecture
What you do with the whole chain when the job is not "make the signal arrive" but "make something happen to a person over ninety minutes". Attention, arousal and expectation as materials — and why the peak and the ending are the only two moments that survive.
- Built on the index
- Every claim links to the protocol, standard or term it comes from, so you can go from the explanation to the citation in one click.
- Interactive, not decorative
- Drag the prefix, terminate the line, switch the access method. The figures are the thing being explained, not an illustration of it.
- Written from load-in
- Each page ends with what actually goes wrong when the rule is ignored — the failure you would otherwise learn about in front of an audience.
Foundations
How something physical becomes a signal, how that signal is written down as numbers, how it survives a wire, and what the plug on the end of it actually carries.
Before there was a computer in it
What a resistor, capacitor, transformer and transistor actually do; how an analogue console controlled a rig with no memory and no processor; how an amplifier is built; and why a CD, a DVD and a Blu-ray are the same disc holding 0.7, 4.7 and 25 gigabytes.
Turning the world into a voltage
Dynamic and condenser microphones as signal problems and what phantom power actually feeds; why a balanced line rejects interference; what a ground loop is; and why an absolute encoder is a safety decision rather than a resolution one.
Numbers that stand for signals
Sample rate, bit depth and 6 dB per bit — the same fact that explains 24-bit audio and 16-bit fixture control. Then the short list of arithmetic behind every delay, reverb, filter and distortion you have ever used.
How a colour becomes a number
What #ffffff actually is and why colours are written in base 16, why 128 is not half the light, what a colour space adds that the numbers cannot, and the round trip from photons to code values and back to photons.
How a one gets down a wire
A receiver has no clock of its own, which is the whole reason line codes exist. Manchester, NRZI and block codes; parity, checksum, CRC and forward error correction; and why almost every show protocol chooses UDP.
The same plug is not the same signal
Connector, pinout and protocol are three independent layers. What a USB-C port really carries in each mode, why Thunderbolt and DisplayPort share a socket but only work one way round, and the show connectors that catch everybody once.
The signal
What happens on the control bus, on the network, in the air and on the crew's headsets — and why each one fails in its own characteristic way.
DMX on the wire
Why the limit is 32 unit loads and not 32 fixtures, what a terminator actually does, and why an unterminated line fails intermittently rather than completely.
Show networks
What QoS is actually protecting on an entertainment network, how to read a subnet mask without memorising tables, and why multicast floods a switch that is not told otherwise.
Sharing the airwaves
Simplex, half duplex and full duplex; how FDMA, TDMA, CDMA and OFDMA divide the same spectrum differently; and what WMAS changes about packing radio mics into a band.
Which radio, and why
LoRa, Bluetooth LE, Zigbee, Wi-Fi, UWB, CRMX and cellular all answer the same three-way trade between range, data rate and battery differently. Plus what 2G through 6G actually changed, and why a GNSS antenna on site is usually feeding a clock.
Why the picture is black
The three negotiations a video chain has to pass before a single pixel moves, why every one of them fails the same way, and why a frame-timing offset that is invisible on one screen is unmistakable across a seam.
Getting the crew to hear each other
Partyline, matrix, IP and wireless intercom; why a walkie-talkie is not an intercom and never becomes one; what latency does to a cue call; and the licensing question nobody asks until a show travels.
The room
Turning a signal into something an audience experiences, and drawing it accurately enough that other departments can trust you.
Measuring and aligning sound
How a transfer-function measurement is actually taken, how to time-align a delay speaker, what separates a point source from a line array, and why the inverse square law is 6 dB.
Putting a sound somewhere
Polarity is a sign flip and phase is a time relationship that differs at every frequency, so a button fixes one and not the other. What a square, saw and triangle are actually made of. And four ways of placing a sound in a room that fail differently — by moving, by frequency, by order, and by whose head it was measured on.
Estimating beams and blends
Beam angle against field angle and why a data sheet flatters the fixture, how to size a beam before you rig it, and the assumptions a projection blend quietly depends on.
Making air visible
A beam is invisible in clean air — what you see is particles scattering it sideways, and their size decides everything. Why haze reveals a beam without fogging the picture, why low fog comes back a minute later, what the exposure standards do and do not cover, and the pyrotechnic vocabulary.
Designing something an audience accepts
Perception is a prediction machine rather than a camera, so an illusion is a plausible story the eye is allowed to finish. The contrast ratio that decides whether a Pepper’s ghost reads as solid, why forced perspective collapses for the front row, and what attention actually follows.
Drawings, models and BIM
The difference between a line and an object that knows what it weighs — and why that difference is what makes automatic paperwork, load calculation and a patch that nobody retyped possible.
Power, earth and the things that trip
Why three phases cancel and what stops them, why a neutral full of LED fixtures can carry more than any phase, and why the device that protects a cable and the device that protects a person are not the same device.
Why the shadow is blue
Emitters add spectra and filters multiply transmissions, and every surprise in stage colour follows from that: why a deep colour on a CMY fixture is a dim one, why a red costume goes black under green, why two sources cast two coloured shadows, and why the camera disagrees with your eye.
When the venue is a field
Wind force goes with the square of speed, air gives its water back on a schedule set by temperature rather than rain, and an IP rating describes a sealed laboratory assembly rather than your deck at 4pm. The three outdoor facts that are worse than they look.
Hoists and the safety chain
What D8, D8 Plus and C1 actually permit and where those words come from; what a safety relay does that a stop button does not; the standards behind an emergency stop; and how far a load keeps moving after somebody presses it.
The system
Several technologies behaving as one thing. A shared clock, a shared coordinate system, and what happens when either is assumed rather than agreed.
How it all runs together
One familiar system pulled apart — Google Maps — then four show systems built the same way: tracked followspots, an LED volume, AR and XR, and the timecode spine that holds a stadium together.
What is actually in a timecode frame
An LTC frame is 80 bits and only 26 of them are the time, stored as BCD behind a sync word that cannot occur anywhere else. MTC sends the same value four bits at a time and is always two frames behind. Drop frame drops numbers, not frames. And MIDI framing is one bit.
Drone shows and pyro
Nobody flies a drone show. Every aircraft flies a pre-computed path against a shared clock, corrected to centimetres by RTK. Pyro works the same way, one bus and one timecode — with the safety chain deliberately outside it.
What you build with
Software talking to software, the languages and platforms it is written in, and the engines that draw a world sixty times a second.
Making the part that does not exist
FDM, SLA and SLS fail in different directions, and a printed part is dramatically weaker across its layers than along them — so orientation on the bed is a structural decision somebody made by pressing slice. Plus scanning, photogrammetry, and the load-path boundary that does not move.
How software talks to software
Protocol, API and SDK are three different things, and "does it have an API" is only a useful question once you know which one you are asking about. Plus when to poll and when to subscribe.
Code on a show
What actually separates HTML, JavaScript, Python, Lua, C++ and Structured Text; why determinism disqualifies most of them from moving scenery; and what TwinCAT and the IEC 61131-3 languages really are.
Node graphs and game engines
Why a Max or TouchDesigner patch is a patch bay rather than a script, and what a real-time engine is actually for — because a rendered file, however beautiful, cannot answer a camera.
The person
Every threshold in this industry is a measurement of a nervous system. What it can detect, how it works, how a feeling is built, and what makes somebody believe they are somewhere.
How each sense tells things apart
Two ears turning a 700-microsecond delay into a direction. Three overlapping cones making a colour that is not in the light. A receptor that cannot tell chilli from heat. None of it is measurement — all of it is inference from a pattern.
The person on the other end
Flicker fusion and phantom arrays, the precedence effect, the window in which sight and sound are one event, metamerism, dark adaptation — and the anticipation mechanism behind musical goosebumps.
The brain as a signal system
Every sense is a transducer and they all output the same currency, which is why brain-computer interfaces and sensory substitution work at all — and why their limits are bandwidth problems you already understand.
How a feeling is built
Emotion is not something a show transmits. It is constructed from bodily arousal plus an appraisal of what it means — which is why the same racing heart is terror in one room and joy in another, and why contrast is the only real lever.
Who the show is not reaching
Four access provisions as engineering problems with numbers attached: where the three-flashes-per-second threshold sits between two ordinary programming decisions, three assistive listening technologies that fail in different places, captioning as a latency budget, and audio description as a mix problem.
Feeling it with them
How one person’s state gets into another in an auditorium: simulation, expression contagion and entrainment — plus the two things that decide whether any of it is available, which are whether the room has held the audience and whether they can hear each other.
Being somewhere
The senses nobody counts — balance, proprioception, interoception — and how a body decides it is in a place, owns a limb, and caused a thing to happen. The mechanism a set, a room and a headset are all working on.
Machines that copy us
Each of these is an attempt to do in a tool what the previous stage does in a person: read the world, decide something about it, and act. Seeing them that way is what stops them being magic.
How a machine reads the world
A QR code that still scans with a hole in it, OCR that turns a photographed page into text, a camera that finds a face — three versions of the same trick, and all of them are engineered around a human limitation rather than a machine one.
What AI is actually doing
A network of weights that learned a mapping, run forwards. How training differs from the thing you use, why an image generator starts from noise, what a language model is predicting, and where all of it is genuinely useful on a show.
Robots, animatronics and connected things
How a machine decides where its own arm is, why a show robot is a safety case before it is a puppet, and what actually happens when a smart device joins a network — Matter, Thread, hubs, and why the cloud is a single point of failure.
This material is hand-written rather than generated from the dataset, so corrections are a pull request against one file. Open an issue and say which bit did not land — that is genuinely the most useful thing you can send.