You can have a room full of expensive kit and still lose the show to one bad protocol decision. The usual failure isn't dramatic, either. It starts as a delay in cueing, a lighting desk that can't see a node, or audio that comes up clean in rehearsal and drifts once the room fills and the network gets busy.
That's why communication protocols matter so much in London venues. They decide how devices talk, how faults surface, and whether your crew spends the afternoon fixing a network or focusing on the show. In temporary event builds, the wrong choice usually doesn't fail politely.

Why Protocol Choice Matters on Show Day
The first time most crews feel protocol pain is not in the office, it's in a London venue with the doors already open. A corporate keynote is due to start, the audio desk is waiting on networked outputs, the lighting programmer wants cues to land on time, and the video op needs confidence that the playback chain will stay in step. If one layer is badly chosen, every department starts blaming the next.
That's because communication protocols are the invisible rules underneath the event. The historical roots go back to the UK's own NPL work in 1967, when the memorandum titled A Protocol for Use in the NPL Data Communications Network helped define the modern meaning of protocol in data communications, built around Donald Davies's packet switching research at the National Physical Laboratory, and it predates the formal ARPANET TCP/IP era by more than a decade (communication protocol history). That matters on show day because the same idea, formal rules for how devices exchange information, still decides whether a room behaves like a system or a pile of separate boxes.

