One laptop, one splitter, eight displays in a lobby. Seven light up. The eighth shows nothing, and one of the seven is running at 1080p when it is a 4K panel.
The instinct is to blame the cable on the dead display. Almost always, the answer is in a conversation that happened before any video was sent: the source asked one question, got several different answers, and picked one.
Distribution is rarely a cable problem. It is a negotiation problem, and once you can see the negotiation, the shape of the failure makes sense.
HDMI Is Point-to-Point, So Distribution Is a Negotiation
An HDMI connection is not a video pipe. It is a sequence, and the order matters.
First comes hot plug detect: the display asserts a voltage on the HPD pin, which is the source’s cue that something is connected and awake. Then the source reads EDID from the display over the Display Data Channel, a low-speed bus unrelated to the video lanes. Only after reading that EDID does the source decide what to output. Then, if the content requires it, HDCP authentication begins, and that key exchange must succeed at every device in the chain before a single frame of protected video passes. Finally the link trains, whether that is legacy TMDS signaling or the Fixed Rate Link used by HDMI 2.1 and above.
Everything the source decides comes out of that conversation. Put eight displays on the far side of one splitter and you have asked one source to hold a conversation with eight devices that have eight different opinions.
That is why distribution faults appear as black screens rather than as soft picture quality. A black screen tells you nothing about which step failed, which is why a method beats a bag of spare cables.
The negotiation in order
Splitters, Switchers, Matrix Switchers, Multiviewers
Device | Inputs and outputs | What it solves |
|---|
Splitter | One input, several outputs | The same image on every display |
|---|
Switch | Several inputs, one output at a time | Choosing between sources |
|---|
Matrix switch | Several inputs and several outputs | Routing any source to any display |
|---|
Multiviewer | Several inputs, one output | Many sources consolidated on one screen |
|---|
A splitter is named by its ports, so a two-output unit is a 1×2. The AV trade often calls a splitter with re-driven outputs a distribution amplifier, which describes the electronics rather than a different function.
Four devices, four jobs
Whose EDID Does the Source Get?
EDID is the display describing itself: resolutions, refresh rates, color depth, HDR metadata, and audio formats. The base block is 128 bytes, extended by CTA-861 extension blocks and, for higher-bandwidth modes, DisplayID structures. The source reads it and picks the best format both ends claim to support.
That works cleanly on a single source-to-display run and stops working the moment you introduce distribution, because the question "what does the display support?" has become unanswerable — and the source still gets exactly one answer.
Splitters resolve this in different ways, and none of them are magic:
- Some pass through the EDID of output one and hope the other seven agree.
- Some compute a lowest-common-denominator EDID, which protects the weakest display and starves the best — this is why one 1080p panel in a group of 4K screens drags the group down.
- Some let you load a fixed internal preset, the most predictable option and the least commonly configured.
Whose EDID the source gets
The symptoms are distinctive. Video with no audio, or audio with no video. One display works while the others show nothing. The source drops to a resolution the display cannot handle, or falls back to 480p. HDR content plays in standard dynamic range. Everything works until a display is powered off, at which point the source renegotiates and picks wrong.
Audio is the most common casualty. A display advertises Dolby Atmos, the source obliges, and the soundbar or DSP in the middle of the chain cannot decode it. The screen lights up and the room stays silent. Forcing a stereo PCM EDID solves that in about thirty seconds.
The fix is EDID management, which any serious distribution product offers. Three strategies are usable: copy the EDID from a specific downstream display, load a built-in preset describing a known-good format, or upload a custom EDID captured from a working reference. The principle is the same each time: stop letting a mixed-display system negotiate dynamically. Decide what the source should output, tell it explicitly, and record the choice.
Why HDCP Takes Down Systems, Not Displays
There is a fast way to tell the two failure families apart: an EDID problem produces wrong-looking video, an HDCP problem produces no video at all.
HDCP is content protection, and the version history is where distributed systems get into trouble. HDCP 1.4 governs pre-4K content and legacy devices, HDCP 2.2 arrived with 4K and premium streaming, and HDCP 2.3 tightened it further. The versions do not gracefully interoperate: an HDCP 2.2 source feeding a 1.4 display needs a converter licensed to downconvert, and if any device in the chain is not licensed, the link simply fails. In the United States, HDCP support is mandated by the Federal Communications Commission.
Two constraints catch professional systems. The first is a repeater limit. HDCP 1.4 allows a maximum of 127 downstream devices across seven levels of repeater depth. Published figures vary slightly: a chip vendor databook describes the same limit as seven levels and as many as 128 total devices, a one-off difference worth confirming against the silicon in your design. What matters on site is the behavior — exceed the limit and the entire tree goes dark rather than degrading at the edges. Stadium, casino, and campus signage systems can genuinely reach it.
The second is a locality check introduced with HDCP 2.2. The transmitter measures round-trip time to the receiver and fails authentication if the response takes too long. Long fiber runs, AV over IP transport, and chains with several repeaters in series can all push past that window, so a system can fail for being too slow over a path that is electrically perfect.
HDCP failures announce themselves clearly. A consistent black screen or a flashing image, but only on protected content. Test patterns display normally while streaming apps do not. The system works with a display connected directly and fails through the matrix, or fails only after a device in the middle is power cycled.
One thing is worth stating plainly: if the content is protected, there is no legitimate way around HDCP. The goal is always to make authentication succeed — by matching versions across the chain, keeping repeater counts inside the limit, and specifying distribution hardware that handles version conversion under license.
Where the Bandwidth Goes
A splitter does not divide bandwidth. Each output carries the same signal, so every output is its own link — eight outputs means eight chances for one to be marginal.
That changes how a cable failure looks over time. A passive cable that carried 4K60 for three years can fail the day a source negotiates 4K120 or 8K, because the demand moved and the cable did not. The signature is intermittent dropouts, sparkles, or green and pink flashes rather than a clean failure. Marginal bandwidth produces marginal symptoms.
Extender generation matters too: an extender rated for 10.2 or 18 Gbps will not pass a Fixed Rate Link signal, however good the cable behind it is.
HDBaseT, AV over IP, and Wireless
Once the run leaves the rack, three transport families cover almost every project.
HDBaseT is the workhorse for long copper runs: its 5Play feature set carries video, audio, Ethernet, control signals, and power over one connection on category cable, uncompressed, to about 100 meters. It does not carry USB, which rules it out where a camera or touch panel travels with the video.
AV over IP packetizes the signal onto the network, scaling past the point where a matrix switch runs out of ports and reusing cabling you may already have. The trade is that the network joins the failure chain, latency included — relevant because of the HDCP locality check.
Wireless HDMI uses the WiFi protocols and is generally slower than a hardwired link. It earns its place where cable genuinely cannot go, not as a substitute for a run that could have been pulled.
A Diagnostic Order That Converges
When a system is down, resist the urge to swap parts. Work the chain in this order.
- Connect the source directly to the display. If it works, the problem is in the distribution path. If it does not, you have a source, display, or content protection issue before distribution is involved.
- Read the symptom. No image at all on protected content points to HDCP. Wrong resolution, missing audio, or bad color points to EDID. Sparkles, dropouts, and intermittent loss point to bandwidth or cable.
- Add one device at a time back into the path, testing after each. The device that breaks it is the one to investigate.
- Check firmware across the chain. Mismatched firmware between a matrix and its receivers is a common cause of handshake failure, and it costs nothing to rule out.
- Force the EDID instead of letting it negotiate. Set the source to a known-good fixed format and see whether stability returns.
- Verify the HDCP version at every hop: the display, the audio processor, and every extender in between.
Two pieces of gear shorten this loop: an EDID emulator you can drop inline to force a clean EDID, and a generator and analyzer that reads back what a display actually reports, including a full EDID dump and HDCP status.
FAQ
Can an HDMI splitter extend my desktop across two screens? No. A splitter replicates one signal to multiple displays, so every screen shows the same image — mirroring, not extending. An extended desktop needs separate video outputs from the source, or a dock with multiple display outputs.
Why did my 4K display drop to 1080p when I put it on a splitter? Almost always the EDID. In a mixed group the splitter either passes through one display’s EDID or computes a lowest-common-denominator version the weakest panel can handle, so a 1080p screen drags the group down until you set the EDID the splitter presents.
How many devices can sit behind HDCP repeaters? HDCP 1.4 permits seven levels of repeater depth and around 127 downstream devices. Exceeding it takes the entire tree down rather than dropping the far edge.
The Distribution Path Is Where the Signal Is Least Protected
The distribution path is where one source meets displays that disagree, where a legacy panel sits in a 4K group, and where a repeater count nobody tracked decides whether the wall works.
We build the cable side of that path: certified HDMI assemblies in the lengths the run needs, and optical assemblies where copper is no longer realistic. Send us the source, the displays, the endpoint count and the distances.
Sources
- AVProSupply, "How to Fix HDMI Handshake, EDID, and HDCP Problems in Professional AV Systems" (September 2026) (the negotiation sequence from hot plug detect through EDID over the Display Data Channel, HDCP authentication and link training; EDID base block size and CTA-861 and DisplayID extensions; the three ways splitters resolve EDID in a mixed group including lowest-common-denominator behavior; EDID symptom list and audio as the most common casualty; the three EDID management strategies; HDCP 1.4 at 127 downstream devices across seven levels of repeater depth and the whole-tree failure mode; the HDCP 2.2 locality check against round-trip time; HDCP failure signatures; the six-step diagnostic order; extender generation and Fixed Rate Link) — https://avprosupply.com/news/how-to-fix-hdmi-handshake-edid-and-hdcp-problems-in-professional-av-systems/
- Eaton, HDMI Explained (splitter, switch, matrix switch and multiviewer definitions; splitter port naming; the statement that a splitter mirrors rather than extends a desktop; EDID and Display Data Channel definitions; HDCP handshake definition and the FCC mandate; CEC control of up to 15 devices; wireless HDMI using WiFi protocols and being generally slower; HDMI cable length commentary) — https://www.eaton.com/us/en-us/products/backup-power-ups-surge-it-power-distribution/backup-power-ups-it-power-distribution-resources/cpdi-vertical-marketing/hdmi-explained.html
- Synopsys DesignWare HDMI TX databook, as published (HDCP permitting up to seven levels of repeaters and as many as 128 total HDCP devices, including repeaters) — https://www.scribd.com/document/620545722/DWC-hdmi-tx-databook
- Wikipedia, HDBaseT (the 5Play feature set of HDBaseT 1.0 carrying video, audio, Ethernet, control signals and power over a single connection, and that HDBaseT 1.0 does not support USB) — https://en.wikipedia.org/wiki/HDBaseT
- HDBaseT Alliance, HDBaseT Technology (uncompressed ultra-high-definition audio and video distribution over distance) — https://hdbaset.org/hdbaset-technology/
