Chapter 1: Sixteen Feeds Arrive at Once

There is a moment when the Festival Mesh stops looking like a collection of venues and starts looking like a television network.

It happens when the OB Truck door closes.

I felt it years ago, before I ever had a spreadsheet or a therapist — back when SDI was still something I thought you could manage without both. I was a student, and the team behind our local Freeview channel, Estuary TV, had invited a group of us to Grimsby to help with local election coverage. The vote count itself was exciting enough — politics, tension, the occasional recount — but the part that stayed with me happened before we even left the studios. They gave us a tour of the broadcast suites.

I remember standing in front of a wall of screens, watching feeds arrive from places I could not hear, rooms I could not walk to, and performances I could only experience through the decisions someone else had already made. The director sat in the middle of the room, surrounded by people who trusted him to know which rectangle mattered at any given moment. He had a headset on, a coffee that had gone cold two hours ago, and a running order that was being rewritten in real time by a production coordinator who was fielding calls from three different events simultaneously. The wall of screens showed feeds from Grimsby, Cleethorpes, and the surrounding villages — each one a different room, a different set of events, a different story. The director chose which one the audience saw. He chose when to cut from a book group in a village hall to a reporter ready to go live from a town centre. He chose when to hold on someone's face and when to pull back to a wide shot. I did not understand the half of what I was seeing. But I understood the feeling: this was what it looked like when multiple feeds became one broadcast.

It is a strange kind of power. And a strange kind of powerlessness.

The power is the ability to decide what thousands of people see. The director in that broadcast suite was not counting votes. He was not a candidate, an agent, or a returning officer. He was a storyteller who had been given multiple cameras and the authority to choose which one mattered. When he cut from a quiet count to a tense declaration, he was making an editorial decision that shaped how the audience understood the election. He was telling them: this is the moment that matters. The audience trusted him because they had no choice — they could not see the other feeds. They could only see the one he chose.

The powerlessness is the flip side of that same coin. The director could not fix a venue's Wi-Fi from the broadcast suite. He could not make a candidate concede gracefully. He could not stop a returning officer from mispronouncing a name. He could only watch the feeds arrive and make the best decisions he could with whatever the universe sent him. When a feed dropped — a camera failed, a cable came loose — the director had to react in real time. He could not pause the election. He could not ask the candidates to wait while engineering fixed the problem. He had to cut to another feed, or to a holding slide, and hope that the audience would not notice the gap.

That is the Command Nexus. That is what it feels like to sit in the middle of a room and hold multiple live feeds in your head at once. The power to choose. The powerlessness when the choice is taken away. The knowledge that every decision you make shapes what thousands of people see, and the awareness that you cannot control everything that happens in sixteen venues simultaneously. The director in the broadcast suite in Grimsby taught me that. And every time I sit in front of a wall of screens, I feel it again.

Outside, Bridlington is still Bridlington. Bands are playing in pubs. The Priory is shaping its own acoustic world. The Spa Gardens is running a full outdoor IP production. The Royal Hall is making its headline programme beneath the restored Art Deco dome. Every venue has its own audience, crew, running order and reason to exist.

Inside the truck, they become sixteen rectangles on a wall. That sounds like a reduction until you sit in front of them. Each rectangle is a live responsibility. One may be carrying the festival's biggest performance. Another may be waiting for a presenter. A third may be showing a changeover. A fourth may have perfect pictures and no audio. A fifth may disappear because somebody in a pub has restarted the wrong router. The truck must know the difference.

This is the Command Nexus: £180,000 of decoding, switching, recording, monitoring, storage and distribution hardware built around one uncomfortable truth. The town-wide festival only becomes a shared broadcast when somebody can see the whole thing at once.

The venues have already done the difficult local work. They have found camera positions, built programme audio, made graphics, protected their recordings and encoded their finished feeds as SRT contributions. The truck does not receive every raw camera and microphone in Bridlington. It receives the decisions each venue has made.

That boundary is essential. The Royal Hall director chooses between four URSA Cine cameras. The central director chooses whether the festival should be at the Royal Hall at all. The difference is editorial scale.

Sixteen Blackmagic Streaming Decoder 4Ks form a flexible contribution pool. Fourteen active SDI channels carry six fixed venues, three independent South Beach camera feeds and five paths for backup, pop-up, fringe-event or roving-reporter sources. Two further SDI channels carry fill and key from the Blackmagic Media Player 10G. Three SDI Expander 8x12G units form the edges between SDI equipment and the native-IP core. Five Ethernet Switch 820s provide the 100G environment. The ATEM 4 M/E Constellation IP Plus, operated from a 2 M/E Advanced Panel 40, makes the central programme. Six HyperDeck ISO Recorder 100Gs preserve the services. Eight Streaming Encoder 4Ks provide one main output, six fixed-venue services and one flexible or spare service. A 48TB Cloud Store Ultra gives the records somewhere central to live. The equipment list is not dominated by a beautiful camera or an absurd lens. The cameras are elsewhere.

The responsibility is here.

Sixteen independent realities

The incoming feeds may all be SRT, but they are not interchangeable. The Royal Hall may send a polished 4K headline programme. The Black Lion may send a much leaner feed from a compact switcher. The Priory may have a full broadcast audio mix. South Beach may provide the best balance it can make from three phones on cellular data. Their delays, bitrates, frame rates and operational confidence may differ.

The truck's first job is not to make them identical. It is to make them understandable. Every service needs a name, a decoder, an expected format, a known audio arrangement and a contact at the venue. "Decoder 7" is not enough when the director needs the Black Lion. "That one in the corner" is not enough when engineering needs to know which contribution has been unstable since soundcheck. Source identity is infrastructure.

The second job is to decide what matters now. Sixteen live feeds cannot all receive equal editorial attention. The central director needs to know which venue is on programme, which is about to become useful, which is in changeover and which is unavailable. Engineering needs to know whether a black picture means an intentional slate, a failed contribution, a decoder problem or a broken route inside the truck. The multi-view therefore cannot be a passive mosaic. It is a live status board for the town.

The decoder wall is the Command Nexus's first impression of the festival — sixteen small screens, each one a different room, each one a different stage. It is the festival's mosaic, and the mosaic shows the variety honestly. The Royal Hall is a concert hall with professional lighting and a full sound system. The Black Lion is a pub with a back room stage and a PA from the nineties. The Priory is a medieval building with stone walls and a single spotlight. The Spa Gardens is an outdoor stage with a tent and a bar. The screen also shows the festival's health: a locked decoder is a healthy decoder, an unlocked one needs attention, a black one has failed. Variety and health on the same wall, because the programme must honour the variety without pretending every room is in the same condition.

The truck makes a promise to every venue: if you send a healthy authorised service, we will receive it, identify it, monitor it and make it available to the central production. If that service is selected, we will carry it into the main programme or the appropriate additional output. If it is worth preserving, the recording system will capture it with enough information to find it later.

The truck also makes a promise to the audience. The central programme will not feel like somebody flicking randomly through security cameras. It will move through the festival with intention. A change of venue will have a reason. Audio will not leap wildly between rooms. A missing satellite will not automatically become a black screen.

Those promises create the truck's real workload. Centralisation does not remove complexity. It gathers complexity into a room where people can coordinate it.

The warning built into the budget

The Command Nexus is also the largest shared point of failure in the mesh. If one venue loses its local switcher, that venue has a serious problem. If the central ATEM, timing environment or critical truck power fails, every centrally produced service can be affected. The truck simplifies coordination by concentrating responsibility, and concentration always creates consequence.

That is why this post is not a victory lap for expensive networking. It is about the discipline required to make central control useful rather than fragile. The truck has to receive sixteen realities, preserve their differences and turn them into one comprehensible service.

The door is closed. The feeds are arriving.

Chapter 2: Venue Portrait — The Truck as a Workplace

A kit list has no chairs. It has no knees, elbows, coffee cups, headsets, fire exits or engineers trying to reach the rear of a rack without interrupting the director. It can make the relationship between a Streaming Decoder and an SDI Expander look clean. It does not show the heat from sixteen decoders or the fan noise from five 100G switches after ten hours on air. The signal layout below is the nervous system of the Command Nexus — but the vehicle around it still needs a body.

Someone's home from home

This truck is not a venue you visit for an hour and leave. For the crew inside, it is the longest commitment of the festival day. Twelve, fourteen, sometimes sixteen hours in a room the size of a small garage, with the same people, the same hum of fans, and the same knowledge that if something goes wrong, the whole town goes dark on your watch. That changes the room.

The director's chair is not a luxury. It is the place where someone will spend the entire festival, making hundreds of cuts, drinking cold coffee, and listening to sixteen venues through a single pair of headphones. The audio engineer's position is not a desk. It is where someone will sit for fourteen hours, riding gain on a Fairlight panel, trying to make the Black Lion sound like the Royal Hall and the Priory sound like a pub without the audience ever noticing the transition. The truck has to be designed around the fact that people live in it. Not visit it. Live in it.

There is a rhythm to a long day in the truck. The morning is quiet — line checks, decoder locks, the calm before the first band starts. By midday, the room has warmed up, the fans have found their voice, and the crew has settled into their positions. By evening, when the Royal Hall headline is running and every venue is live, the truck is at its most intense — and its most cramped. Someone needs to reach the back of a rack. Someone needs to swap a cable. Someone needs to lean over the technical director to check a decoder state, and the technical director is trying to cut the programme, and the audio engineer is trying to balance a transition, and the recording operator is watching six HyperDecks and a storage meter that is slowly climbing. The room has to absorb all of that without becoming hostile.

The working zones

Even a small truck needs several working zones, even if the physical space cannot give each one a separate room. Vision control needs the director and technical director positioned where they can see the central multi-view and communicate without shouting across other roles. Audio needs a position where the engineer can hear the programme properly, reach the Fairlight panel and avoid mixing through the noise of the racks. Engineering needs access to the media fabric, timing, decoders, conversion and encoder states. Recording needs visibility of six HyperDecks and the Cloud Store. Playback and graphics need computer surfaces that do not become a dumping ground for every unrelated task.

The challenge is not fitting the equipment inside — rack units can be counted. The challenge is fitting the work. If the engineer has to squeeze behind the technical director to replace a connection, the floor plan is wrong. If the audio engineer is seated against the loudest rack fan, the monitoring plan is wrong. If the recording operator cannot see the storage state without leaving their position, the interface is wrong. The truck must be designed around moments of pressure, not around a photograph taken while it is empty.

Heat, noise and the long day

Every major system in the truck produces heat. Decoders, encoders, Ethernet switches, recorders, storage, Mac Studios and displays all convert power into work and then into warmth. The Cloud Store Ultra and the Ethernet Switch 820s use front-to-rear airflow because they expect to live in a proper rack environment — and that airflow has to go somewhere. Cooling is therefore part of the production system. It is not a comfort upgrade added after the signal flow works.