What goes wrong when the wrong layer is chosen
On live work, the failure pattern is usually predictable. A protocol with weak timing discipline may pass basic tests, then drift once the room becomes active. A protocol that looks elegant on paper may be a headache if the venue layout forces long cable paths, noisy power, or mixed manufacturer gear that doesn't interpret the traffic the same way.
Practical rule: if the system only works when every patch lead is perfect, it's not resilient enough for a live room.
That is why event teams should think in terms of interoperability, timing, and fault recovery, not just whether the connection is “networked”. A show day needs devices to converge on the same state quickly, then stay there when the room gets busy. If they don't, the pain usually appears as late cue execution, silent endpoints, or intermittent sync problems that are hard to reproduce under pressure.
What Communication Protocols Actually Control
At a basic level, communication protocols are the formal rules that govern transmission between two or more network points, including physical transmission, data format, channel sharing, error detection, authentication, and timing-related behaviour (formal protocol breakdown/U0611174180.pdf)). In practical AV terms, that means they define not just what gets sent, but how devices agree on who speaks, who listens, and how they know the message arrived intact.
Think of a protocol as the stage manager for a network. Without one, every device would be trying to talk at once, and none of them would know whether the message made sense on the other side. With one, the system has rules for framing the message, checking it, and deciding what to do when something goes wrong.
The mechanics that matter on site
A protocol usually controls five things that crews feel during setup and operation.
- Message format: The device needs to know how information is packaged so it can be read correctly.
- Channel sharing: Multiple devices may need the same path, so the protocol defines how they take turns.
- Error detection: Bad data should be spotted before it becomes a visible fault.
- Authentication: Control traffic must be limited to trusted devices where security matters.
- Timing behaviour: Some systems need to act together, not merely eventually.
That last point is where AV work gets unforgiving. Lighting cues, distributed audio, and device telemetry all depend on predictable timing. A protocol that handles that well can keep a system tight. One that doesn't may still pass traffic, but it won't pass a show.
For a useful comparison outside AV, the way voice systems carry traffic over IP is a good example of how transport rules shape behaviour. Nutmeg Technologies' guide to VoIP business benefits explained is a sensible read if you want a simple business-side parallel to the same underlying idea, message handling changes the whole user experience.
Good protocol design is invisible when it works and painfully obvious when it doesn't.
That's why experienced engineers treat protocol selection as part of system design, not an afterthought. The workflow is not just “get data across”. It is “get the right data across, on time, with errors surfaced early enough to fix them before the audience notices.”
Key AV Protocols and Where Each Earns Its Place
The AV world is full of protocols that look similar until you put them into a live venue. Some are built for audio transport, some for video distribution, some for lighting control, and some for sync. Mixing them without understanding the trade-offs is where show-day friction starts.
For a deeper overview of IP-based transport in AV systems, this internal guide on AV over IP fundamentals is a useful companion to the practical comparisons below.
| Protocol | Primary Use | Typical Latency | Best For | Limitations |
|---|---|---|---|---|
| Dante | Networked audio | Very low in practice | Large audio systems, flexible routing, multi-channel audio over IP | Needs proper network design and vendor compatibility planning |
| AES67 | Interoperable audio over IP | Low, depending on implementation | Mixed-manufacturer audio environments | Interop can be uneven if devices only partially support the standard |
| NDI | Network video transport | Low for many production uses | Fast-moving video workflows, software-centric production | Can become demanding on network capacity and design |
| SDI | Baseband video transport | Very low | Reliable point-to-point video paths | Less flexible for distributed IP-based systems |
| Art-Net | Lighting over IP | Low enough for many lighting tasks | Smaller to mid-size lighting networks | Not every environment likes it, especially when networks are crowded |
| sACN | Lighting over IP | Low enough for many lighting tasks | Larger lighting setups and structured multicast use | Needs disciplined network planning to stay clean |
| SMPTE timecode | Synchronisation | Timing reference rather than media transport | Cue alignment across departments | It synchronises, it does not carry the full production signal by itself |
Dante and AES67 often sit in the same conversation because both solve audio transport, but they don't solve it in the same way. Dante tends to be attractive when you want managed routing and a controlled ecosystem, while AES67 matters when interoperability across different manufacturers becomes the priority. The catch is that mixed environments can be awkward if each endpoint implements the standard differently in practice.
For video, NDI is convenient in software-heavy production workflows, while SDI remains a reliable choice when you want a stable, direct path and minimal ambiguity. The same split shows up in lighting. Art-Net is easy to deploy in the right environment, while sACN is often the cleaner choice when you want structured distribution and network discipline.
If you're checking transport concepts around cloud voice or mixed media systems, the discussion of RTP ports in cloud PBX is a good reminder that packets only help if the network around them is designed properly. In live events, that is an important lesson. A protocol does not rescue a poor topology.
London Venue Constraints That Shape Protocol Decisions
London venues do not behave like a lab. You're often dealing with listed buildings, narrow risers, shared infrastructure, and cable paths that were never designed for modern AV density. Even where the room is brand new, adjacent systems and temporary builds can create enough electromagnetic noise to make a careless protocol choice expensive.
That is where the physical side of protocol selection starts to matter. The practical guidance is simple, choose the protocol layer that fits the worst-case environment, not the most convenient one. Reliable transport becomes more important when cable runs get longer, the air gets noisier, or the venue forces awkward separation between control positions and endpoints (industrial communication trade-offs).
What changes from one venue to the next
A conference floor at a large docklands site feels very different from a tight Shoreditch warehouse. In one space, you may have long distribution paths, structured network racks, and plenty of room for planned routing. In the other, you may be threading cables through narrow routes, sharing power with multiple suppliers, and working around unpredictable reflections from building materials.
The protocol decision follows the building.
- Longer cable routes: favour transport that tolerates distance and still keeps error handling clean.
- Dense RF or electrical noise: favour systems that remain stable when the venue environment is hostile.
- Limited power and patch access: favour architectures that reduce on-site rework.
- Mixed manufacturer kit: favour clearer interoperability, even if setup takes a little longer.
A USB-led approach is often where temporary event planning goes wrong. USB is typically limited to 5 metres without signal-integrity issues, so it stops being a sensible primary interconnect for large rooms, exhibition halls, and multi-zone productions (USB distance limit). That pushes most real-world London event builds towards networked or bus-based protocols once devices are physically separated.
For venue planning that leans heavily on distributed connectivity, this internal note on WiFi for events helps frame why wireless convenience only works when the underlying design is disciplined. Wireless can be useful, but it is not a substitute for a well-planned control architecture.
The experienced move is not to fight the venue. It's to map the space, understand where interference or distance will hurt, then choose protocols that can survive those conditions without heroic patching during doors.
Matching Protocols to Event Requirements
Protocol choice gets easier when the brief is translated into operational questions. What matters most, low latency, cross-brand compatibility, or the ability to recover cleanly from faults. Those are different goals, and each one pushes the build in a different direction.
A corporate conference with several breakout rooms usually rewards simplicity and clear segmentation. You want a control structure that is easy for the crew to understand, easy to troubleshoot, and unlikely to fail because one room's traffic bleeds into another. A product launch with tightly choreographed sound, picture, and lighting places more weight on sync and cue accuracy. A multi-stage festival asks for distributed control and a network that stays calm when several teams are active at once.

