Broadcast Production 101
Introduction
A broadcast is a room full of people making one picture. Eight or ten specialists, each holding one job, sitting close enough to hear each other, turning twenty live sources into a single feed that somebody watches on a sofa four hundred miles away. Nobody in that room can do the job alone and nobody in it is watching the whole show except one person.
This book is about the room. Not the camera, not the desk, not the microphone -- those have their own books. This is about the chain those things sit on, the seats around you, the running order everybody works from, and the stream of calls that binds it together while it is happening and cannot be stopped.
What this book covers
What broadcast is, and the ways it is not a live event. The signal path from camera to transmission, and where master control sits on it. The control room, and why the whole team is put in one room. Every seat -- director, technical director, audio, graphics, replay, producer, engineering -- and what each one needs from you. Comms, partylines and IFB, and the accident you can cause by talking on the wrong one. The rundown. Calling the show, and the ready-then-take rhythm that keeps a fast show out of chaos. Counting, back-timing and a hard out. Graphics and replay. Broadcast audio, mix-minus and loudness. Studio against outside broadcast against REMI. Reference, genlock and the clock in an IP plant. Redundancy, the clean feed, and what happens when something fails while the audience is watching.
Who it is for
Somebody who can already do one AV job -- camera, audio, a switcher, cabling -- and is about to work in broadcast for the first time. You do not need to have been in a gallery. You do need to be willing to sit still, listen to a headset and do exactly one thing well while several other people do theirs.
Where this book sits
Video Switching Fundamentals teaches the desk the technical director drives. Camera Basics teaches the lens. Audio Basics teaches the mix. This book teaches the room those all meet in: what the chain is, who sits where, and how a live show is actually run. It is a map. It is meant to make every one of those specialisms legible, and then hand you to them.
How to Use This Book
This book is a map of a room. It is worth knowing how it is laid out before you walk into one, because the chapters are ordered the way a show is: what the thing is, what the chain is, who sits where, how they talk, what they work from, and what happens when it breaks.
The shape of every chapter
Each chapter opens with what it is for, then works through the thing itself, then turns to what goes wrong and how to find it. The what-goes-wrong sections are not filler. Broadcast is a trade where the faults are a short, well-known list, and knowing the list is most of what separates somebody useful from somebody standing still.
Every chapter ends with something to do and something to check. Do them. A broadcast control room is one of the few places in AV where you cannot learn by watching, because the whole point is that everyone is busy at once.
Keep a notebook
Start one today. Broadcast runs on details that nobody will repeat for you -- which partyline the replay operator is on at this facility, what the house calls the clean feed, which camera is the safety shot on this show, the number the producer counts down from. Write them by hand as you meet them.
Two pages earn permanent space. One is a list of the facilities and trucks you have worked in and what is odd about each, because you will go back. The other is the running list of things that went wrong and what fixed them, which is how a fault you have seen once stops costing you an hour the second time.
A note on the words
Broadcast vocabulary is regional and inconsistent. A control room is a gallery in Britain. A rundown is a running order. A vision mixer is both a person and a machine depending on which side of the Atlantic you are standing on, and in America the machine is a switcher and the person is a technical director. IFB, talkback and interruptible foldback are the same idea. This book uses the words most widely understood and names the alternatives where they matter, because the first day is hard enough without a vocabulary problem.
A note on safety
The hazard in this discipline is not weight or electricity, though both exist around a truck. It is that the show is live and being watched, and the pressure of that makes people move fast near things they should not move fast near -- cable runs at a stadium, a truck ramp in the rain, a studio floor with a camera on a pedestal coming the other way. The rule that keeps you safe is the same one that makes you good in the room: know where you are supposed to be, and be there.
The other hazard is your voice. A live microphone and an open partyline have ended careers. Assume both are open.
What Broadcast Production Is
Broadcast is the live production you already know, with the audience moved out of the room and the margin for error removed with them.
Broadcast turns many live sources into one polished feed for an audience that is not in the room.
Broadcast vs live events
Broadcast production creates a single finished video-and-audio feed for an audience watching remotely -- on television, online, or on a stream -- rather than (or as well as) a crowd in the room. Where a live event serves people present, broadcast serves the viewer at home, which changes everything: the show is built for the camera, every shot and graphic matters, and the output must be continuous, clean, and reliable because millions may be watching with no second chance.
Almost everything in broadcast is the live production skills you have learned, raised to a higher standard and tightly coordinated. Cameras, switching, audio, graphics, and coordination all feed one polished result. What makes broadcast distinct is the discipline: a defined chain, defined roles, and a director orchestrating it all in real time.
The broadcast signal path
A broadcast is a signal chain like any other, scaled up. Cameras and other sources feed a switcher (the vision mixer), where the director's chosen shots are cut together. Graphics and replay are layered in. The combined programme goes through master control and processing -- where it is finished, levelled, and checked -- and then to transmission or streaming, the path that carries it to the audience. Audio runs in parallel, mixed and embedded with the video.
Understanding this path tells you where every role and piece of gear fits. The camera operator feeds the switcher; the graphics operator feeds the switcher; the switcher's output becomes the programme that goes to air. As always, problems are traced along this chain -- and in broadcast, with an audience watching live, calm tracing under pressure is essential.
The audience is not in the room
A live event serves people who are present. They can look around. If a camera misses a moment, the crowd still saw it, and the show carries on. Broadcast serves somebody who is not there and can only see what you send them. If the shot is wrong, that is the event, as far as they are concerned. There is no looking around.
That single fact drives everything else in this book. The show is built for the camera rather than the room. Every shot matters because it is the only one. The output has to be continuous, because a gap is not a pause -- it is a fault, and it looks like a fault to everybody watching. And the whole thing has to be clean, because polish is the baseline expectation of the medium rather than a bonus.
Raised standard, tighter coordination
Almost nothing in broadcast is a new skill. Cameras, switching, audio, graphics, communication -- you have met all of it. What changes is the standard each is held to and how tightly they are coordinated.
A corporate event will survive a soft shot, a late graphic and an audio level that drifts. A broadcast will not, because there is nothing else for the viewer to look at and nothing else for them to listen to. The same crew doing the same jobs to a higher standard, all driven from one seat, is what broadcast actually is.
What makes it distinct
Three things, and they recur throughout this book. A defined chain, so that every source and every fault has a known place on it. Defined roles, so that when something is called, exactly one person answers. And a director orchestrating both in real time, continuously, for the length of the show.
Live events have all three loosely. Broadcast has them tightly, and the tightness is not bureaucracy. It is the only way a dozen people make one picture without talking over each other.
What this costs, and what it gives back
It costs flexibility. A broadcast is planned, timed and rehearsed in a way most live events are not, and the plan is a document everybody works from rather than a conversation. It costs tolerance for improvisation: the moment to invent something is not while the programme is on air.
What it gives back is that a well-run broadcast is a whole crew performing together in real time, and there are not many jobs like that. Being a dependable member of that crew, in any seat, is a capability that travels -- to sport, to news, to corporate streaming, to anything with a camera and a deadline.
Live event against broadcast
| Live event | Broadcast | |
|---|---|---|
| The audience | In the room, can look around | Not there, sees only what you send |
| A missed moment | The crowd still saw it | It did not happen |
| A gap in output | A pause | A fault, and it reads as one |
| The standard | Good enough to carry the room | Polished, because there is nothing else |
| Coordination | Loose, conversational | Tight, defined roles, one caller |
| The plan | A conversation | A rundown everybody works from |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A shot is held too long because nobody called the next one | Treating broadcast like a live event, where the room covers the gap | Somebody is always a step ahead of the rundown. Usually the director; on a small show it might be you |
| The stream stops and nobody notices for two minutes | Nobody is watching the output as output | One person, one screen, watching what the audience sees, all the time |
| The show looks fine in the room and wrong on air | Built for the people present rather than for the camera | Judge every decision on the programme monitor, not on the stage |
Practice it
You do not need a control room for this one. You need a broadcast and an hour.
- I can say in one sentence why broadcast cannot have a gap.
- I know the show is built for the camera, not for the room.
- I expect a defined chain, defined roles and one person calling.
- I know which seat I am sitting in and what it is responsible for.
- I have a notebook.
The Signal Path
Every role in this book and every fault you will ever chase sits somewhere on one line that runs from a lens to a viewer. Learn the line and the rest of the room becomes readable.
The line, end to end
Cameras and other sources feed a switcher. The director's chosen shots are cut together there. Graphics and replay are layered on through the switcher's keyers. The combined programme leaves the switcher and goes to master control, where it is finished, levelled and checked, and from there to transmission or to a stream. Audio runs alongside the whole way, mixed separately and embedded with the picture.
That is the entire chain, and it is worth being able to draw it from memory. Every piece of equipment in a broadcast facility is on it somewhere, and so is every person.
Sources are more than cameras
A source is anything the switcher can select. Cameras, certainly, but also the graphics machine, the replay server, a laptop with a presentation on it, a remote contributor arriving over the internet, a recorded package, a clean feed coming back from another facility, and colour bars.
Counting the sources is the fastest way to understand the size of a show. A four-camera corporate stream and a twenty-camera sports coverage are the same shape; there are just more things plugged into the left-hand side.
What master control is for
Most people new to broadcast have never heard of it, and it is the part that makes the output a broadcast rather than a feed. Master control is where the programme is checked and made continuous: levels confirmed, the picture legalised, the audio held inside the permitted range, breaks and station material inserted, and the output monitored against what is supposed to be going out.
On a small stream it might be one person with a meter and a confidence monitor. In a broadcaster it is a room with its own staff. The function is the same either way, and if nobody is doing it, nobody is watching the thing the audience actually receives.
Tracing, and why it is calmer here
A fault is somewhere on the chain, and the chain is short. Work along it in one direction and you will find the break: does the source exist at the camera, does it reach the switcher input, does it appear on the multiviewer, does it cut to programme, does programme reach master control, does master control reach transmission.
Broadcast does this under pressure, with an audience watching, which is exactly why the method has to be mechanical rather than inspired. Working the chain in order is slower than a good guess on the first attempt and very much faster on the third.
The chain, and who lives on each part
| Stage | What happens | Who owns it |
|---|---|---|
| Sources | Cameras, graphics, replay, remotes, playback | Camera ops, graphics, replay, engineering |
| Switcher | The chosen shot becomes programme | Technical director, on the director's call |
| Keying | Graphics and lower thirds layered on | Graphics operator, through the switcher |
| Audio | Sources mixed and embedded, in parallel | A1 in the room, A2 at the event |
| Master control | Finished, levelled, legalised, made continuous | Master control, or whoever is watching output |
| Transmission | To air, to the platform, to the stream | Engineering and the distribution chain |
How to do it
- Look at the multiviewer first. If the source is black there, the fault is upstream of the switcher.
- Ask the camera operator, or whoever owns that source, what they see at their end.
- Check the switcher input rather than the output -- an input that is dark and an output that is dark are different faults.
- If the source is good at the switcher and wrong on air, the fault is in what is selected, not in the signal.
- Tell the director what you have ruled out, in one sentence, and keep tracing.
- Say when you are going to touch something before you touch it.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A source is fine on the multiviewer and black on air | It is not selected, or a key is covering it, or the wrong bus is on programme | This is a switcher fault, not a signal fault. Look at what is selected |
| Everything is fine in the room and the stream is dead | The break is downstream of the switcher -- master control, the encoder, the platform | Somebody has to be watching the actual output, continuously |
| One camera is a different colour from the rest | Shading, not the chain | Engineering, at the camera control unit, not anything on the switcher |
| The picture is right and the audio is not there | Audio runs in parallel and fails in parallel | Trace the audio chain separately; the two share almost nothing but a destination |
Practice it
A pen, a sheet of paper, and any broadcast you can get near -- including a streamed meeting.
- I looked at the multiviewer before I looked at anything else.
- I know whether the fault is upstream or downstream of the switcher.
- I checked the audio chain separately from the picture.
- I said out loud what I had ruled out.
- I warned the room before touching anything.
The Control Room & Its Roles
Capture happens out there. Assembly happens in here. That separation is the basic shape of broadcast, and the reason the room is built the way it is.
A broadcast is made by a team in a control room, each owning one job, all led by the director.
The control room
The control room (or gallery) is where a broadcast is assembled in real time. It is a room of screens -- every camera, the programme, graphics, replay -- and the specialists who operate them, sitting together so they can coordinate instantly. Out at the event are the cameras and audio sources; in the control room the feeds are turned into the finished show. This separation -- capture out there, assembly in here -- is the basic shape of broadcast.
Everyone in the control room can see the same sources and hear the same comms, which is what lets a complex live show stay coordinated. The room is built so the director can call shots and the whole team can execute them together, second by second.
The roles
Broadcast runs on defined roles working as a team. The director makes the creative calls -- which shot, when, what comes next -- and is the leader of the show. The technical director (TD) operates the switcher, executing the director's calls. Camera operators provide the shots. The audio engineer (A1) mixes the sound. The graphics operator builds and triggers on-screen graphics. The replay operator captures and plays back key moments. On bigger shows there are more specialists; the principle is that each owns a clear job and responds to the director.
This is teamwork at high speed. The director calls, the relevant person responds and executes, all over comms, all live. It works because everyone knows their role, listens, and trusts the others to do theirs. A broadcast control room running well is one of the clearest examples of a coordinated crew, which is why the leadership and communication skills from the other books in this series matter here.
A room of screens and specialists
The control room -- the gallery, in Britain -- is where the show is assembled while it happens. It is a wall of pictures showing every camera, the programme, the preview, the graphics and the replay, and a row of people who each operate one of those things, sitting close enough to hear one another speak.
It looks chaotic on a first visit and it is the opposite. Everybody can see the same sources and hear the same comms, which is the only reason a dozen people can act together second by second.
Why they sit together
They sit together so that coordination costs nothing. A director who has to phone the graphics operator cannot run a show. A director who can say four words into a headset and be answered by the right person in half a second can.
This is also why the room is quiet in a specific way. The only voices are the ones doing work. Conversation that is not a call is noise on a channel somebody needs, and a gallery that is chatty during a show is a gallery that is about to miss something.
Reading the room on your first day
Find four things before the show starts and you will not be lost. Where the programme monitor is, because that is the only picture that matters. Where the preview is, because that is what is coming. Who the director is, because every call originates there. And which seat is yours and what it is responsible for.
Everything else can be learned during the show. Those four cannot.
The room is the same size everywhere
A studio gallery, an outside broadcast truck and a REMI control room look wildly different and are the same room. The same screens, the same seats, the same calls. A truck is the gallery packed into a vehicle; a REMI room is the gallery moved a long way from the event.
That is genuinely useful the first time you walk into an unfamiliar one, because the unfamiliar part is the furniture rather than the job.
What is on the wall, and what it is for
| Screen | Shows | Why you look at it |
|---|---|---|
| Programme | What the audience is receiving now | The only picture that is actually the show |
| Preview | What is set up to go next | So the next cut is not a surprise |
| Multiviewer | Every source, small, with labels | To see what is available and what is broken |
| Graphics preview | The next graphic, before it is keyed | To catch a wrong name before a viewer does |
| Replay | What the replay operator has cued | So the director knows what they are cutting to |
| Confidence / off-air | What is actually leaving the building | Because the room can be perfect and the output dead |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Two people answer the same call | Overlapping responsibility, or an unclear seat | One job, one seat, settled before the show rather than during it |
| The director is repeating themselves | Somebody is not listening on the right channel, or not acknowledging | Acknowledge every call aimed at you, briefly, every time |
| Nobody notices the stream has stopped | Everyone is watching their own source and nobody is watching output | A confidence monitor, and one person whose job includes looking at it |
| The room is loud and calls are being missed | Conversation on working channels | If it is not a call, it waits until the break |
Practice it
Best done in a real gallery, and worth doing on a streamed show if that is what you can reach.
- I found the programme monitor.
- I found the preview.
- I know who the director is and where they sit.
- I know which seat is mine and what it owns.
- I know which comms channel I am on, and which one the director is on.
- I know where the off-air or confidence monitor is.
The Seats Around You
Broadcast runs on defined roles. The value of a defined role is not tidiness -- it is that when something is called, exactly one person answers, and everybody knows who.
The director
The director decides what the audience sees and when. Which camera tells this moment, when to cut, when a graphic appears, when to go to replay, when to come out of a segment. They are the creative lead and the organisational one at the same time, which is unusual and is why the job is hard.
A good director stays a step ahead of the rundown rather than level with it, and keeps the room calm through hours of live output. The calm is not temperament. It is a working method: anticipate, warn, then command.
The technical director
The TD drives the switcher and executes what the director calls. Deciding and executing are deliberately split, and the split is what lets a show run fast -- the director can think about the next thirty seconds because somebody else's hands are on the panel.
In Britain this person is the vision mixer, and so is the machine. In America the machine is the switcher and the person is the technical director. On small shows the director does both, and the show runs slower for it.
Audio -- the A1 and the A2
The A1 sits in the room and mixes the programme. The A2 is out where the event is, putting microphones on people, fixing the one that failed, and managing what the A1 cannot reach. Two jobs, two places, one result.
Audio faults are as fatal as video faults and more noticeable, because a viewer will tolerate a soft picture and will not tolerate not hearing the speaker. Broadcast Audio later in this book is about the mix itself; here it is enough to know there are two people and where each of them is.
The graphics and replay seats
The graphics operator builds the on-screen elements in advance and fires them on a call. Almost nothing about graphics is improvised: the names are spelled before the show, the scores are wired to a data feed, the full-screens are built and checked.
The replay operator records the live feeds continuously and, on a call, plays back a chosen moment, often slowed. The hard part of replay is not playback. It is marking the moment while it is still happening, so that it can be found ten seconds later under pressure.
The people counting time, and the people keeping it alive
A producer owns the show -- the content, the running order, and whether it is working. An assistant director or production assistant frequently owns the clock, counting the room into and out of segments and keeping the rundown honest against real time.
Engineering owns the plant. The engineer in charge, the video operators shading the cameras, the people who built the chain and will rebuild it if it breaks. You will notice them most on the day something goes wrong, which is a compliment to them.
The seats, and what each needs from you
| Seat | Owns | What it needs from everyone else |
|---|---|---|
| Director | What the audience sees, and when | Acknowledge the call, then do it |
| Technical director | The switcher | Clean calls, one at a time |
| Camera operator | The shot | Notice and hold when you are on a tally |
| A1 | The programme mix | Tell them before a source makes noise |
| A2 | Microphones at the event | Tell them the moment something sounds wrong |
| Graphics | Building and firing graphics | Names and spellings, early, in writing |
| Replay | Marking and playing back | A call that says which moment, not just 'replay' |
| Producer / AD | Content and the clock | Honest timings, not optimistic ones |
| Engineering | The plant | Say what you observed, not what you concluded |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A call gets no answer | It named a job nobody in this room holds, or named nobody at all | Calls name a seat. 'Somebody' is not a seat |
| A graphic goes on air with a misspelled name | It arrived verbally, late, during the show | Names and titles in writing, before the show, checked by somebody who cares |
| Replay misses the moment | The operator was not marking while it happened | Marking is continuous. Playback is the easy half |
| Two people adjust the same thing | Undefined ownership between seats | Settle it in the pre-show, not on air |
Practice it
A show you can watch, and the seat list above.
- I know which seat I hold and what it owns.
- I know who calls me and on which channel.
- I know who I have to tell when something changes.
- I have everything I need in writing, not in memory.
- I know who to tell if I cannot do what was just called.
Comms
The room runs on who can hear whom. Get that wrong and you will either miss every call aimed at you or say something into a presenter's ear while they are live.
The partyline
A partyline -- a PL, an intercom channel -- is a shared conversation. Everybody assigned to it hears everybody else on it. The director is on one, and the seats that need to hear the director are on the same one.
Big shows use several. Production on one, engineering on another, cameras on a third, so that a cable discussion does not sit on top of the shot calls. Knowing which channels exist and which you are on is a thing to establish before the show, not during.
IFB, and the thing you can break
IFB is interruptible foldback: a feed sent to somebody on camera, usually programme audio, which the producer or director can interrupt to talk directly into their ear. It is how a presenter is told to wrap, or that the next guest is not ready.
It is also the single easiest way to embarrass a production. A presenter hears whatever goes down that channel, including things not meant for them, while they are on air and cannot react. Before you speak, know which channel you are on. Assume it is open.
Talking on comms
Short, named, and once. Name the seat, say the thing, stop. 'Camera two, tighter on the guest' is a call. 'Could we maybe get a bit tighter on the, on the guest there, camera two, if that's alright' is four seconds of a channel somebody else needed.
Acknowledge what is aimed at you. A one-word answer costs nothing and tells the director that the call landed, which is the difference between them moving on and them repeating themselves at a worse moment.
When you have bad news
Say it immediately, say what you observed rather than what you concluded, and say what you are doing about it. 'Camera three has lost its picture, I am checking the cable' is useful. 'Something is wrong with three' makes the director do your job.
Never go quiet. A seat that stops responding is, from the director's side, indistinguishable from a seat that has failed, and they will start working around you while you are still there.
Channels, and who is on them
| Channel | Carries | Who hears it | The mistake |
|---|---|---|---|
| Production PL | Shot calls, segment calls | Director, TD, graphics, replay, producer | Holding a conversation on it |
| Camera PL | Framing, moves, tally queries | Director, camera operators | Calling a camera on the wrong channel |
| Engineering PL | Faults, shading, plant | Engineering, TD | Reporting a fault where the director cannot hear it |
| IFB | Programme audio, interrupted by production | The people on camera | Forgetting it reaches somebody who is live |
| Talkback to site | Production to the A2, stage manager, floor | Crew at the event | Assuming the site hears the production channel |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| The director keeps repeating a call to you | You are not acknowledging, or you are on the wrong channel | Acknowledge every call, briefly. Confirm your channel before the show |
| A presenter reacts to something nobody said to them | It went down IFB | Know which channel you are on before you speak, every time |
| A fault is fixed and the director never knew there was one | It was reported on the engineering channel only | Anything that changes what the audience sees goes to the director too |
| Nobody can get a word in | One channel doing the work of three | Split the channels, and put conversation somewhere that is not a working one |
Practice it
A headset, or failing that, a rehearsal in your own head with a stopwatch.
- I know which channel I am on and which the director is on.
- I know which channel reaches the people on camera, so I do not speak on it by accident.
- I know how to talk to the crew at the event.
- I know to acknowledge every call aimed at me.
- I know to report what I saw, not what I assume.
Directing & Calling the Show
A rundown is the map everybody works from. Calling is how the director turns that map, plus whatever is actually happening, into one stream of instructions a room can act on.
The director turns a plan and many feeds into a coherent live show, one call at a time.
The rundown and the director
A broadcast follows a rundown (or running order) -- the planned sequence of segments, items, and timings for the show. It is the broadcast equivalent of the run of show: the map everyone works from, so the team knows what is coming. The director works from the rundown, anticipating each segment and preparing the shots, graphics, and replays it needs before it arrives.
The director is the creative and organisational leader of the live show. They decide the visual story -- which camera tells the moment best, when to cut, when to show a graphic or replay -- and they communicate it as a stream of calls. A good director sees the whole show, stays a step ahead of the rundown, and keeps the team calm and coordinated through hours of live production.
Calling the show
Calling is the director's real-time instruction to the crew, in a recognisable rhythm: a warning (ready camera two, stand by graphics), then the execution (take two, graphics go). The warning lets the responsible person prepare; the command triggers the action. This ready-then-take pattern, over comms, is how a director coordinates a fast live show without chaos, and learning to hear and respond to it is essential for everyone in the control room.
Live broadcast also means reacting to what actually happens -- a goal is scored, a speaker goes off-script, a guest arrives late. The director adapts the plan in real time while keeping the show flowing, deciding instantly what to show and calling it cleanly. This blend of following the rundown and reacting to live events, all communicated as clear calls, is the core craft of directing a broadcast.
What a rundown is
The planned sequence of the show: every segment and item, in order, with a duration against each and a note of what it needs -- which camera, which graphic, which replay, which remote. It is the broadcast equivalent of a run of show, and it is the document that lets ten people be ready for the same thing at the same time.
It is also a live document. Items move, get cut, run long. A rundown that has not changed by the end of a show is unusual, and the changes are announced rather than discovered.
Reading one, and reading ahead
Read your own column first: what does this show need from your seat, and when. Then read the item after the one you are in, because the whole discipline of broadcast is being ready for the thing that has not happened yet.
The director works two or three items ahead. If you are working level with the rundown, you are already late -- not because you are slow, but because a call arrives just before the thing it is for, and you need to have prepared before the call comes.
The ready-then-take rhythm
Every call has two halves and they are separated in time. The warning: 'ready two', 'stand by graphics'. Then the command: 'take two', 'graphics go'. The warning tells the responsible person to prepare; the command triggers the action.
This is the single most important pattern in the room, and it is why a fast show is not chaotic. Nobody is ever asked to do something instantly from cold. They are asked to be ready, and then told to go. Hearing your seat named in a warning means get your hand on it now.
Reacting when the show stops following the plan
A goal is scored. A guest arrives late. A speaker goes twenty minutes long. The director's job stops being execution and becomes decision: what do we show, right now, and how do we get back to the plan.
What they need from every other seat at that moment is the truth, fast, and no initiative. Tell them what you have. Do not start solving it in a way nobody knows about, because the one thing worse than a gap is two people fixing the same gap in different directions.
What a rundown carries
| Column | Holds | Who lives in it |
|---|---|---|
| Item | The segment, in order | Everybody |
| Duration | How long it is meant to run | Producer, AD, director |
| Source | Where the picture comes from | Director, TD, camera |
| Graphics | What has to be built and fired | Graphics operator |
| Audio | Who is speaking, what is played in | A1 and A2 |
| Notes | Anything that will surprise somebody | The seat it surprises |
The shape of a call
| Half | Example | What it means to you |
|---|---|---|
| Warning | Ready two / stand by graphics | Get your hand on it now |
| Command | Take two / graphics go | Do it, this instant |
| Acknowledgement | Standing by / yes | The director knows you heard |
| Bad news | Two has lost picture, checking cable | Said immediately, observation first |
How to do it
- Find the item in the rundown and read the note against your seat.
- Read the item after it, so the end of this one is not a surprise.
- Ask your question before the show, not during the item.
- When your seat is named in a warning, get ready and acknowledge.
- On the command, do exactly what was called -- not what you think would be better.
- If you cannot do it, say so immediately and say why in one sentence.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Somebody is always half a beat late | Working level with the rundown instead of ahead of it | Read one item ahead, always. The warning is not the moment to start |
| A call is executed differently from how it was made | Somebody improved it | Execute the call. Suggest the improvement in the break |
| The show overruns and nobody saw it coming | Durations were optimistic and nobody was counting against real time | Somebody owns the clock and says the numbers out loud |
| Two people fix the same problem in different ways | Initiative instead of reporting | Report it, then do what you are told about it |
Practice it
A rundown, real or invented, and a show you can watch.
- I have read my column for this item and the next one.
- I have everything the item needs, in front of me, now.
- I know what my warning will sound like.
- I have acknowledged that I am standing by.
- I know who to tell, and how fast, if I cannot deliver it.
Time
A live broadcast is measured in seconds against a clock somebody else set, and the clock does not care what the room would prefer.
Duration, and why it is always wrong
Every item in a rundown has a planned duration, and the sum of them is the show. In practice items run long, guests talk, and something gets cut. The rundown is a plan against which reality is continuously measured, not a prediction.
This is why somebody -- an assistant director, a production assistant, a producer -- owns the clock, and why their numbers are said out loud. A room that does not know it is four minutes heavy cannot do anything about it.
Counting the room in and out
Counts are said aloud so that everybody arrives together: 'thirty seconds to end of item', 'ten, nine...', 'coming to you in five'. The count is not decoration. A camera operator, a graphics operator and a presenter all need to arrive at the same instant, and the count is what synchronises them.
Learn to hear counts without stopping what you are doing. They are frequent, and they are the metronome the show runs on.
Back-timing, and a hard out
A hard out is a moment the show must end, set by something outside the room -- a network junction, a satellite window, a venue curfew, the start of something else. It is not negotiable and it is not approximate.
Back-timing is working backwards from it: if we must be off at the hour, and the closing sequence is ninety seconds, then we must start the close at fifty-eight thirty, and so the item before it must end by then. The room then knows what it can afford.
Making time and losing it
When a show is heavy, time is found by cutting an item, shortening one, or dropping something planned. When it is light, time is filled -- a longer look, an extra replay, a wider shot held, a question the presenter has in reserve.
Both are decisions that belong to the producer and the director. What every other seat owes them is honest numbers: how long your thing actually takes, not how long you hope it might.
The words, and what each one is asking of you
| What you hear | It means | You do |
|---|---|---|
| Thirty to end of item | The item finishes in thirty seconds | Be ready for the next one |
| Coming to you in five | Your seat is about to be live or needed | Be there at zero, not after |
| We are heavy | The show is running long | Expect a cut; do not add anything |
| We are light | The show is running short | Expect to be asked to stretch |
| Hard out at the hour | The show must end then | Nothing after that is negotiable |
| Back-timed from the close | Working backwards from the end | Your slot may move earlier |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| The show hits the hard out mid-sentence | Nobody back-timed, or the numbers were optimistic | Back-time from the end at the start, and re-check it during the show |
| A cut lands before anybody is ready | The count was not heard, or was not given | Counts are said out loud and acknowledged, every time |
| The show runs dry with four minutes left | Nothing held in reserve | Somebody always has something in their pocket -- a replay, a look, a question |
| Every item over-runs a little and the show over-runs a lot | Optimistic durations accepted without challenge | Honest numbers at the planning stage, and a clock owner who says the truth |
Practice it
The rundown you wrote in the last chapter, and a watch.
- I know whether this show has a hard out, and when it is.
- I know the planned duration of the item I am responsible for.
- I gave an honest number, not an optimistic one.
- I can hear counts without stopping what I am doing.
- I know who owns the clock and what their voice sounds like.
Graphics, Replay & Audio
Graphics and replay are most of what separates a polished broadcast from a bare multi-camera feed, and both are built long before anybody calls for them.
The elements that turn camera feeds into a finished broadcast: on-screen graphics, replays, and clean sound.
Graphics and replay
The on-screen information: lower thirds carrying names and titles, scores and clocks, logos and idents, transitions, and full-screen elements like a table of results or a list of what is coming. They are layered into the programme through the switcher's keyers -- the same keying taught in Video Switching, driven by somebody else's machine.
Good graphics inform and clear. They appear when the thing they refer to is on screen and they go away again. A graphic that is still up when the subject has changed is worse than no graphic, because it is now wrong rather than merely absent.
Broadcast audio
The third element this chapter's title names, and the one that gets the least attention until it fails. Graphics and replay are things a viewer notices arriving. Audio is the thing they notice only when it is wrong, and then they notice nothing else.
It is layered in the same way and on the same calls -- a package played in, a remote contributor opened up, a microphone brought under a presenter who has just started talking. The next two chapters are about the mix itself and about the numbers it has to hit.
Nothing about graphics is improvised
The names are spelled before the show. The titles are agreed before the show. The scores come off a data feed that somebody configured. The full-screens are built and checked and previewed.
The commonest embarrassment in broadcast is a name misspelled on air, and it is almost always caused by the name arriving verbally, late, during the show. If you are the person who knows a name, write it down and hand it over early. If you are the graphics operator, refuse to take names by ear.
Replay, and marking while it happens
The replay operator records the live feeds continuously -- not on request, continuously -- and on a call plays back a chosen moment, usually slowed. In sport it is the goal and the foul. In other shows it is the reaction, the mistake, the thing worth seeing again.
The hard half is not playback. It is marking: noticing, while the moment is still happening, that this is the moment, and flagging it so it can be found ten seconds later with a director asking for it. An operator who is not marking continuously will not have the moment when it is wanted, and no amount of skill afterwards recovers it.
Calling for a replay
A useful call names the moment, not just the machine. 'Replay the goal' is workable. 'Replay' is not, because there have been four things worth replaying in the last minute and the operator has to guess.
The other half of the call is the way out. A replay has to end somewhere -- back to live, to a graphic, to a wide. Deciding that before you go in is what stops a show getting stuck inside a replay while something happens live that nobody is watching.
Kinds of graphic, and what each needs in advance
| Graphic | Carries | Needs, before the show |
|---|---|---|
| Lower third | A name and a title | Correct spelling, in writing, checked |
| Score / clock | Live numbers | A data feed, configured and tested |
| Ident / logo | Whose show this is | The right version of the artwork |
| Full screen | A table, a list, a message | Built, previewed and approved |
| Transition | Movement between segments | Built to the show's timing |
| Straps and tickers | Continuous information | A source for it, and a rule for when it clears |
A replay call that works
| Part | Example | Why |
|---|---|---|
| Warning | Stand by replay | The operator gets a hand on it |
| Which moment | The goal, not the save | There are several; guessing costs the shot |
| Speed | Half speed | Slowing is a decision, not a default |
| Command | Replay go | It rolls |
| The way out | Back to camera one | So the show does not get stuck inside it |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A name is misspelled on air | It arrived verbally during the show | Names in writing, before, checked by somebody who cares |
| The lower third is still up after the speaker changed | No rule for when graphics clear | Every graphic has a planned life. Somebody calls it out as well as in |
| Replay does not have the moment | The operator was not marking continuously | Marking is the job. Playback is the easy half |
| The show is stuck in a replay while something happens live | No way out was decided before going in | Call the exit as part of the call |
Practice it
Any sport broadcast, watched with a pen.
- Every name and title is in writing and has been checked.
- The data feed for scores or clocks has been tested with real data.
- Every full screen has been previewed.
- The replay machine is recording every source it needs to, now.
- Everybody knows what counts as a moment on this show.
- Every planned graphic has a rule for when it clears.
Broadcast Audio
The viewer cannot see the room. Everything the picture does not carry has to arrive in the mix, and a broadcast is judged on its sound faster than on its pictures.
A mix for somebody with no visual context
In the room, a muddy mix is survivable because people can see who is talking and fill in the rest. At home there is no room to look at. The mix has to do the work alone: the speaker clear, the atmosphere present enough to feel like a place, the played-in content at a level that makes sense against the voice.
It blends more sources than people expect. Talent microphones, crowd or ambience microphones, audio from packages and playback, effects, music, and the feeds coming back from remote contributors. All of it continuously, all of it live.
Mix-minus, and the fault it prevents
A remote contributor needs to hear the programme -- the presenter, the other guests -- so they can take part. What they must not hear is themselves, delayed by the round trip, coming back into their own ear. A person who hears their own voice a third of a second late cannot speak.
Mix-minus is the feed that solves it: everything except that contributor. One per contributor, each missing a different voice. It is the commonest avoidable fault on any show with a remote guest, and the symptom is unmistakable -- a contributor who suddenly starts stumbling over words they were saying fluently a moment ago.
Consistency is the standard
Broadcast audio is judged on evenness more than on beauty. A viewer who is blasted by one segment and straining to hear the next will change channel, and they will do it before they can tell you why.
This is why loudness is not left to taste. There are published standards, they specify a target and a ceiling, and broadcasters hold output to them. The next chapter is about exactly what those numbers are.
Audio on the chain
Audio runs in parallel with the picture from the sources all the way to transmission, and it fails in parallel too. A picture fault and an audio fault usually have nothing to do with each other and are traced separately.
In an IP plant the audio is carried by its own part of the standard -- ST 2110-30 for PCM audio -- as a separate stream from the video, which makes the parallelism literal rather than merely conceptual. It also means audio can be perfect while video is broken, and the reverse, which surprises people the first time.
What the mix is carrying
| Source | Gives the viewer | Goes wrong as |
|---|---|---|
| Talent microphones | The words, which are the show | Dropouts, handling noise, a dead battery |
| Ambience / crowd | A sense of a real place | Absent, so the room sounds dead |
| Playback and packages | Content played into the show | Levelled for the edit, not for the broadcast |
| Remote contributors | Somebody who is not there | No mix-minus, and they cannot speak |
| Effects and music | Shape and punctuation | Loud enough to bury the voice |
| Comms feeds | Nothing, to the viewer | Accidentally in the mix, which is a bad day |
How to do it
- Confirm you can hear them before anybody needs them.
- Confirm they can hear the programme.
- Confirm they are NOT hearing themselves -- ask them to speak and watch for hesitation.
- Set their level against the presenter, not on its own.
- Tell the director they are good, or exactly what is wrong.
- Keep listening. A remote that was fine ten minutes ago is not a remote that is fine now.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| A remote guest stumbles over every sentence | They are hearing their own voice delayed -- no mix-minus | Send them everything except themselves, and check it before air |
| The room sounds dead | No ambience in the mix | Crowd or room microphones, present but under the voice |
| A played-in package is far louder than the studio | It was levelled for an edit suite, not for this show | Check every piece of played-in content against the programme level before air |
| Comms audio appears in the programme | A routing mistake, and an embarrassing one | Comms and programme are kept apart by design, and checked |
Practice it
Headphones, and any broadcast with a remote contributor in it.
- Every microphone has been heard, not just seen on a meter.
- Every remote has a mix-minus and it has been tested by making them talk.
- Played-in content has been checked against programme level.
- Ambience is present and under the voice.
- Comms cannot reach the programme.
- Somebody is listening to the output, not just to the desk.
Loudness
Loudness is the one part of broadcast audio with published numbers attached, and the numbers exist because the alternative was a viewer with their hand on the volume control all evening.
Why there are rules at all
For years the complaint was the same everywhere: the programme was fine and the advertisements were deafening. Peak meters were the reason. A signal can peak at exactly the same level as another and be far louder to a human ear, because loudness is about the whole of a sound over time and peaks are about single instants.
So the industry adopted a measurement that models hearing rather than voltage, and then agreed targets in it. That is what a loudness standard is: a way of measuring, and a number to aim at.
The numbers worth carrying
EBU R 128 is the European recommendation, titled loudness normalisation and permitted maximum level of audio signals, and it asks for programme loudness of minus twenty-three LUFS with a true peak no higher than minus one dBTP. The American equivalent, ATSC A/85, uses minus twenty-four LKFS and a ceiling of minus two dBTP.
LUFS and LKFS are the same unit with different names. The one-unit difference between the two targets matters far less than the fact that both exist and both are checked. Which one applies to you is a question about the platform you are delivering to, and it is a question you ask before the show rather than after it.
What the meters are showing you
R 128 is supported by two further EBU documents, and knowing what they are stops the meter being mysterious. Tech 3341 defines loudness metering -- how a compliant meter behaves, and the difference between momentary, short-term and integrated readings. Tech 3342 defines loudness range, which describes how much the loudness varies across a programme.
In practice: momentary tells you about now, short-term tells you about the last few seconds and is what you mix against, and integrated tells you what the whole programme came out at, which is the number that is judged. Loudness range tells you whether the show is dynamic or flat.
Mixing to a target without flattening the show
A target is not an instruction to make everything the same level. A drama with quiet dialogue and loud action should have a wide loudness range; a news bulletin should not. What the standard asks is that the programme, taken as a whole, arrives at the target and never exceeds the peak ceiling.
The discipline that follows is simple and unglamorous. Watch the short-term meter while you mix, watch the integrated number as it settles across the show, and check every played-in item against the programme rather than against itself.
The standards, and what each document is for
| Document | What it is | The number |
|---|---|---|
| EBU R 128 | Loudness normalisation and permitted maximum level of audio signals | -23 LUFS, true peak -1 dBTP |
| ATSC A/85 | The American recommended practice for digital television | -24 LKFS, true peak -2 dBTP |
| EBU Tech 3341 | How a compliant loudness meter behaves | Momentary, short-term and integrated |
| EBU Tech 3342 | Loudness range -- how much a programme varies | A descriptor, not a target |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| The show is compliant and sounds lifeless | Mixing everything to the target instead of the programme to the target | The integrated number is the whole show. Individual moments are allowed to differ |
| Every played-in package jumps in level | Each was levelled for itself somewhere else | Check played-in content against the programme before air, every time |
| The integrated reading drifts over a long show | Nobody watched it after the first ten minutes | It is a running number. Look at it through the show, not at the start |
| A delivery is rejected for true peak | Mixed to the loudness target with no regard for the ceiling | They are two separate requirements and both have to be met |
Practice it
Any loudness meter -- most editing software has one -- and two pieces of audio.
- I know which standard applies to this output.
- I mixed against short-term and watched integrated settle.
- The integrated number is at the target.
- The true peak never exceeded the ceiling.
- Every played-in item was checked against the programme.
- I know that loudness and peak are two separate requirements.
Where Broadcast Happens & Putting It Together
A studio, a truck at a stadium, and a control room a continent away are the same broadcast in three different packages. The roles and the chain do not change. The logistics change completely.
From a fixed studio to a truck at a stadium to control done a continent away -- and the live show that results.
Studio, OB, and REMI
Broadcasts are produced in different settings. A studio is a controlled, fixed indoor space -- the home of news and many shows -- with cameras, lighting, and a built-in control room. An outside broadcast (OB) brings the production to an event, with the control room housed in trucks parked at the venue -- the model for sports and live events at stadiums and arenas. REMI (remote integration, sometimes called at-home production) captures the event on site but does the production back at a central control room connected over a network, saving the cost of sending a full crew and truck to every event.
Each setting is the same broadcast fundamentals in a different package. The roles, the chain, the director calling the show -- all the same. What changes is logistics: a studio is stable and repeatable; an OB is a massive coordinated load-in of trucks and cabling; REMI shifts the control room far from the event and leans heavily on networking. Knowing which model a job uses tells you how it will be staffed and run.
The live broadcast, end to end
Put it all together. Sources are captured (in studio, at an OB, or for REMI), the control room team assembles the show in real time following the rundown, the director calls shots and the TD cuts them, graphics and replay are layered in, audio is mixed clean and consistent, and the finished programme goes through master control to transmission or stream -- to an audience that experiences a single seamless show. Every skill in this book converges here.
What makes broadcast demanding is that it is all live, continuous, and watched, with a standard of polish that leaves no room for visible mistakes. That is also what makes it rewarding: a well-run broadcast is a whole crew performing together in real time, and being a dependable, skilled member of that crew -- in any role -- is a career-defining capability. This book is the map; the specialist books and real control-room time build the craft.
Glossary
| Control room / gallery | Where the broadcast is assembled in real time |
| Director | The creative and organisational leader who calls the show |
| Graphics operator | Builds and triggers on-screen graphics |
| Master control | Where the programme is finished, levelled, and checked |
| Mix-minus | A feed to a contributor of everything except their own voice |
| OB (outside broadcast) | Production from trucks at the event venue |
| Programme | The finished live feed going to air |
| Replay operator | Captures and plays back key moments |
| REMI | Capture on site, production back at a central control room |
| Rundown | The planned sequence and timing of the show |
| TD | Technical director -- operates the switcher |
| Transmission | The path carrying the programme to the audience |
Practical sign-off
Broadcast is learned in a control room. The learner maps the signal chain, identifies the roles, follows a director's calls in a role, works with graphics or replay, and contributes to a small live broadcast. A mentor signs off when the learner can reliably hold a role on a small broadcast.
- Mapped a broadcast signal chain and identified the roles
- Followed a director's ready-then-take calls in a role
- Triggered a graphic or replay on cue
- Held a role through a small live broadcast
The studio
A controlled, fixed, indoor space with cameras, lighting and a control room built into the building. The home of news, and of most shows that happen every day at the same time. The advantage is repeatability: the same room, the same rig, the same positions, week after week, so the crew can get very good at one thing.
It is also where almost everybody should learn the shape of broadcast, because nothing about the venue is fighting you while you learn.
Outside broadcast
An OB takes the production to the event. The control room lives in a truck parked outside, cameras and cable are run into the venue, and the whole thing is built and struck around somebody else's event. This is the model for sport and for large live events.
What changes is scale and logistics rather than craft. An OB is a coordinated load-in of vehicles, power, cable and people on a schedule set by the venue, and a large part of the skill of working on one is being where you said you would be with the thing you said you would have.
REMI, and moving the control room away
REMI -- remote integration, sometimes called at-home production -- captures the event on site and does the production back at a central facility, with the signals travelling over a network. A small crew goes to the venue; the gallery stays where it always is.
It is spreading because it is cheaper and because the people are already there. It leans entirely on the network being good enough, which is why the next chapter exists: a REMI show is an IP plant whether anybody in the gallery thinks about it that way or not.
Which one you are on, and what it tells you
Knowing the model tells you how the job will be staffed and run before you arrive. A studio means a fixed rig and a familiar room. An OB means a load-in, a truck and a day that starts much earlier than the show. A REMI means a small site crew, a long day for them, and a gallery full of people who will never see the venue.
It also tells you where the risk is. In a studio, very little. On an OB, the load-in and the weather. On a REMI, the connection.
Three packages, one broadcast
| Studio | Outside broadcast | REMI | |
|---|---|---|---|
| Where the gallery is | In the building | In a truck at the venue | At a central facility, far away |
| Where the crew is | All together | All together, on site | Split -- small crew on site |
| What is hard | Very little; it repeats | The load-in, the venue, the weather | The connection |
| What it suits | News, daily shows | Sport, large live events | Repeatable events at many venues |
| Day length | Show hours | Long -- build, show, strike | Long on site, normal in the gallery |
| The chain | The same | The same | The same, over a network |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| An OB crew arrives to find no power or no access | The venue schedule was assumed rather than confirmed | The load-in is a plan agreed with the venue, in writing, in advance |
| A REMI show loses the venue mid-programme | One connection, no fallback | REMI without a second path is a show with a single point of failure |
| The site crew on a REMI cannot get an answer | Comms to site was an afterthought | Talkback to site is as important as the pictures coming back |
| A studio show breaks the first time it moves | The crew learned the room rather than the job | The chain and the roles are identical everywhere. Learn those |
Practice it
Three shows you can find, one of each kind.
- I know which of the three this is.
- I know what time I am needed and what happens before the show.
- I know where the gallery is and whether I am in it.
- On an OB, I know the load-in plan and my part in it.
- On a REMI, I know who is on site and how I talk to them.
- I know what the single biggest risk to this show is.
Reference, Timing and the IP Plant
Two sources at the same frame rate can still be impossible to cut between, because a frame rate says how often a frame starts and not when. Reference is the agreement about when.
Genlock, and what it fixes
Genlock distributes one timing reference to every device that makes a picture, so they all start their frames together. A cut between two genlocked sources lands on a frame boundary that both of them share, and the output is clean.
Without it, the boundaries drift against each other and a cut lands part-way through a frame on one of them. The result is a tear, a roll or a black flash at the moment of the cut -- intermittent, because it depends where the drift happens to be, which is what makes it maddening to chase. On older plants the reference is black burst; on HD it is usually tri-level sync.
Frame synchronisers, and where they sit
Not everything can be genlocked. A remote contributor, a laptop, a feed arriving from another building -- none of them is going to take your reference. A frame synchroniser sits on that input, buffers the incoming picture and re-clocks it to the house timing.
It is a fix rather than a cure. Synchronising costs a frame or two of delay, which matters when the same person's audio is arriving by another route, and it is why lip sync problems so often start at exactly the input that needed a synchroniser.
In an IP plant the clock is a protocol
REMI and modern facilities carry video, audio and data as separate streams over an IP network rather than as SDI on coax. SMPTE ST 2110 is the suite that defines how. It matters here because of what replaces genlock: in a 2110 plant, timing comes from Precision Time Protocol, and ST 2110-10 is the part that defines system timing and definitions for the whole suite.
The practical consequence for somebody in a gallery is that PTP is now a thing that can be wrong. When it is, the symptoms are the old genlock symptoms wearing new clothes, and the person who fixes it is an engineer rather than anybody at the desk.
What else is on the wire
Two more parts of 2110 are worth knowing by name. ST 2110-20 carries uncompressed active video, which is the picture itself. ST 2110-40 carries ancillary data -- the things that used to travel in the blanking of an SDI signal, including timecode and captions.
The rest of the suite is engineering: traffic shaping, compressed essence, measurement practice, metadata frameworks. You do not need it. You need to know that a REMI show is an IP plant, that its clock is a protocol, and who to tell when the pictures start doing something inexplicable.
Timing faults, and what they look like
| What you see | What it is | Who fixes it |
|---|---|---|
| Tear or roll at the moment of a cut | Sources not genlocked | Engineering, at the reference |
| Intermittent, baffling picture faults | An unterminated reference chain | Terminate the last device |
| A source cuts cleanly but sits behind | Frame-synchronised, not genlocked | Accept it, or genlock the source |
| Lip sync out on one source only | The delay a synchroniser added | Delay that source's audio to match |
| Everything wrong at once in an IP plant | PTP | Engineering. Nothing at the desk will help |
The parts of ST 2110 a gallery needs to know
| Part | Carries | Why you care |
|---|---|---|
| OV 2110-0 | The roadmap for the suite | It tells you the suite is a suite |
| ST 2110-10 | System timing and definitions | This is where the clock lives |
| ST 2110-20 | Uncompressed active video | The picture |
| ST 2110-30 | PCM digital audio | The sound, as its own stream |
| ST 2110-40 | Ancillary data | Timecode and captions |
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| One camera tears on every cut and is fine otherwise | That camera is not taking reference | Check its reference input and the chain that feeds it |
| Reference faults that move around the rig | The reference chain is not terminated at its end | Terminate the last device, and make sure it is actually the last |
| Audio and video drift apart on one source | A frame synchroniser delayed the picture and nothing delayed the sound | Delay the audio to match, at the desk |
| An IP plant misbehaves in ways that make no sense | PTP, almost always | Report it as an observation and let engineering work; there is nothing at the desk |
Practice it
A facility you can look at, or its documentation.
- Every source that can take reference is taking it.
- The reference chain is terminated at its actual end.
- I know which inputs are frame-synchronised and expect them to be late.
- Lip sync has been checked on every synchronised source.
- In an IP plant, I know that timing is PTP and who owns it.
When It Goes Wrong
Broadcast plans for failure in a way live events often do not, because the audience is watching and the show cannot stop while somebody thinks.
Redundancy, and what it actually means
Redundancy is having a second one of the things that cannot fail. Two paths out of the building. Two power feeds. A second recorder. A backup of the show file. A spare camera that is already rigged rather than in a case.
It is not a promise that nothing breaks. It is a promise that one thing breaking does not end the broadcast, and the difference is the whole discipline. The question to ask of any part of a chain is simple: if this dies now, what happens? If the answer is 'the show stops', that part needs a second one.
The safety shot
Somewhere there is a wide shot that is always available, always framed, and always acceptable to cut to. On a football broadcast it is the wide of the pitch. In a studio it is the two-shot. It is the shot the director goes to while they work out what to do, and it exists precisely so that they have somewhere to go.
Designing a show you can recover means always having one. A show built entirely from tight shots and specials is a show with nowhere to hide when a source dies.
What to do when your thing fails on air
Say it immediately. Say what you observed, not what you concluded. Say what you are doing about it. Then do that, and keep talking if the situation changes.
What not to do is go quiet and start fixing. A director who does not know a source is gone will cut to it, and the audience will see the fault you were busy hiding. Ten words before you start work is the fastest possible fix, because it lets everybody else stop walking into it.
Recording, and the clean feed
The programme is not the only output worth keeping. A clean feed is the programme without the graphics, taken before the downstream keyer, and somebody will want it -- for a re-edit, for another broadcaster, for a version with different titles. Isolated recordings of individual cameras are the other thing people ask for afterwards.
Both have to be set up before the show, because neither can be recovered later. The question 'is it recording' has a right answer and it is not 'I think so'.
If this dies now, what happens
| Part | If it fails | The redundancy |
|---|---|---|
| The output path | The audience sees nothing | A second path, tested, not assumed |
| Power | Everything stops at once | A second feed, and UPS on the core |
| A camera | One angle gone | The safety shot, and a spare already rigged |
| The recorder | No record of the show | A second recorder, running |
| The show file | Hours of setup gone | A backup, taken today, off the machine |
| The connection on a REMI | The show ends | A second path by a different route |
How to do it
- Say it now, on the channel the director hears: what you observed, in one sentence.
- Say what you are doing: 'checking the cable', 'swapping to the spare'.
- Do not touch anything else until the director has acknowledged.
- Fix what you can fix, and keep talking if what you find changes the picture.
- Say clearly when it is back, and do not say it until it is.
- Write it down afterwards, while you still remember what actually happened.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| The director cuts to a dead source | Nobody told them it was dead | Report it before you start fixing it, every time |
| The show stops for thirty seconds while something is found | No safety shot to sit on | There is always a wide that is always available |
| The recording is not there afterwards | Nobody confirmed it was running | Confirm it, out loud, before the show, and check during it |
| A backup path has never been tried | It was bought rather than tested | An untested redundancy is a belief, not a redundancy |
Practice it
Any show you can see the chain of, real or on paper.
- I know what happens if the output path dies.
- I know what the safety shot is on this show.
- The recorders are running and somebody has confirmed it out loud.
- The clean feed exists and is being recorded if anybody wants it.
- The show file is backed up somewhere that is not the machine.
- Every redundancy has been tested, not assumed.
Holding a Seat
Everything in this book converges on one thing: being the person in a seat who can be relied on for the length of a live show. That is the whole qualification, and it is earned rather than claimed.
Tally, and the people who cannot see the gallery
A tally light tells a camera operator that their camera is live, and tells the person in front of it that they are being seen. It is a small red light doing an enormous amount of work, because it is the only channel by which somebody on camera learns they are on.
Which is why tally is treated as a safety system rather than a convenience. A presenter who believes they are off air behaves like somebody who is off air. If tally is wrong on a show, it gets fixed before the show, not during it.
What a seat actually owes
Be there, early, with the thing your seat needs. Know what is coming next. Acknowledge every call aimed at you. Do what was called rather than what you would have preferred. Say bad news immediately and accurately. Never go quiet.
None of that is skill in the sense of craft. It is reliability, and in a control room reliability is worth more than flair, because flair that arrives late is indistinguishable from a fault.
Learning a seat you have never held
Ask your questions before the show. Nobody minds a question in the pre-show and everybody minds the same question during an item. Find out what your seat is called here, what channel you are on, and what the show expects from you that it might not expect elsewhere.
Then sit and do one job well. The temptation in a first gallery is to watch everything, because everything is interesting. The seats around you are covered. Yours is not.
The sign-off for this book
This book is a map. It cannot make you a director or a technical director, and it does not try. What it can do is let you walk into a control room and be useful in one seat on a small broadcast, which is how everybody who is now good at this started.
The measure is simple and somebody else applies it: you mapped the chain, you identified the seats, you followed a director's ready-then-take calls in a role, you triggered a graphic or a replay on a cue, and you held that seat through a whole live show without being the reason anything went wrong. A mentor signs that off when it is true.
What each seat is signed off on
| You can | Which proves | Evidence |
|---|---|---|
| Draw the chain from source to viewer | You know where you are | From memory, on paper |
| Name every seat and what it owns | You know who to tell | Out loud, in an unfamiliar room |
| Follow ready-then-take in a role | You can be called | A whole show without a repeat |
| Trigger a graphic or replay on a cue | You can execute | On time, on the call given |
| Report a fault correctly | You will not hide one | Observation, action, ten words |
| Hold a seat for a whole show | You are reliable | Somebody signs it off |
How to do it
- Arrive early enough to ask your questions before anybody is busy.
- Confirm your channel, your seat's name here, and who calls you.
- Find the programme monitor, the preview and the off-air monitor.
- Read the rundown, your column, and the item after the one you start on.
- Acknowledge everything aimed at you, briefly, every time.
- Afterwards, write down what surprised you, while you still remember it.
What goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Tally is wrong and a presenter talks over a live shot | Tally treated as a convenience rather than a safety system | Test tally before every show, on every camera |
| A first-timer misses calls while watching the room | Trying to see everything instead of doing one thing | The other seats are covered. Do yours |
| Questions arrive during the show | They were not asked in the pre-show | Ask early. Nobody minds then and everybody minds later |
| Somebody is good and still not trusted | They improvise on calls | Execute the call. Offer the better idea in the break |
Practice it
The real one. Find a small broadcast and ask to sit in a seat.
- I can draw the broadcast chain from memory.
- I can name every seat and what it owns.
- I followed ready-then-take through a whole show.
- I triggered something on a cue, on time.
- I reported a fault as an observation, immediately.
- I did not go quiet once.
- Somebody who was there would put me in that seat again.
What the gear actually looks like
Every device named in this book, in one place. Recognition is the whole point of Chapter 4 — use this page to attach a picture to each name before you meet it on a dock at six in the morning.
Find the destination.
Work along the path between them.