The same fans that protect the equipment create noise. That matters because audio decisions are being made a few metres away. It also matters because sustained noise is tiring — a crew can tolerate an unpleasant room for an hour, but a festival day may ask them to remain accurate for twelve or fourteen. Human concentration is a limited technical resource. The truck needs sensible cooling, acoustic management, breaks, lighting and working surfaces because tired people make routing mistakes. A perfectly redundant network does not protect against a technical director taking the wrong source after ten hours without relief.

The racks must be serviceable

The decoder wall and encoder bank are likely to need attention during the event. The same is true of the SDI Expanders, switches and recorders. Their rack positions should reflect that. A front panel that shows service state is useful only if somebody can see it. A cable that can be replaced is useful only if somebody can reach it. A redundant power input is useful only if the two supplies are actually fed from appropriately separated sources.

The vehicle needs cable management that preserves identity. Satellite 1 should not become a mystery bundle disappearing behind Satellite 2. The three SDI Expanders need clear channel maps. The 100G connections need labels that describe both endpoint and path. Management connections need to remain distinguishable from media and timing. Neatness is not cosmetic in a truck. It is recovery speed.

I learned this the hard way. Early in my career, I worked a show where a cable needed replacing during a live broadcast. It was a faulty SDI cable — the picture was breaking up on one source. We identified the problem. When we went to remove the cable, we couldn't find it. The cable was routed through a bundle of other cables, unlabelled, indistinguishable from the dozen others in the same bundle. It took five minutes to identify the faulty cable. Five minutes of a broken picture on the director's multi-view. Five minutes of the director cutting around the broken source. Five minutes that felt like five hours.

We replaced the cable. The picture returned. The broadcast continued. But the lesson was learned. After that show, we labeled every cable at both ends, colour-coded by function — blue for SDI, yellow for Ethernet, red for power, green for management. We added cable management that kept each cable accessible, traceable, replaceable. The next event, when a cable needed replacing, it took thirty seconds. Not five minutes. Thirty seconds. The difference was labels and cable management. The difference was preparation.

The room around the running order

The physical layout should also reflect the rhythm of the day. The director needs immediate access to the running order and venue status. The production coordinator needs a place to receive changes without standing in the vision line. Venue communications need to reach the right operator rather than becoming a general conversation inside the truck. Playback material needs to be prepared and checked away from the live trigger surface.

The truck will never feel spacious. That is not the goal. The goal is that every movement has a reason and every role has enough space to remain accurate. The signal flow tells us how the equipment connects. The workplace tells us whether the people can operate it.

The pre-show checklist

The pre-show checklist is the crew's final verification. It happens before the first feed arrives, before the first encoder runs, before the audience sees the festival. It is the last chance to catch the mistakes that preparation missed — the ones the crew's own familiarity has blinded them to.

The checklist walks the systems in order. Power first: is the mains connected, is the UPS charged, is the generator ready? Then the network: are the switches powered, are the VLANs configured, is PTP running? Then the decoders: are all sixteen online, are the SRT streams configured, are the outputs routed to the right monitoring paths? Then the encoders: are the eight ready, are their outputs routed to the correct destinations, are the settings verified?

It also covers the audio — is the Fairlight panel powered, are the faders assigned, are the monitoring paths correct, are the emergency beds loaded? The graphics: are the lower thirds loaded, are the titles ready, are the holding loops cued? And the comms: is the intercom working, is the party-line clean, is the IFB reliable?

The checklist is not a formality. It is the crew's last line of defence, and it catches the mistakes the audience would otherwise see.

Chapter 3: Sixteen Doors Into One Room

Every venue enters the Command Nexus through a decoder. That decision gives the incoming wall a useful simplicity: one service, one device, one SDI output and one visible place to begin troubleshooting.

Let me walk you through the room. Not the equipment list — the room. Because the Command Nexus is not a spreadsheet. It is a physical space that you enter, and the moment you step inside, you understand what it does.

Start at the door. To your left, the decoder wall — sixteen Streaming Decoder 4Ks, each one a window into a venue. Each decoder has a label: the Royal Hall, the Spa Gardens, the Priory, the Black Lion, the Harbour Tavern, Sewerby Hall, South Beach 1, South Beach 2, South Beach 3, and the rest for the flexible paths. The decoders are rack-mounted, and when they are all locked and receiving, the front panel of each one shows a video feed that means "I have a stream." When a decoder loses its stream, the screen turns black. When the black screen appears, someone in the nexus notices. Someone always notices.

Walk further in. The decoder wall feeds into the SDI Expanders — units that convert the SDI outputs from the decoders and other sources into the native-IP core. The expanders are the bridge between the physical world of BNC cables and the virtual world of 2110 streams. They are not glamorous. They do not have screens or meters. They have LEDs that blink when they are working and stop blinking when they are not. But without them, the decoders would be speaking a language the ATEM cannot understand.

Next we have the encoder bank — eight Streaming Encoder 4Ks, each one a boundary between the truck's internal programme services and the outside world. Each encoder takes a selected programme service, compresses it to H.265, wraps it in SRT, and sends it to a destination. The main programme goes to the primary distribution platform. The six fixed-venue services go to their respective destinations. The flexible eighth encoder sits ready to be reassigned at a moment's notice.

The ATEM sits in the middle of the room like a throne. The 4 M/E Constellation IP Plus is the largest switcher Blackmagic makes, and it dominates the space. The 2 M/E Advanced Panel 40 is the surface from which the technical director operates it — a landscape of buttons, knobs, and touchscreens that looks like the control panel of a small aircraft. The first time I sat in front of one, I felt overwhelmed. There were more buttons than I had fingers. More menus than I had patience. But the technical director's hands moved across the panel with the confidence of a pianist, cutting between sources, adjusting transitions, keying graphics, all without looking at their hands. The muscle memory was extraordinary.

The monitoring wall sits behind the ATEM and is made up of SmartView 4K G3 displays. That is enough glass to create the illusion of awareness. When everything is working, the monitoring wall is a masterpiece of information design. When something goes wrong, it becomes a wall of anxiety — every screen demanding attention, every alarm competing to be the most urgent.

To the right we have the Audio Console. A Blackmagic Fairlight Live Audio Panel 40, paired with a Mac Studio and Studio Display XDR screens. The Fairlight panel is the audio engineer's instrument — forty motorised faders, each one assigned to a source or a group, with touchscreens above showing metering, routing, and processing parameters. The audio engineer sits here for twelve or fourteen hours, riding gain on a mix that changes character every time the director cuts from one venue to another. The Royal Hall's headline act sounds nothing like the Priory's acoustic set, and the audio engineer has to compensate for that difference in the time it takes the director to press the transition button.

The room hums. The fans from the Ethernet switches, the decoders, the encoders, the recorders, the storage — they create a constant background noise that you stop noticing after ten minutes but that would deafen you if you walked in from silence. The air is warm. The equipment generates heat, and the cooling system works hard to keep the temperature stable. The lighting is dim — not dark, but dim enough that the screens are the brightest things in the room. The crew sits in specific positions: the director in the centre, the technical director at the ATEM panel, the audio engineer at the Fairlight panel, the recording operator watching the HyperDecks, the distribution operator watching the encoders, the network engineer watching the switches and the timing environment.

This is the Command Nexus. It is not a truck, necessarily. It could be a room at the college, with its 1Gb line and its lecture-hall quiet. It could be a spare room in a civic building, with a view of the car park and a kettle in the corner. It could be a dedicated facility built for the purpose, with proper power, proper cooling, and proper acoustic treatment. The key requirement is not mobility. The key requirement is bandwidth — enough to receive all sixteen SRT feeds simultaneously and send out the eight encoder feeds. The Command Nexus is wherever the bandwidth is.

The decoder wall at Command Nexus scale

The Blackmagic Streaming Decoder 4K receives H.264 or H.265 streams from compatible Blackmagic encoders, ATEM switchers and cameras, then converts them back into SDI or HDMI video. It supports 12G-SDI output and HDMI 2.0, with format and frame-rate conversion available on those outputs. It can work with Blackmagic Cloud streaming and provides a reference input and output for integration into a controlled production environment.

For a remote studio workflow, it can also support return control, tally and talkback when paired with suitable equipment. In the Festival Mesh, its central purpose is more direct: turn an incoming SRT contribution into a baseband source the truck can identify, monitor and pass into the IP core.

The decoder does not improve a poor contribution. It cannot recreate detail removed by an encoder or repair an audio mix that was wrong at the venue. It gives the truck a stable operational endpoint for whatever arrived. That is exactly what master control needs.

The Streaming Decoder 4K was introduced at venue level at the Harbour Tavern and Sewerby Hall, decoders converted incoming NDI or camera streams into SDI for local switching. Here, the same device appears sixteen times, each one assigned to a specific venue contribution. The difference is scale and identity. At venue level, a decoder is a utility. At Command Nexus level, it is a relationship. Decoder 1 is the Royal Hall. Decoder 2 is the Spa Gardens. Decoder 3 is the Priory. The naming is not optional. It is infrastructure.

Two banks of eight

The central incoming edge is divided across two SDI Expander 8x12G units. Fourteen SDI channels carry decoder-fed contributions: six fixed venues, three independent South Beach cameras and five flexible paths. The remaining two channels are used by the Blackmagic Media Player 10G for fill and key for media on the central multi-venue broadcast.

Each decoder produces its SDI service. The two expanders convert the active contribution inputs into sources on the local SMPTE 2110 fabric. The ATEM, recorders and authorised monitoring destinations can then use those named sources without carrying a separate BNC route to every device.

The division also gives engineering a useful fault boundary. If the Black Lion's contribution is missing, the team can inspect its decoder, the corresponding input on the expander, the IP sender and the destination route. If the first eight decoders disappear together, the shared edge becomes an obvious place to look. The physical design helps the mental model.

Names before pictures

Every incoming contribution needs an agreed identity before the event. The decoder name, expander channel, NMOS sender name, ATEM source label, recorder label and multi-view label should describe the same venue. If Decoder 4 is the Black Lion, every layer should say Black Lion or follow a documented naming convention that makes the relationship obvious.

The expected format and audio arrangement belong beside that identity. Is the service UHD or HD? What frame rate is expected? Is the programme audio embedded? Is there a clean version? Who at the venue can confirm the encoder state? A decoder wall without this information is sixteen opportunities to guess.

This matters more than it sounds. In the middle of a live show, when the director says "take the Black Lion," the technical director needs to know instantly which source that is on the ATEM. The audio engineer needs to know which fader group carries the Black Lion's programme audio. The recording operator needs to know which recorder channel is capturing it. If the naming convention breaks down — if "Decoder 4" means nothing to the director, if "Source B" means nothing to the audio engineer — the crew starts guessing. And guessing in a live broadcast is how you cut to the wrong venue, or lose the audio, or discover that the source you thought was the Priory is actually a holding slate.