The questions to ask before anything gets patched
Before a build is signed off, the production lead should be asking practical questions, not brand questions.
- How far apart are the devices: Distance changes what remains reliable.
- How mixed is the kit: Interoperability becomes critical when the system spans multiple manufacturers.
- How tight is the timing: Sync-heavy shows need predictable coordination.
- How much crew expertise is available: Simpler systems can be the right call when the team is lean.
- What happens if one segment fails: A protocol only looks good until it breaks under load.
For event teams that need a quick reminder on connectivity planning, the internet failover guide for home is a useful plain-language reference on why backup paths matter. The same mindset applies in live events, because resilience is not an abstract nice-to-have. If the primary path drops, the show still has to carry on.
A simpler protocol is often the right choice when the event is routine, the crew is small, and the venue is awkward. A more advanced stack earns its keep when the show has enough moving parts that small timing errors become visible to the audience. The decision is not about using the most advanced option. It's about using the least complicated option that still protects the show.
Designing Resilient Event Networks
Resilience starts before the first cable is laid. The strongest live networks are usually boring on purpose, because they separate control traffic from media traffic, build in sensible fallbacks, and avoid making any one device or switch the single point of failure. That calm behaviour on show day is the result of a deliberate architecture, not luck.

Layered design beats heroic troubleshooting
A resilient build usually starts by keeping functions separate. Control traffic, media streams, and admin access should not all ride through the same uncontrolled path if there's a practical alternative. VLAN segmentation is useful here because it helps contain problems, reduce chatter, and keep fault domains smaller when a device misbehaves.
The second layer is redundancy, but not the theatrical kind. A backup route only helps if the crew knows when it takes over and what happens to the active endpoints. Proper planning means choosing protocols that recover cleanly, then proving that recovery under load before the audience arrives.
Practical rule: design for the worst cable route, the worst noise floor, and the least forgiving changeover, then test to that standard.
Networked events often go wrong because teams focus on raw bandwidth and forget that fault handling matters just as much. A system with plenty of capacity can still feel fragile if it doesn't isolate failures well or if a minor mispatch drags the whole room into trouble.
The video below gives a useful visual on how protocol layers fit into a structured event network.
For venue-scale planning, the internal guide on network infrastructure planning connects directly to this point. The best networks are designed around the physical environment first, then the protocol choices are fitted into that layout so the show is less exposed to surprise failures.
Troubleshooting Common Protocol Failures
Most protocol faults on show day are not mysterious. They're usually a mismatch between what the crew expected and what the network was doing. Once you get used to the symptoms, the fixes become much faster.
The usual problems and the fastest fixes
- IP address conflicts: Two devices answer as if they own the same address, which can look like random dropouts or a controller that keeps losing one endpoint. The fix is to check addressing discipline and separate static assignments from anything that is left to auto-configure.
- Subnet mismatches: Devices can see the network but cannot talk cleanly across it. That usually means one part of the system is sitting outside the range the rest of the crew built around.
- Timecode drift: Cues that were tight in rehearsal start to feel loose once the show runs. The cause is often poor sync discipline, so the fix is to verify the reference path before chasing the individual playback devices.
- Multicast flooding: Network traffic spreads too freely and the switches start carrying more than they should. The practical answer is to review segmentation and make sure multicast is only travelling where it's needed.
- Intermittent device discovery: Gear appears during setup, then vanishes under load. That usually points to a network design issue, not a broken box.
When things get messy, the best move is to isolate the fault domain. Pull the system back to a smaller working segment, confirm which protocol is failing, then expand again in a controlled way. Crews lose time when they keep adding devices to a broken network instead of narrowing the problem.
Document the fix as soon as the room is stable. Note the symptom, the cause, the affected protocol layer, and the exact workaround that restored service. That short record becomes valuable on the next build, especially when the same venue, supplier mix, or show format returns.
If the fault affects authentication, timing reference, or anything that could compromise the show's safety or continuity, escalate immediately rather than improvising. The crew on site needs a clean decision, not a long debate.
If you're planning a conference, launch, festival, or hybrid event in London and need the network, audio, lighting, and video layers to behave properly on show day, speak with London Audio Visual Hire. We can help you choose the right communication protocols for the venue, the crew, and the level of resilience the event needs.