The convention should be documented before the festival. Every operator should have a copy. The multi-view labels should match. The ATEM source labels should match. The recorder labels should match. The encoder labels should match. The convention is not decorative. It is the shared language of the Command Nexus.

Latency belongs to the service

SRT is designed to deliver reliable streams across imperfect networks by buffering against loss and variation. That reliability introduces latency, and different network paths may require different buffers. The Royal Hall, the Black Lion and the Harbour Tavern may therefore arrive at slightly different moments even if events on their stages happen simultaneously. The truck can monitor and manage its central presentation, but it should not pretend that every public-internet contribution shares the same production clock.

This matters most when services interact. A presenter in the truck cannot conduct a natural two-way conversation with a venue unless the delay has been rehearsed. Cutting rapidly between two performances does not require frame synchrony, but a split-screen exchange or shared countdown may expose the difference immediately. Latency is not a defect to be hidden. It is a property to be understood.

I have seen latency cause a visible problem on a live show. A director decided to do a split-screen interview between a studio presenter and a reporter in the field. The presenter asked a question. The reporter heard the question, paused, and answered. The pause was about two seconds. The audience saw the presenter ask a question, then a two-second silence, then the guest answer. It looked like the guest had not heard the question. It looked like the technology had failed.

The reporter's SRT stream had a latency of about 1500 milliseconds. The return feed from the studio to the reporter had another 500 milliseconds. Total round-trip: two seconds. That two seconds was the pause the audience saw. The guest had heard the question perfectly. The technology had worked perfectly. But the latency had made it look like nothing was working.

The solution was to rehearse. Before the next split-screen interview, we measured the latency. We told the presenter: "There will be a two-second delay. Ask the question, wait one second, then the guest will answer." The presenter followed the script. The interview looked natural. The latency did not change. The understanding of the latency changed. That is the difference between a problem and a property.

The missing venue

When a contribution disappears, the decoder wall should make the failure easy to locate and the programme easy to protect. The director takes a safe source. The affected venue is marked unavailable. Engineering checks whether the stream is reaching the decoder, whether the decoder has a usable output and whether the source exists beyond the SDI Expander. The venue contact checks the local encoder and internet service. The central programme does not wait on black.

The truck may use a festival slate, holding loop or another healthy venue while recovery continues. If the lost service is one of the additional stage outputs, that channel can fall back to an identified holding source or the main festival programme rather than presenting a silent failure. One missing door should not darken the whole room.

The recovery process should be documented. The crew should know which steps to take when a venue drops. The crew should know which comms channel to use to contact the venue. The crew should know which source to cut to while the venue recovers. The crew should know which source to cut back to when the venue returns. The recovery process should be rehearsed. The recovery process should be tested. The recovery process should be verified.

The recovery process also requires patience. The venue may take five minutes to restart its encoder. The venue may take ten minutes to restore its internet connection. The venue may take fifteen minutes to diagnose the problem. The crew needs patience. The crew needs to wait. The crew needs to keep the programme alive while the venue recovers. The crew needs to protect the audience's experience while the venue fixes its problem.

The recovery process also requires communication. The crew communicates with the venue. The crew communicates with the production team. The crew communicates with the audience. The communication prevents panic. The communication coordinates the response. The communication keeps the festival alive.

The roving contribution

There are going to be moments throughout the festival that you can't catch in a venue. A piece to camera from a presenter outside the Priory or overlooking the harbour. A popup event that isn't part of the festival but is too good not to include in the broadcast. A speech by the organisers outside one of the venues. It is not realistic to get one of the teams to run a bunch of cable from the nearest participating venue to wherever it's needed. You need a roving camera.

The URSA Broadcast G2 is the festival's roving camera. It is the camera that can go anywhere. It is the camera that can capture the unexpected. It is the camera that can bring the audience into the festival's most intimate moments.

The URSA Broadcast G2 is not a studio camera. It is a field camera. It is designed to be carried, to be moved, to be pointed at whatever the moment demands. It has a lightweight body, a sensitive sensor, and a lens mount that accepts broadcast lenses. It is the camera that the crew grabs when something unexpected happens. It is the camera that the crew carries when the festival demands mobility.

The URSA Broadcast G2 connects to the mesh via SRT. It sends its feed to the Command Nexus like any other venue. The decoder receives it. The SDI Expander introduces it to the fabric. The ATEM can cut to it. The audience sees it. The URSA Broadcast G2 is a venue. It is the festival's mobile venue. It is the camera that goes where the other cameras cannot.

The URSA Broadcast G2 is also a reminder that the festival is not just the venues. The festival is the spaces between the venues. The festival is the street, the market, the crowd, the faces. The URSA Broadcast G2 captures those moments. The URSA Broadcast G2 brings those moments to the audience. The URSA Broadcast G2 is the festival's eyes on the street.

South Beach stays unmixed

South Beach is the festival's most challenging venue. It has no professional audio. It has no professional lighting. It has three phones on cellular data. It has a signal that is as unreliable as the weather. South Beach is the festival's most honest venue.

The Command Nexus receives South Beach's three camera feeds. The three feeds are independent. Each feed carries its own video and audio. The three feeds are not mixed. They are not combined. They are not processed. They arrive at the Command Nexus as three separate sources. The director can cut between them. The audio engineer can manage them independently. But the three feeds are not a programme. They are three cameras pointing at the beach.

The decision to keep South Beach unmixed is deliberate. The three phones capture different angles. The three phones capture different moments. The three phones capture different perspectives. Mixing them would flatten the variety. Mixing them would destroy the authenticity. Mixing them would make South Beach something it is not. South Beach is three phones on cellular data. South Beach is honest. South Beach stays unmixed.

This doesn't mean any less care is given to South Beach than to any of the fixed venues — it just means it's handled differently. The technical director will have these three mobile feeds on a separate M/E, where they can switch between the camera angles available. As the audio is coming from the phones and into the ATEM, the sound engineer can mix the audio between the three phones — keeping the one with the clearest audio on permanently, or switching between them when one phone moves closer to the act.

Chapter 4: The 100G Spine of the Command Nexus

Once the satellite feeds cross the SDI Expanders, they enter the truck's local media environment. This is where 100G stops being a spectacular number and becomes plumbing.

The Festival Mesh has already introduced SMPTE 2110, PTP, NMOS and protected network paths, so if you need a refresh, pop back to the previous posts. The Command Nexus does not need another glossary. It does though, need those ideas to operate at a scale where sixteen incoming programmes, multiple outgoing services, six recorders, format converters, storage and monitoring all need access to the right media.

Five switches, one responsibility

The OB Truck budget includes five Ethernet Switch 820 units. Each provides eight 100G QSFP28 ports, two 10G RJ45 connections and dedicated facilities for PTP reference, NMOS control and management.

The number five is not impressive by itself. It tells us that one small switch cannot sensibly carry every relationship in the truck. In a conventional single-venue production, one or two switches might carry everything. The Command Nexus is different because it has more relationships. Sixteen decoders feed the incoming edge. The ATEM needs sources from those decoders plus playback, graphics and holding material. Six HyperDecks need to subscribe to the right sources. Four UpDownCross converters need to sit between formats. The Cloud Store needs to be reachable by multiple recorders and workstations. Eight encoders need to receive their programme feeds from the outbound edge. Each of those relationships is a connection, and each connection needs a port. The question is not "why five switches?" It is "what does each switch do?"

The answer is that they form a star. Four switches connect to the fifth, and that fifth one is doing real work — it is carrying the traffic between all the devices attached to the other four. The servers on switch two talk to the storage on switch four, and the conversation travels through switch five to get there. That is not an aesthetic choice. Blackmagic does not currently manufacture a 100G switch with enough ports to carry every relationship in the truck on a single device. The technology is not there yet. The five-switch star topology is what the available hardware requires.

The arrangement works because the bandwidth demand on each device is well within what a single 100G link can carry. The calculations are straightforward: add up the sources each switch needs to deliver, account for the overhead, and confirm that no single link is asked to carry more than its capacity. The numbers check out. Every source can reach every destination. The topology is not elegant, but it is honest — and it delivers what the programme needs.

None of which happens by accident. The exact topology should be drawn before the rack is built, not discovered during the first line check. The completed port schedule should show which switches form the media planes, which devices attach to each layer and where A/B protection actually exists. Two drawn routes are not proof of physical redundancy. Every 100G link should have a label at both ends. Every port should be documented. Every protected path should be tested. The switches are not decorations. They are the infrastructure that makes the ATEM, the recorders and the encoders behave like one system instead of a collection of isolated boxes.

The fabric is local

The 100G network begins and ends inside the truck. The venues do not send uncompressed 2110 streams across Bridlington — they send compressed SRT contributions over available internet connections. The decoder wall turns those contributions back into SDI. The expanders introduce them to the internal IP environment.

At the outbound edge, the process reverses. Selected IP programme services leave through the third SDI Expander and enter the eight-channel Streaming Encoder bank. The encoders compress them for external delivery. This boundary keeps the architecture honest: the truck uses 100G where it has control of the network and SRT where it does not.

The temptation is to ask: why not run 100G across Bridlington? Why not run fibre between the venues and the truck? Why not send uncompressed 2110 streams directly from the Royal Hall to the Command Nexus? Why not eliminate the decoders, the encoders, the SRT compression, and the latency that comes with it?

The answer is cost. Running fibre across a town is not cheap. It requires planning permission, trenching, ducting, splicing, and testing. It requires agreements with property owners, the local council, and anyone else who has a say in what happens under the streets. It requires a capital investment that would dwarf the entire budget of the Festival Mesh. And it requires a level of permanence that a temporary festival does not justify.

A fibre run from the Royal Hall to the Command Nexus — assuming the Command Nexus is at East Riding College, which is about a mile away — would cost somewhere in the range of £50,000 to £100,000, depending on the route, the obstacles, and the negotiation required. That is more than half the budget of the entire Command Nexus. For one venue. For one direction. For one festival weekend.

So for one festival weekend, the honest answer is no — unless Openreach or KCom hand us the keys to the kingdom and let us take over some of the dark fibre under the streets. Which is very not likely to happen. The day we actually get that phone call is the day the town council fills in all of the potholes when we are not in the middle of tourist season.

The alternative — SRT over the public internet — costs nothing beyond what the venues already have. The venues already have internet connections. The truck already has an internet connection. The SRT protocol is designed to work over imperfect networks, with buffering, retransmission, and error correction that make it resilient to the kind of packet loss and jitter that the public internet throws at it. The latency is higher — a second or two, compared to the sub-millisecond latency of a fibre run — but for a festival broadcast, a second or two is acceptable. The audience does not notice. The director works around it. The broadcast continues.

That is why the 100G spine stays inside the truck. The public internet carries the contributions. The 100G fabric carries the production. The boundary between them is the decoder wall.

The ATEM at the centre

The ATEM 4 M/E Constellation IP Plus has already appeared at the Royal Hall. In the truck, its role changes. It is no longer cutting four cameras from one stage — it is switching complete venue programmes and building central services. Its capacity gives the Command Nexus room for sixteen satellites, playback, graphics, holding sources, clean outputs, previews and distribution routes.

The central team does not need to use every M/E simply because it exists. The M/Es need assignments that reflect the service plan. One may build the main festival programme. Others may prepare clean or auxiliary services, protect outgoing channels or support preview and transition workflows. Headroom is valuable only when it is labelled.

The first time you sit in front of an ATEM 4 M/E Constellation IP Plus, the scale is disorienting. Four M/E rows, each one a complete mixer with its own keyers, its own transitions, its own outputs. The main programme on M/E 1. A clean feed on M/E 2. A preview of the next venue on M/E 3. A monitoring composite on M/E 4. Each M/E independent, each M/E capable of building a complete programme, each M/E available to the director at the touch of a button.

The ATEM 1 M/E at the Black Lion is a capable switcher. But it has one M/E. The ATEM 4 M/E IP Plus has four. That is not an incremental improvement. That is a qualitative difference. It means the truck can run the main programme, prepare an auxiliary service, protect an outgoing channel, and maintain a preview — all at the same time, all on the same panel, all without the technical director having to reconfigure anything mid-show.

This is where a powerful switcher can become dangerous. If an output depends on an M/E assignment that only one person understands, the truck has created an invisible trap. Every service should have a documented source path and a clear operator responsibility. The panel is not the programme design. It is the surface from which the design is operated.

Media, timing, control and storage

The truck contains several forms of network traffic that should not be described as one giant pipe. The media fabric carries the 2110 streams. PTP gives compatible devices a shared local timing reference. NMOS and control services describe sources and manage connections. Management traffic keeps equipment reachable. Storage traffic allows HyperDeck recorders and workstations to access the Cloud Store. The UniFi Pro XG 48 switches support ordinary high-speed data and operational systems alongside the dedicated broadcast fabric.

These functions can be designed to cooperate without being allowed to interfere casually with one another. A file transfer should not destabilise programme media. A management fault should not be mistaken for a lost source. A healthy network link should not be treated as proof that PTP is healthy. The engineer needs boundaries because boundaries make faults understandable.

The distinction matters because different traffic types have different requirements. Programme media needs guaranteed bandwidth and minimal latency — a dropped multicast packet is a visible glitch on the programme output. PTP needs priority and stability — if the timing reference drifts, every device on the fabric may lose synchronisation. NMOS needs reliability — if the controller cannot register a source, the ATEM cannot see it. Management needs reachability — if the engineer cannot access a switch, they cannot diagnose a problem. Storage needs throughput — six HyperDecks writing simultaneously to the Cloud Store generate a sustained load that must not compete with programme media for bandwidth.

The Ethernet Switch 820s support quality of service, VLAN isolation and multicast filtering. Those features are not theoretical. They are the tools that keep a file transfer from corrupting a programme feed, that keep a management broadcast from flooding a media port, that keep PTP traffic from competing with video for switch bandwidth. The network engineer's job is to configure those tools before the first feed arrives, not to discover their absence when the programme glitches.

Network monitoring

Configuring the switches is not the end of the network engineer's job. It is the start. The network is a living system. It changes, it degrades, it recovers — and the engineer needs to see those changes in real time, because by the time the audience notices, it is too late.

The Ethernet Switch 820s provide detailed monitoring. They show bandwidth utilisation, error rates, multicast group membership, PTP synchronisation status and VLAN health. The network engineer watches these metrics throughout the show. They see the bandwidth climbing as more venues go live. They see the error rates rising as the internet connection degrades. They see the PTP status changing as devices join and leave the fabric.

This is not passive watching. It is interpretation. A rising error rate is not just a number. It is a symptom — the internet connection is under load, the SRT streams may be at risk, and the crew needs to be warned before the director finds out the hard way. The monitoring is the network's early warning system. The engineer is the person who reads it.

The monitoring also includes the UniFi Pro XG 48 switches. These carry management traffic, storage traffic and operational systems. They are not part of the broadcast fabric, and a failure on them does not affect the programme output. But they are the festival's operational backbone — the crew's ability to communicate, to manage equipment, to access storage. If the UniFi switches die, the truck does not stop broadcasting, but it stops functioning. The network engineer keeps them healthy too.

Format conversion with a reason

The four UpDownCross 100G units provide multi-channel standards conversion inside the IP environment. They are not SDI-to-IP bridges — the SDI Expanders perform that edge conversion.

Their value appears when the sixteen contributions do not all arrive in the central programme standard. A venue may be HD while the main service is UHD. A frame rate may need normalising. A monitoring or outbound route may require a different format. Conversion belongs in the system design because every conversion has consequences — it may affect timing, latency, scaling and monitoring. A named conversion path can be tested. An emergency converter inserted during the show becomes another unknown.

The UpDownCross 100G is a 1RU device that provides multi-channel standards conversion in the IP environment. It can take a 2110 stream at one resolution and frame rate and output a 2110 stream at another. It can convert HD to UHD, UHD to HD, 50fps to 60fps, 60fps to 50fps. It can apply scaling, aspect ratio conversion, and colour space conversion. It can do all of this simultaneously on multiple channels, with sub-frame latency, without breaking the PTP timing.

The Command Nexus has four of them. Their job is to make every incoming contribution predictable before the director takes it. The Royal Hall may be sending UHD. The Black Lion may be sending HD. South Beach may be sending 1080p from a phone. The director does not care about the technical provenance. The director cares about the editorial moment. The UpDownCross units ensure that when the director cuts from the Royal Hall to the Black Lion, the audience does not see a jarring resolution change.

That conversion has consequences. Upconverting HD to UHD does not add detail that was not captured. It interpolates — it guesses what the missing pixels might look like based on what it has. The result is a clean image that is slightly softer than native UHD. Some viewers will notice. Most will not. The alternative — leaving the HD feed as-is in a UHD programme — creates a visible quality jump that every viewer will notice. The conversion is the lesser compromise.

The Command Nexus does not need every source to begin identical. It needs every source to become predictable before the director takes it. The UpDownCross units make that possible. They are not glamour devices. They do not have screens or meters. They sit in the rack and do their job. And when the director cuts from the Royal Hall to the Black Lion and the audience sees a seamless transition, the UpDownCross units are part of why.

Compare that to the UpDownCross units at the Royal Hall. The Royal Hall has two UpDownCross units, used to convert between the 12K URSA Cine cameras and the 2110 fabric. The Command Nexus has four UpDownCross units, used to convert between the sixteen incoming venues and the central programme standard. The Royal Hall's converters handle two or three sources. The Command Nexus's converters handle sixteen. The scale is different. The principle is the same.

Chapter 5: Master Control — Making One Festival Programme

The central director is not directing sixteen performances. They are directing the audience's journey between them.

Every venue has already made its local programme. The Royal Hall sends the cut chosen by its director. The Spa Gardens sends its outdoor stage mix. The Priory sends the version of its room that its own team has built. The Command Nexus receives those finished perspectives and decides when each one belongs in the festival-wide service.

The main programme has an argument

A central programme needs more than a running order. It needs an editorial reason to move. The Royal Hall may hold the headline, but the Black Lion may contain the most surprising moment. The Spa Gardens may be in changeover while the Priory is reaching the end of a set. A presenter may need to connect two locations while the next stage becomes ready.

The director needs information from every venue without allowing every venue to shout at once. A status system can show which services are live, preparing, in changeover, delayed or unavailable. The production coordinator can translate running-order changes into choices the director can use. Venue contacts can warn the truck about an approaching finale rather than expecting somebody to notice it in a small multi-view box. Central switching is editorial listening.

That is the argument. Not "what is the running order?" but "what does the audience need to see right now?" Sometimes the answer is the Royal Hall headline. Sometimes the answer is a Priory interview. Sometimes the answer is a folk duo in the Black Lion that the director did not expect to use. The running order is a plan. The argument is the reality. And the director's job is to reconcile the two.

Taking the Royal Hall

When the truck takes the Royal Hall, it takes the finished Royal Hall programme.

This boundary allows both teams to concentrate. Local production makes the performance. Master control makes the festival.

The hand-off still needs rehearsal. The Royal Hall should tell the truck when its programme is clean, when titles are present, when the headline is about to start and when the local director expects to end. The truck should know whether it is taking the venue's complete programme audio or adding a central presenter over it. Two directors can cooperate without competing for the same cut.

That cooperation is more delicate than it sounds. The Royal Hall director is inside the performance, feeling it, responding to it. They can see the guitarist's fingers, the drummer's expression, the way the light catches the vocalist's face. They make choices that are intimate and immediate. They cut to the close-up because the vocalist is about to hit the high note. They cut to the wide because the drummer is about to do the fill that builds into the chorus. They are inside the performance.

The central director is in the truck, watching sixteen feeds on a wall. They cannot see the guitarist's fingers. They can see the Royal Hall's programme feed — the finished product of the local director's choices. They do not have access to the four individual URSA Cine cameras. They cannot ask camera two to find the drummer. That is not their job. Their job is to decide whether the festival audience should be at the Royal Hall at all, or whether the Black Lion's surprise acoustic set is more interesting, or whether the Priory's interview with the festival organiser is the right moment to cut away from the music.

The communication between the two directors is polite but firm. There can be a moment — a real moment, at a real festival — when the Royal Hall headline is running long. The running order said they should finish at ten fifteen. At ten twenty, they are still going. The central director needs to cut to the Spa Gardens for a scheduled interview. The Royal Hall director is not ready to let go.

"Royal Hall, we need to move to the Spa Gardens in two minutes."

"We're in the finale. Give us three."

"Royal Hall, the Spa Gardens is ready now. Two minutes."

The Royal Hall director uses those two minutes. The band hits their final chord at ten twenty-two. The central director cuts to the Priory at ten twenty-three. The audience at home sees a seamless transition. The audience in the Royal Hall sees the band take their bow. Both directors made the right choice. The boundary held.

M/Es as service structure

The ATEM's four M/Es give the truck room to separate tasks. One can build the main festival programme. Another can prepare an auxiliary or clean path. Others can support outgoing services, previews, transitions or protected programme structures. The exact assignment should follow the seven-service distribution plan rather than being copied from a conventional single-channel gallery.

The central programme may live on M/E 1 — the main festival service that cuts between venues, carries the central presenter and carries the festival's visual identity. M/E 2 could be the South Beach mobiles or the Roving Camera ready for a presenter to segue between venues. M/E 3 may be the preview of the next venue — the director can see what is coming next, can decide whether to cut now or hold for a few more seconds. M/E 4 may be a monitoring composite — all sixteen venues on a single screen, with programme and preview overlaid.

The assignment should be documented. Every operator should know which M/E does what. Every output should have a label. Every source should have a path. The assignment should not be a secret known only to the technical director. It should be a design known to the entire crew.

The M/E assignments should also be tested before the show. The technical director should verify that each M/E produces the expected output. The audio engineer should verify that each M/E's audio is correct. The graphics operator should verify that each M/E's graphics are present. The test should be documented. The test should be repeated if the assignments change. The test is the programme design's validation.

The ATEM's four M/Es also give the truck the ability to prepare the next venue without the audience seeing it. The director can cue the next venue on M/E 3 — the preview M/E — while the current venue is live on M/E 1 — the programme M/E. The director can see the next venue's feed, check its quality, check its audio, check its graphics, before cutting to it. The audience sees a seamless transition. The director sees a prepared transition. The M/E structure makes that preparation possible.

Graphics, playback and continuity

The Media Player 10G and one of the Mac Studios provide the central production with material that does not belong to any single venue. Festival titles, schedule updates, sponsor material, holding loops, presenter graphics and emergency slates can all be prepared centrally. That gives the main service a visual identity even as it moves between productions of very different scale.

Continuity material is especially valuable when a venue is not ready. The director should never be forced to choose between an unstable contribution and black. A known holding source, festival ident or presenter position creates time for engineering and the venue to recover. Preparation turns waiting into broadcasting.

The holding loop is the most important piece of continuity material. It should be prepared before the festival. The graphics team designs it. The audio team composes the music. The production team approves it. It is loaded into the Media Player 10G, tested, and verified. When a venue's feed drops, the director presses a button and the holding loop appears. No panic. No scrambling. No improvisation. Just preparation.

The holding loop has limits. It is usually thirty seconds long. If the venue takes longer than thirty seconds to restore, the loop plays on repeat. The audience sees the same animation twice, then three times. The comments section notices. "Is the holding loop stuck?" "Why is the logo spinning?" At that point, the director should cut to a presenter who can explain the situation, to a healthy venue, or to a replay from the truck's own recordings — an earlier performance or interview, shown behind a festival replay ident so nobody mistakes a recording for a live moment. The holding loop buys time. It does not replace the programme.

The small stage can win

The central programme should not become a ranking of equipment budgets. The Royal Hall is visually magnificent because its job justifies it. That does not mean it owns every minute of the festival. A singer in the Black Lion may create the moment people remember. An interview at the Priory may matter more than a technically perfect wide from the Royal Hall. A spontaneous audience response may be more alive than the planned transition.

The Command Nexus exists so the festival can recognise those moments across the town. Sixteen feeds are not sixteen obligations to cut randomly. They are sixteen opportunities to choose well.

There could be a moment — a real moment, at a real festival — when the central director was cutting between venues, following the running order, when a small venue sent a feed that was unexpectedly extraordinary. A folk duo, just a singer and a guitarist, performing in the Black Lion's back room. The room that smelled of ale and wood polish, with church pews facing the stage and corrugated iron on the back wall. The director held on the feed. The running order said to cut away after two minutes. The director held for four. Then six. Then the production coordinator leaned over and said, "We're supposed to be at..." The director said, "I know. Look at this."

The Royal Hall was running a headline act with a full lighting rig and a sound system that cost more than a house. The Black Lion had two parcans and a PA from the nineties. The director stayed on the Black Lion. The audience at home saw a folk duo in a room that smelled of ale and wood polish, and the comments section lit up with "this is the best thing I've seen all night." The director had the power to make that choice. And he made it.

That is what the small stage can win. Not because the small stage is better than the big stage. But because the small stage can contain moments that the big stage cannot. Intimacy. Spontaneity. Authenticity. The kind of moments that make people remember a festival. The kind of moments that the Command Nexus exists to recognise and share.

Chapter 6: Audio at Town Scale

Changing venues is also changing rooms. The picture makes that obvious — the Royal Hall looks nothing like the Black Lion. The sound can be more disorienting because the listener cannot see the acoustic shift coming.

One venue may arrive loud, wide and full of audience. Another may be quiet and intimate. A third may have a presenter close to the microphone. If the central programme cuts between them without audio control, the festival feels less like a shared service and more like somebody changing channels with the volume control broken.

The mix arrives finished

The truck normally receives each venue's finished programme audio embedded with its SRT contribution. It does not receive every microphone from every stage. This is worth stating plainly, because it is the boundary that separates a realistic system from a fantasy: the Fairlight panel cannot rebuild a poor drum balance at the Black Lion if the venue has sent only a stereo mix. It cannot remove room echo from a source that was captured badly. Local responsibility remains local.

The practical consequence is that audio quality at the Command Nexus is bounded by the quality of the venue contribution. If the Royal Hall sends a polished broadcast mix, the central engineer can make it sit well alongside the Priory's acoustic set and the Spa Gardens' outdoor programme. If the Black Lion sends a distorted stereo from the back of the room, the central engineer can limit the damage but cannot create a clean mix from a dirty source.

The central audio engineer can manage the service that arrives. They can match loudness, protect transitions, apply sensible processing, manage presenter and playback sources and prevent a venue change from becoming an attack on the listener. That is a substantial job without pretending it is remote multitrack mixing.

Audio monitoring

The audio engineer needs to hear what the audience hears. Not what the venue sends. Not what the Fairlight panel produces. What the audience hears. That distinction drives the entire monitoring chain.

The main bus feeds the programme output, the programme output feeds the encoder, and the encoder feeds the audience. The monitoring chain taps the programme output and feeds it back to the engineer's headphones, so the engineer hears the programme as it leaves. It also taps each venue's contribution, so the engineer can hear the Royal Hall's feed before it enters the programme — and preset the faders, the EQ and the compression for the cut before the director makes it. When the cut happens, the transition is seamless.

The chain also includes a confidence feed: the encoded output after compression. Programme audio leaves the Fairlight panel, enters the encoder, gets compressed and leaves as a transport stream. The confidence feed taps that encoded output and feeds it back to the engineer's headphones. If the encoder's compression has damaged the audio, the engineer hears it before the audience does, and can compensate on the Fairlight panel. It is the audio engineer's final check — and the one that catches the failures you cannot predict.

This also matters because the audio engineer is not mixing a studio programme. The programme changes every time the director cuts, and the sound changes with it. The monitoring chain is the tool that makes that change manageable.

Fairlight in master control

The Fairlight Live Audio Panel 40 has already been introduced at venue scale. In the truck, it becomes the central surface for the main programme and related services. The engineer can organise the incoming venues as sources or groups, keep presenter and continuity channels available, manage playback and build a programme bus with enough protection for unpredictable transitions. The motorised faders and touchscreens allow the surface to change context without forcing the operator to live inside a mouse-driven interface.

The transition between venues is the central audio engineer's finest moment and greatest challenge. A good transition is invisible — the audience moves from a pub to a concert hall without noticing the acoustic shift. A bad transition is jarring — the audience reaches for the volume control and is pulled out of the experience.

The preparation is everything. The audio engineer knows which venue is coming next, presets the faders, the EQ and the compression, and when the director makes the cut the transition is seamless. But the transition is as much an editorial decision as a technical one. Loudness consistency does not require emotional sameness: the audio engineer preserves character rather than flattening every room into the same sound. The Royal Hall's headline act has a powerful, full-range sound. The Black Lion's indie band has a raw, immediate sound. The Priory's acoustic set has a spacious, reverberant sound. The engineer honours that variety.

And the transition is a timing decision. The director cuts at the right moment; the audio engineer fades at the right moment; the two decisions are synchronised. The audience sees the new venue and hears the new venue at the same instant, and neither the picture nor the sound tells them the system is doing anything at all. That is the trick: when the audio engineer is at their best, nobody watching would ever know the job existed.

What the Rio is doing in the truck

The Yamaha Rio3224-D3 is not receiving the original stage microphones from sixteen venues. Its role is local to the Command Nexus. It can provide analogue and AES I/O for presenters, commentary, communications integration, local playback, guest positions or external feeds connected at the truck. Its Dante connectivity allows those local sources to reach the Fairlight environment and other authorised destinations without building another large analogue patch around the vehicle.

The exact input list should justify the stagebox. A central presenter microphone is clear. A commentary position is clear. Spare inputs for unexpected interviews or an emergency local programme are clear. "Because a large stagebox belongs in an OB truck" is not a signal-flow reason. Every connector should have a possible job before it is treated as essential.

The Rio's presence in the truck is a reminder that not everything arrives over SRT. The truck itself needs local audio sources — a presenter who can explain a technical difficulty, a commentary position for a special event, a playback system for festival idents and holding music. The Rio gives those sources a clean path into the Fairlight environment without requiring a tangle of analogue cables around the mixing position.

Silence, holding and failure

Silence can be correct in a performance. It is rarely correct when the venue contribution has failed. The audio operator needs known holding material, an emergency bed and a way to follow the director's safe-source decision. If a venue disappears during a transition, the programme should not retain a frozen fragment of its audio or jump unexpectedly to full-scale music from another stage.

Comms discipline matters here. Engineering may be discussing the failed decoder. The venue may be calling with an update. The director may be moving to a presenter. The audio engineer needs the information required to protect the programme, not every detail of the fault. Good communication reduces sonic panic.

I have seen a silence incident save a show. A venue's audio dropped during a transition. The director cut from the main stage to a Popup event. The main stage's audio faded out. The pop up's audio should have faded in. But the pop up's audio was silent. The SRT stream was arriving, the decoder was locked, the video was perfect, but there was no audio.

The audio engineer had three seconds to decide. Cut the programme audio entirely? Hold the main stage's audio? Fade to the emergency bed? The engineer chose to fade to the emergency bed — a low-level music track that was always ready on the Fairlight panel. The fade took two seconds. The audience heard the Royal Hall's music fade out, a brief moment of emergency bed, then the pop up's audio returned. The pop up's audio had been silent for five seconds. The emergency bed had covered the gap. The audience noticed a brief change in the music. They did not notice a silence.

Engineering diagnosed the problem. The pop up's encoder had dropped the audio stream but kept the video stream. The SRT stream was carrying video but not audio. The decoder was locked to the video. The audio was gone. The pop up restarted their encoder. The audio returned. The broadcast continued.

Multiple services, different responsibilities

The main programme needs central mixing because it moves between venues. A venue-specific additional service may normally retain that venue's own programme audio. Those are different operational models. The truck must not accidentally apply a main-programme transition to a stage channel that is expected to remain continuous. Nor should a central presenter appear on every output unless the service design intends it.

The next post in the series will follow these outputs into the viewer experience. Inside the truck, the rule is simpler: every service needs a defined audio source, a defined fallback and somebody responsible for hearing it.

The main programme has the central presenter's microphone. The Royal Hall's additional service has the Royal Hall's programme audio. The Black Lion's additional service has the Black Lion's programme audio. Every service is a different mix with a different source, a different fallback and somebody responsible for hearing it.

The danger is in the routing. If the central presenter's microphone is accidentally routed to the Royal Hall's additional service, the audience watching that service hears the presenter over the Royal Hall's music — and the audience, the Royal Hall and the truck are all confused at the same time. The fix is a routing verification before the show: check every output bus, confirm which sources are present on each, and verify the routing matches the service design. One pass, before the festival, and the mistake is never repeated.

Those services leave the truck through the encoder bank — eight Streaming Encoder 4Ks on the outbound edge. Seven carry the live services: the main programme and the six venue channels. The eighth is the flexible one, held back as a backup or pressed into use when an additional event or venue needs coverage. How a viewer finds those services, chooses between them and catches up afterwards is the next post's story — the Red Button experience this whole series has been building towards. The truck's job is to hand over healthy, clearly identified services. The viewer-facing side is a different job, and it deserves a post of its own.

Chapter 7: The Wall of Anxiety — A Jim Rant

There is a point in every festival build where you stand in front of the multi-view wall and feel the full weight of the thing pressing down on you. Not because anything is wrong. Because everything is right, and it is still bloody terrifying.

The anxiety is the point

If you are not anxious standing in front of sixteen live feeds, seven outputs and a rack of equipment that costs more than your house, you are not paying attention. The anxiety is not a weakness. It is a discipline. Panic is the absence of control. Anxiety is the presence of responsibility. The technical director should be anxious. Not panicked — anxious. There is a difference, and it is the difference between a crew that fixes problems and a crew that creates them.

I'll tell you now that every event that i have worked on I have spent the whole time being anxious. Especially when everything was working perfectly. Audio levels correct. Timecodes matched. Every green light on every device. And I was anxious because I knew that the moment I relaxed was the moment something would go wrong. That is not paranoia. That is experience. The wall teaches you that perfection is temporary. The wall teaches you that the job is to hold the perfection for as long as you can, and then respond when it breaks.

The wall shows every feed, every output, every decoder status, every encoder status. It shows the programme feed, the preview feed, the clean feed. It shows the audio meters bouncing, the timecodes running, the SRT streams connected. It shows everything that could go right and everything that could go wrong, all at once, on a single wall of screens. And it does not care which one you are looking at. It shows everything simultaneously. The wall is indifferent to your attention span.

What the wall teaches you

The wall teaches you about the audience because it shows you the distance between what you control and what they experience. You control the encoder, the decoder, the switcher, the audio mixer, the media player. They experience the festival. The wall is the gap between those two realities. You are standing on one side, surrounded by rack gear and faders and timecodes. The audience is on the other side, watching a festival. The wall is the place where those two worlds meet, and it is thinner than you think.

The wall also teaches you about failure, because it shows you the failure before the audience experiences it. A decoder drops. An encoder fails. An SRT stream disconnects. You see it on the wall. The audience does not. That is the wall's gift. It gives you time. Time to cut to a healthy venue. Time to switch the service to the flexible encoder. Time to contact the venue. Time to fix the problem before the audience knows it exists. The wall is your early warning system. It is the reason the audience never sees the cracks.

I started out in events as a lighting tech, and I will never forget the day somebody told me the unvarnished truth. Years later, during my Media and Live Production degree, the head of curriculum turned to me and said: "No one cares about the lights, Jim. You might know what every one of them is capable of and push them to their limits, but all the audience wants is to see what they paid for. They would be happy with just the house lights."

At the time I was a bit upset. Lighting was, and is, a passion I hold dear. Of course it matters — it sets the atmosphere. You don't book a rave without strobes, or a ballet with them — except that one time I did it by accident, but that is a story for another time. After sitting back from it for a while — okay, maybe a year or three — it made sense. The audience came to see the performer, not my lighting. The lighting adds to the performance.

Rant within a rant aside, it is the same thing in the truck. The audience watching on their television, phone or tablet does not care about the gubbins between them and the show. They just want to see the performance. The wall is your world. The festival is theirs. You are separated by a screen, and that screen is the thinnest barrier in broadcasting.

The wall is not a scoreboard

The wall is not a scoreboard. It does not show you who is winning. A decoder that is locked is not winning. A decoder that is unlocked is not losing. A decoder that is locked is healthy. That is all. The wall shows you health, not performance.

And health can be misleading. I have seen a decoder locked and delivering picture so soft it looked like it had been filmed through a shower curtain. The wall showed green. The programme showed mush. The wall shows you connectivity, not quality. It shows you whether the stream is arriving, not whether the stream is worth watching. That is your job. The wall is the data. You are the decision-maker.

The wall is also a reminder that the festival is not a competition. The Royal Hall is not competing with the Black Lion. The Priory is not competing with the Spa Gardens. The venues are not competing with each other. The wall shows you all of them simultaneously, and it is tempting to think of it as a leaderboard — the Royal Hall has the most impressive picture, South Beach has the worst, therefore the Royal Hall is winning. That is not how it works. The festival is a shared experience. The wall shows you the system that delivers it. It does not show you who is winning, because nobody is winning. The audience is watching. That is the only result that matters.

What the wall does to your decisions

The wall does not make decisions. You do. But the wall makes those decisions faster, harder and more consequential than they would be without it.

The director looks at the wall and decides. Cut to the Royal Hall. Hold on the Black Lion. Cut to the Priory. The decision happens in a fraction of a second. The wall shows you the data. You process the data. You make the decision. The decision is editorial. The wall is technical. The two are related, but they are not the same.

And the decisions are not reversible. When you cut from the Royal Hall to the Black Lion, the audience sees the Black Lion. You cannot un-cut. You cannot ask the audience to forget what they saw. The wall shows you the consequences of your choices in real time. Every cut is permanent. Every transition is a commitment. The wall is a reminder that every decision matters, and that the wall does not give you a second chance.

I have made a cut I regretted. We all have. You cut to a venue too early, before the act is ready. You cut away from a venue too late, after the moment has passed. You hold on a feed that drops, and the audience sees black for three seconds that feel like three hours. The wall shows you the mistake. The wall shows you the consequences. The wall shows you that you cannot undo it. And then the wall shows you the next feed, and the next decision, and the next cut, because the festival does not stop for your regrets.

I have been that person — the one who finds out after it is far too late. when I was in high school I had my own weekly show on a community radio station. It was lacklustre, and I knew it. I had accepted that I am not a personality; I am tech support. Then, before one broadcast, I was told the sound console was not working, so we were using a set of CDJ DJ decks with a mic input. I decided that week I was going to give it my all. I plucked up the courage, resolved to be a proper on-air personality, and pressed the button I thought brought me on air. It played a stupid sound effect, and I did not notice that I had never actually switched the microphone on. Every few tracks, the listener heard that sound effect, then a minute of silence, while I chatted away to nobody for the whole hour. I found out about fifteen minutes after the show ended. I was mortified. It was not long after that my radio career ended in embarrassment.

The wall cannot protect you from that feeling. It can only show you the mistake while it is still yours to fix — and that is the whole point of the wall. Better to see the consequence on the screen than to find out, like I did, fifteen minutes after the show.

What the wall cannot do

The wall is a technical tool. It shows you the health of the system. It does not show you the health of the festival. The wall can tell you that a decoder is locked, but it cannot tell you whether the audience is enjoying the programme. The wall can tell you that an encoder is running, but it cannot tell you whether the audience is engaged. The wall can tell you that the audio levels are correct, but it cannot tell you whether the audience is moved.

The festival's health is measured by the audience's experience. The wall cannot measure that. Only the audience can measure that.

The wall also cannot tell you what happens next. It shows you what is happening now. It does not show you what will happen in five minutes, when the Royal Hall headline starts, when the Black Lion changes over, when the Priory's interview finishes. The wall is a snapshot. The festival is a stream. You are watching one frame of a movie that is still being written.

The wall is the crew's common ground

The wall is the place where every crew member looks. The technical director stands in front of it. The audio engineer glances up from the Fairlight panel. The graphics operator checks it between lower thirds. The production coordinator watches it while fielding calls from three venues. Every crew member looks at the wall. Every crew member sees the same thing. The wall is the shared reality of the truck. It is the only place where the entire crew is looking at the same data at the same time.

That shared reality matters more than you think. When the technical director says "the Black Lion has dropped," the audio engineer does not need to check. They saw it on the wall. When the production coordinator says "the Royal Hall is running long," the graphics operator does not need to ask. They saw it on the wall. The wall is the crew's common language. It is the thing that makes six people behave like one unit.

And when the show starts, the wall disappears. Not literally — the screens are still there, the feeds are still arriving, the status indicators are still blinking. But the crew stops seeing the wall. The crew sees the programme. The crew sees the festival. The crew is focused on the next cut, the next transition, the next audio balance. The wall is there, but it has become invisible. It has done its job. It has given the crew the information they need to make the decisions that matter. And now the crew is making those decisions, and the wall is just the surface they are looking at while they do it.

That is the wall's final gift. It shows you the anxiety. It shows you the sixteen feeds, the seven outputs, the dozens of status indicators. It shows you everything that depends on this truck. And then the show starts, and the anxiety becomes focus, and the focus becomes the festival, and the wall disappears, and all that remains is the programme.

And the crew. The crew remains.

Chapter 8: Recording the Town

The live programme is what the festival says now. The recording system decides what it can say later.

Six HyperDeck ISO Recorder 100Gs sit in the rack. Each one can subscribe to sources across the 100G IP environment, so on paper the channel count is substantial. Capacity is not an allocation plan. The truck still has to decide which incoming venue services, central programmes, clean feeds and outbound channels deserve continuous recording — and where those records are stored, how long the storage lasts, and how the files are identified after the event.

Recording is not monitoring

The multi-view wall shows the state of the system. The recorders capture the programme. The two are related but different. Monitoring tells you what is happening now. Recording tells you what happened. The wall is a snapshot. The recording is an archive.

The recording also does not show you the quality of the source. The recorder captures the signal that arrives. If the signal is clean, the recording is clean. If the signal is dirty, the recording is dirty. The recorder cannot fix a bad source; it can only capture what arrives. If the Black Lion sends a distorted stereo from the back of the room, the recording preserves a distorted stereo from the back of the room — faithfully, and to nobody's benefit. Recording quality is bounded by source quality, and the sooner that is agreed, the fewer arguments there are on Monday morning.

The town records at three depths

The truck records what arrives at the truck. The town records too — at three different depths, depending on what each venue can do.

The professional venues, like the Royal Hall, record everything: every camera and every microphone, captured separately as their own ISO records — individual sources, isolated so they can be mixed and edited later. That rawest material never leaves the building — the truck only ever sees their chosen SRT contribution. That is not a loss. It is the best version of the show, waiting to be edited later, closer to the stage than the truck can ever sit.

The middle tier records its own programme. A venue with a local switcher but without an ISO rig produces and records its finished local show — a better picture than anything the truck caught, because it came from the venue's own cuts and its own audio.

And the smallest stages — the fringe rooms, the pop-ups, the phones on South Beach — record nothing at all. Whatever happens there is only recorded if the truck caught it.

So the six HyperDecks are the town's safety net, not the town's best archive. Whatever a venue could not capture itself, the truck recorded centrally, because it recorded everything that arrived. Nobody who played a stage is left unwitnessed.

The obvious priorities

The first priority is the central programme — the director's cut that moves between venues. That is the festival's official record: the version the audience saw, the version that can be replayed, edited, excerpted and shared. It runs with continuous timecode, so every moment can be located after the event. If the HyperDeck carrying the programme fails, nothing else records the programme exactly as it played out. That is the single most important connection in the recording plan.

The incoming satellite programmes matter too. Those are the town's local records as received by the truck — the contribution that master control actually saw, network artefacts and interruptions included. Recording them centrally protects the history of what arrived, not what was meant to arrive.

The outbound services may also deserve transmission records for compliance, catch-up or fault review. The six HyperDecks bring enough channel capacity to make those choices possible, but the channel map should be written before the show. Recorder 1, channel 1 should not become an archaeological question on Monday morning.

The professional venues' own archives sit alongside all of this. The central record preserves what arrived. The Royal Hall's ISO files answer the questions only source-near material can.

Cloud Store Ultra 48TB

The Blackmagic Cloud Store Ultra 48TB is the truck's shared memory. It is a 1RU network storage system built around twelve M.2 NVMe flash cards — 48TB of capacity with RAID 5 data protection and two 100G QSFP28 Ethernet connections. Each port can carry its own IP address and subnet for load balancing, up to 200G aggregate bandwidth with the right switching, and it serves SMB and NFS to as many as two hundred computers. It has its own 1G management connection, SDI and HDMI monitoring outputs if you want storage status on a screen, two power supplies and front-to-rear cooling. It is a proper piece of kit, and it belongs in this truck.

The important phrase, though, is shared storage. The HyperDecks record to a location the Mac Studios and the post-production team can access. Editors can begin working with material while the festival is still happening. The recording no longer has to be copied out of six isolated boxes before anybody can use it. That is the difference between a pile of files and an archive.

Recorder versus storage

The HyperDeck creates the media file. The Cloud Store holds and shares it. Neither device replaces the other, and neither automatically creates an archive strategy. This distinction matters more than it sounds. RAID 5 protects against an internal media failure — one drive dies, the data survives. It is not a second copy in another place. Two power supplies protect against one supply fault. They do not protect against the loss of the truck's entire electrical environment. Cloud synchronisation can create useful off-site distribution, but it depends on bandwidth, credentials and time. None of those is the same as a backup.

The festival therefore needs a retention policy, decided in daylight. What remains on the Cloud Store during the event? What is copied elsewhere? Which material is retained after post-production, and who has authority to delete files when capacity runs low? Forty-eight terabytes sounds enormous until several dozen high-quality streams begin writing continuously.

Capacity is measured in hours

The true storage duration depends on the number of channels, the codec, the resolution, the frame rate and the chosen quality. The truck should not publish a confident number until those settings are fixed. The recording plan needs to calculate a data rate per service, multiply it by the simultaneous channel count, and leave operational headroom. RAID configuration may also eat into the usable capacity.

The calculation should include the whole day, not only the headline sets. Changeovers, presenter links and fault periods may all be editorially useful. Starting a recorder late to save space can remove the exact context the editor needs later. Storage becomes a schedule decision, not a server decision.

The archive needs to explain itself

Every file should identify venue, service, date, programme segment and source type. The central programme should not be confused with the Royal Hall programme. A clean feed should say that it is clean. An outbound service should identify the service, not merely the encoder number. Timecode and clock relationships need to be understood across received contributions. Because the public-internet feeds arrive with different delays, the central record captures each service as it arrived, and local camera recordings may need alignment during post-production. The archive is useful when somebody who was not inside the truck can understand it.

That is the bar. The recordings exist so the festival can be remembered properly — and remembered means understood, not merely stored. The archive is the festival's legacy, but it is a legacy that has to explain itself.

On the night, the copy that is guaranteed to exist is the truck's, so the first on-demand versions after the festival are built from it. As the venue-proximate material arrives — the Royal Hall's ISO files, the local programme cuts — those first versions are replaced by higher-quality, edited ones made from better sources. The truck recording is not meant to be the best version of anything. It is the version that guarantees the festival was witnessed, while the better version catches up from closer to the stage.

Chapter 9: The Crew Is the Command Nexus

five people can staff the Command Nexus. That does not mean five people will be comfortable. It means six people can run the system. And if those six people trust each other, communicate without ceremony, and share the kind of quiet authority that comes from knowing what they are doing, they can deliver a festival that makes a town feel like it is all happening in one room.

The crew is not a collection of job titles. It is a collection of people who have spent twelve hours together in a room the size of a small garage, who know each other's rhythms, who know when someone needs coffee and when someone needs silence. That knowledge is not in any manual. It is earned.

The technical director

The technical director is the person who remains calm when everything else is on fire. Not literally — although I have seen a rack power supply let out a puff of smoke that caused a moment of genuine concern — but figuratively. The wall of multi-view screens is terrifying. The sixteen feeds are overwhelming. The crew is looking at the technical director to see whether they should be worried. If the technical director is calm, the crew is calm. If the technical director panics, the crew panics. The technical director's composure is the crew's anchor.

The technical director does not make every decision. That is a common mistake. The audio engineer makes audio decisions. The graphics operator makes graphics decisions. The comms engineer makes comms decisions. The production coordinator makes coordination decisions. The technical director oversees these decisions. They do not make them. The technical director's job is to make the decisions that nobody else can make — the editorial calls, the resource conflicts, the moments when two venues need the same thing at the same time. The technical director decides. Everyone else executes. That is the contract.

The technical director also communicates. They talk to the crew. They talk to the venues. They talk to the production team. They are the hub of the truck's communication network, the place where information arrives and from which decisions depart. A technical director who cannot communicate is a technical director who will lose the crew. The wall shows the data. The technical director translates the data into decisions. The crew executes the decisions. That is how the festival is delivered.

The audio engineer

The audio engineer sits at the Fairlight panel for twelve or fourteen hours, riding gain on a mix that changes character every time the director cuts from one venue to another. The Royal Hall's headline act sounds nothing like the Priory's acoustic set, and the audio engineer has to compensate for that difference in the time it takes the director to press the transition button. That is not a technical job. That is a musical job. The audio engineer is the festival's conductor, keeping the programme in tune as it moves between rooms.

The audio engineer does not mix every venue. The venues mix themselves. The audio engineer mixes the programme — the festival-wide service that cuts between venues. They match loudness, protect transitions, manage the central presenter's microphone, and make sure the audience never reaches for the volume control. When they do their job well, nobody notices. When they do their job badly, everybody notices. That is the audio engineer's curse: perfection is invisible.

The graphics & Playback operator

The graphics & Playback operator triggers the lower thirds, the titles, the sponsor material and the continuity graphics. The graphics are created before the show — the graphics operator does not design them during the programme. The graphics operator's job is to play the right graphic at the right moment. That sounds simple until you try it. The presenter introduces a venue, and the lower third needs to appear within a second. The festival opens, and the title needs to be on screen before the first note. The sponsor needs a mention between venues, and the graphic needs to be cued and ready. The graphics operator is always one step ahead, always ready, always watching the wall for the cue.

They also manage the holding loops, the idents, the pre-recorded packages and the emergency slates. When a venue drops and the director needs a safe source, the playback operator presses a button and the holding loop appears. No panic. No scrambling. Just a button press and a loop that buys the crew thirty seconds to fix the problem. The act as the crew's safety net. They are the person who makes sure the programme never goes to black.

The comms engineer

The comms engineer keeps the crew talking. The technical director talks to the venues. The audio engineer talks to the audio operators. The graphics operator talks to the production coordinator. The comms engineer makes all of these conversations possible. They manage the intercom, the party-line, the IFB and the venue connections. When the Royal Hall calls the truck, the comms engineer routes the call. When the Black Lion needs to talk to engineering, the comms engineer connects them. The comms engineer's success is the crew's seamless communication — and the best comms engineers are invisible. The crew does not notice the comms. The comms just work.

The production coordinator

The production coordinator is the person who knows what is happening before it happens. The running order is a plan, and the production coordinator knows how the plan will break. The Royal Hall is running long. The Black Lion is running early. The Priory needs a break. The production coordinator anticipates these changes, prepares the crew, and translates the running order into choices the technical director can use. They are the truck's early warning system, the person who turns chaos into decisions.

I have worked with production coordinators who could hear a running order change coming before anyone said it. They would look up from their laptop, glance at the wall, and say "the Royal Hall is going to run over by three minutes." And they were always right. That is not clairvoyance. That is experience. That is knowing the rhythm of a festival well enough to feel when it is about to change.

Five people, one unit

five people can staff the Command Nexus. Five people can run the system. Fivr people can deliver the festival. But only if they work as a unit.

The unit works because each crew member trusts the others. The technical director trusts the audio engineer to protect the programme's sound. The audio engineer trusts the graphics operator to play the lower thirds at the right moment. The graphics operator trusts the comms engineer to keep the intercom clean. The comms engineer trusts the production coordinator to have the running order updated. That trust is the unit's foundation. It is not given. It is earned.

The unit also works because each crew member can override the others when the programme demands it. The audio engineer can refuse to play a mix that is wrong. The graphics operator can refuse to play a graphic that is incorrect. The comms engineer can refuse to route a call that is inappropriate. Every crew member has the authority to protect the programme. That shared authority is the unit's immune system.

The crew is the Command Nexus. The technology is the infrastructure. The crew operates the infrastructure. The infrastructure delivers the festival. The festival is the audience's experience. The crew is the beginning of that chain.

The audience does not see the crew. The audience sees the festival. But the crew is there, behind the screens, behind the panels, behind the wall. The crew is the festival's invisible workforce. The crew is the reason the wall disappears. The crew is the Command Nexus.

Chapter 10: When the Town Goes Dark

The Command Nexus is built to deliver the festival. It is also built to survive the festival's failures. The system design assumes that things will go wrong. Decoders will fail. Encoders will drop. SRT streams will disconnect. Power will fluctuate. The system design assumes that the town will go dark.

That assumption is not pessimism. It is preparation. A system that assumes failure is a system that can survive failure. A system that assumes perfection is a system that will fail the moment perfection does not arrive. And perfection never arrives. That is the first lesson of live production, and it is the lesson that separates a crew that has done this before from a crew that is about to learn it the hard way.

Eight failure scenarios

The Command Nexus faces eight distinct failure scenarios. Each has a different cause, a different symptom and a different response. The crew needs to know all eight. The crew needs to have rehearsed all eight. And the crew needs to know the response to each one so well that it becomes instinct — because when a decoder drops mid-show, you do not have time to consult a manual.

Scenario 1: Single decoder failure. One SRT stream drops. One venue disappears from the multi-view wall. This is the most common failure and the least dramatic. The director cuts to a healthy venue. The comms engineer contacts the venue. The venue restarts their encoder. The stream returns. The director cuts back. The audience sees a brief change of venue. The audience does not see a failure. I have seen this happen dozens of times. It is never a problem if the crew is prepared. It is always a problem if the crew is not.

Scenario 2: Single encoder failure. One encoder drops. One service disappears. The crew switches the service to the flexible encoder — the eighth, held back as backup for exactly this. The audience sees a brief disruption. The crew diagnoses the fault. The encoder is repaired or replaced. The service returns. This is the scenario that gives the flexible encoder its second job — backup, after coverage. It has never been exciting. It is the most relied-upon piece of flexibility in the truck.

Scenario 3: Multiple decoder failure. Two or more SRT streams drop. Two or more venues disappear. The director cuts to healthy venues. The comms engineer contacts the failed venues. The venues restart their encoders. The streams return. The director restores the programme. The audience sees a reduced festival. The audience does not see a total failure. This is the scenario that tests the crew's ability to triage. Which venue do you bring back first? The answer is always the one that matters most to the programme — and that is an editorial call, not a technical one.

Scenario 4: Switch failure. One of the Ethernet Switch 820s fails. All sources connected to that switch are lost. The director cuts to sources on healthy switches. The engineering team diagnoses the switch. The switch is repaired or bypassed. The sources return. This is the scenario that justifies the star topology. If the switches shared a single point of failure, a switch failure would take down half the festival. With the star arrangement, a single failure is an inconvenience, not a catastrophe.

Scenario 5: Power failure. The truck loses mains power. The UPS keeps the system alive for thirty minutes. The crew continues the programme. The engineering team diagnoses the power failure. The generator starts. The power is restored. The UPS is recharged. The audience sees a continuous programme. The audience does not see a power failure. I have been in a truck when the mains power dropped. The UPS held. The programme continued. Nobody in the audience knew. That is the point.

Scenario 6: Audio failure. The Fairlight panel loses a source. The audio for one venue drops. The audio engineer fades to the emergency bed. The comms engineer contacts the venue. The venue restores the audio. The audio engineer fades back. The audience hears a brief change in the audio. The audience does not hear a silence. This is the scenario that the audio engineer dreads most. Silence is the enemy. A moment of silence feels like an eternity to the audience. The emergency bed is the safety net, and the audio engineer's reflex is the safety net's trigger.

Scenario 7: Graphics failure. The HyperDeck or the graphics computer fails. The lower thirds or titles disappear. The graphics operator switches to a backup source. The programme continues without graphics. The crew diagnoses the fault. The graphics return. The audience sees a brief absence of graphics. The audience does not see a total failure. Graphics are the festival's visual identity. Without graphics, the programme looks unfinished. But unfinished is better than dead.

Scenario 8: Total system failure. The entire Command Nexus fails. All decoders, all encoders, all switches, all graphics. The crew activates the disaster recovery plan. The programme switches to a pre-recorded holding feed. The audience sees a holding loop. The crew diagnoses the fault. The system is restored. The programme returns. This is the scenario that nobody wants to think about. This is the scenario that the entire system design is built to prevent. And this is the scenario that the crew rehearses most often — because if it happens, the crew needs to respond without thinking.

The response hierarchy

Every failure scenario gets the same hierarchy. It is not a suggestion; it is discipline, because it makes the crew respond in an order that prevents panic. The first response is always to protect the programme. The programme is the audience's experience and it must continue; everything else is secondary. Diagnose the fault second. Repair the system third.

I have seen crews break this hierarchy — diagnose the fault before protecting the programme, repair the system before communicating with the venues. Every time, the programme suffers, and every time the lesson is the same: protect the programme first. Everything else can wait.

Then communicate: the crew talks to each other, to the venues, to the production team, because communication coordinates the response and stops panic. Then document, so the failure and the response are on the record for next time. Then learn — the fault's only real value is teaching the crew what to fix and what to prevent.

Before the last resort, there is a better tool: the truck's own recordings. A performance recorded earlier in the day can fill a gap, an interview can be replayed, a highlights reel can hold the audience while a venue recovers or a changeover runs long. Run on the mixed feed behind a festival replay ident, recorded material keeps the festival on screen without ever pretending to be live. The recordings are not only the archive; they are the programme's time-buffer.

The disaster recovery plan and the rehearsal

The disaster recovery plan is the last resort, the plan that keeps the festival alive when the whole Command Nexus dies. It is simple, and Scenario 8 already described it: the programme switches to a pre-recorded holding feed — festival highlights, presenter positions, continuity material — so the audience sees a festival that is temporarily paused rather than a dead screen. The holding feed exists for exactly one reason: to buy the crew time to diagnose, repair and restore.

The plan is only as good as the rehearsal. On paper it is a document; the rehearsal makes it real. Rehearsal reveals the plan's weaknesses, the crew's gaps and the festival's vulnerabilities long before the audience can experience them. I have been part of events where the rehearsal was skipped or treated as a formality, and venues where it was taken seriously. The difference between them was the difference between a crew that panicked and a crew that responded. Rehearsal is not optional. It is the plan.

When the town goes dark, the crew stays lit

The festival's most dramatic moment is not a headline act or a surprise performance. It is the moment when the town goes dark. When the power fails. When the decoders drop. When the encoders fail. When the system collapses.

The crew stays lit. The crew keeps working. The crew keeps communicating. The crew keeps the festival alive. The crew is the Command Nexus. The crew is the festival's last line of defence. The crew is the reason the festival survives.

The town goes dark. The crew stays lit. The festival continues. The audience sees the programme. The audience does not see the failure. The audience sees the festival. The crew sees the wall. The crew sees the failures. The crew fixes the failures. The crew keeps the festival alive. That is the Command Nexus. That is the system. That is the crew. That is the festival.

Chapter 11: Eco-Reality and Closing

What fits in the truck

A vehicle that can be parked in Bridlington, cabled to the mesh and operated by a single crew at town scale is not the same thing as a vehicle that runs for hours without external power. The Command Nexus can survive a short power interruption. It is not a green-power showcase. And that is worth saying honestly, because the temptation in any modern festival plan is to pretend that the technical infrastructure is cleaner than it is.

That temptation is understandable. Nobody wants to be the person who says "our broadcast truck runs on diesel." But the Command Nexus is a realistic, grid-connected, diesel-backed production tool. That is what it is. Pretending otherwise does not help the festival. It hurts the festival's credibility.

The festival can still pursue a responsible operational approach elsewhere. Local venues can reduce unnecessary lighting. Outdoor stage power can be managed. The town can encourage transport plans that reduce car movements during the festival. Those are real, practical steps that have a direct local effect. They do not require the Command Nexus to be something it is not.

Power and efficiency

The Command Nexus can turn off idle rack gear when it is not needed. The crew can shut unused processing and control surfaces during programming and rebuild time. The power budget can include planned rest periods. Those steps matter. They do not make the vehicle carbon-neutral. But they reduce the footprint, and reducing the footprint is better than pretending the footprint does not exist.

The festival can also encourage other local venues to manage power. If the festival's power plan acknowledges that the Command Nexus is a realistic production tool, the town may be more willing to engage than it would be if the festival pretended to be greener than it is. Honesty builds trust. Trust builds engagement. Engagement builds a better festival.

Lifecycle awareness

The Command Nexus is built from professional broadcast equipment. That equipment has a useful life. When the festival replaces machines, it should prefer units that can be resold, reused or recycled. The festival should not assume that new kit automatically equals better practice. Sometimes the most sustainable decision is to keep a reliable machine running for another season.

I have seen productions and venues replace perfectly functional equipment because it looked old. I have seen venues keep equipment running long past its useful life because replacing it was expensive. The answer is somewhere in between. The answer is thoughtful replacement — replacing equipment when it no longer serves the event, not when it no longer looks impressive.

The festival can also use the Command Nexus as an educational tool. The festival can invite local colleges and schools to see the truck. The festival can show the town how broadcast technology works. The festival can explain the power requirements, the cooling requirements, the waste management requirements. The truck can be the festival's most visible educational resource — a place where the town can see how the festival is delivered, and why it costs what it costs.

Local impact

The Command Nexus draws power. It generates heat. It needs a parking space. It needs crew food and water. All of that has a local footprint. A town plan should acknowledge that footprint and manage it. That is more honest than pretending the festival's technical infrastructure has no cost.

There are practical ways to reduce the truck's footprint. The crew can use local food vendors, local transport and local accommodation — which supports the town's economy while the town supports the festival. The relationship is reciprocal. The truck is a guest in the town. The town is the truck's host. The festival is the reason they are both here.

There is also noise. The generator makes noise. The cooling system makes noise. A truck running through the night is not something you want next to someone's bedroom window, and a festival that ignores that is asking for trouble. Schedule the loud stuff for waking hours, tell the neighbours what is happening, and treat the truck like a guest rather than an invader.

The recordings also mean the festival does not have to end when the last venue closes. The main channel could keep the town's night alive with replays, interviews and highlights after the stages pack up. That is a real possibility and a real decision: it needs a 24-hour rotation of crew, power and attention, and a conversation with the neighbours who would hear the generator while they sleep. It is not a promise the first festival should make. It is a door the recordings leave open for the festivals that follow.

And there is waste. Cables end up in skips. Coffee cups end up in bins. The festival generates waste, the truck generates waste, and the crew generates waste. Provide recycling bins. Dispose of waste properly. Do not leave a mess and call it a festival. Be a responsible guest.

The Command Nexus is not the festival

The Command Nexus is the festival's technical infrastructure. It is not the festival itself. The festival is the singer in the Black Lion who makes the audience forget the outside world, the interview at the Priory that makes them think, the headline at the Royal Hall that makes them sing, the outdoor stage at the Spa Gardens that makes them dance. The Command Nexus delivers all of it. But the festival is bigger than the Command Nexus.

The crew stays until the job is done

The crew stays after the audience leaves. They stay to pack the truck, coil the cables, check the recordings and verify the archive. The festival is not over when the audience leaves; it is over when the truck is packed and the archive is secure. Responsibility does not end with the last song. It ends with the last cable.

Then the truck goes home. It goes home because it is a tool — a powerful tool, a complex tool — but a tool. The festival is the experience; the truck is the tool that delivers it. When the festival returns next year, the truck returns with it: the same cables, the same switches, the same wall, the same crew.

Closing

The Command Nexus is the festival's technical heart. It receives sixteen feeds, processes them, routes them, records them and distributes them. It draws power, generates heat, needs a parking space and needs crew food and water. It is staffed by people who have rehearsed what to do when it goes wrong. It is a realistic, diesel-backed, grid-connected production tool — not green, not carbon-neutral, and honest about both.

And the archive remembers it all long after the truck has gone home. The trucks come and go. The festivals come and go. The wall comes and goes. But the archive endures. And the archive is the reason the festival is shared, remembered and understood — by the town, and by whoever discovers it later.