DSID Knowledgebase | HDMI Signal Chain Integrity for BrightSign Passthrough Setups

HDMI Signal Chain Integrity for BrightSign Passthrough Setups

Applies to: All BrightSign Series with HDMI Input

DSID Admin

Last Update 22 days ago

Overview

Some LoopOS deployments include a passthrough feature that allows an external device — such as a Roku Ultra, Apple TV, or cable set-top box — to send its video signal through the BrightSign player and onto the screen. This is commonly used when a practice wants to show live TV, streaming content, or a secondary source as part of their display setup.

When passthrough setups experience issues — particularly a frozen or blank screen that appears when the external device is connected — the cause is almost never a single faulty component. It is nearly always a signal chain problem: one or more links in the path from the source device to the screen are incompatible, misconfigured, or underpowered. Understanding the full chain is the key to diagnosing and fixing the problem.

What Is a Signal Chain?

Think of your video setup like a chain of links. Each link is a device the signal passes through on its way from the source to the screen:

Source Device (Roku etc.) → BrightSign Player → Splitter (if present) → Display(s)
Every link in this chain must be able to handle the signal. If any single link is too slow, incompatible, or non-compliant with content protection requirements, the entire chain can fail — even if every other link is working perfectly.

A Plain-English Explanation of HDCP

HDCP stands for High-bandwidth Digital Content Protection. It is a security system built into HDMI that prevents video from being illegally copied as it travels from one device to another.

Here is a simple way to think about it: imagine every device in your signal chain needs to show a valid ID badge before video will flow through it. The source device (e.g. a Roku) checks whether the BrightSign has a valid badge. The BrightSign checks whether the display has a valid badge. If any device in the chain either has no badge or presents an invalid one, the whole system stops and the screen goes blank or freezes.

This is exactly what HDCP is doing — and it is the reason a passthrough setup can fail even when all the cables are connected and all the devices appear to be on.

There are two versions of HDCP in common use:

HDCP 1.x — used for standard and HD (1080p) content. Supported on all current BrightSign players.
HDCP 2.x — used for 4K content. Supported on select BrightSign models. Not all players or displays support it fully.

Streaming devices like Roku Ultra and Apple TV are HDCP-enabled by default. This means the moment they are connected, they initiate HDCP authentication across the entire chain — including the BrightSign and whatever is connected downstream of it.

Why Passthrough Setups Are More Complex

In a standard LoopOS playback setup, the BrightSign is only dealing with one signal path: its own content out to the display. HDCP is typically not required because the content is not protected at the output level.

When passthrough is involved, the BrightSign becomes an HDCP repeater — it sits in the middle of the chain, authenticating with the source device on one side and with the display on the other side simultaneously. This means:

Every device in the chain must be HDCP-compliant
The chain must be able to sustain that authentication continuously, not just at startup
Any device that breaks the chain — including a splitter — causes the whole thing to fail

This is a significantly more demanding setup than standard playback, and it is why passthrough issues often appear only after everything seems to be working initially.

The Role of Splitters in Signal Chain Failures

HDMI splitters are one of the most common and least obvious failure points in passthrough setups. A splitter takes one HDMI signal and duplicates it to two or more displays — useful when you want the same content on multiple screens.

The problem is that splitters sit inside the HDCP chain. The BrightSign must authenticate not just with the final display, but with the splitter itself, which then authenticates with each connected display. This makes the HDCP handshake significantly more complex.

Passive vs. Active Splitters

Not all splitters are created equal:

Passive splitters have no internal processing power. They physically split the signal. They generally cannot participate in HDCP authentication correctly, and many will cause the signal chain to fail entirely when protected content is involved.

Active splitters have internal electronics that regenerate and amplify the signal. A quality active splitter with HDCP 2.2 compliance can participate in the authentication chain properly. However, even active splitters vary widely in quality and bandwidth capability.

Bandwidth Is a Critical Factor

Every HDMI signal has a bandwidth requirement based on its resolution and frame rate. A signal chain is only as capable as its lowest-bandwidth component.

Output Mode	Pixel Clock	Minimum Bandwidth Required
1080p @ 60Hz	~148 MHz	~14.4 Gbps (HDMI 1.4+)
1080p @ 30Hz	~74 MHz	~7.2 Gbps (HDMI 1.4)
4K @ 60Hz	~297 MHz	~28.8 Gbps (HDMI 2.0)
4K @ 30Hz	~594 MHz	~18 Gbps (HDMI 2.0 HDR)

A splitter rated for HDMI 1.4 at 74 MHz may handle 1080p@30 cleanly but fail entirely at 1080p@60, because the 148 MHz pixel clock exceeds what it can process. When a splitter is pushed beyond its bandwidth ceiling, it typically cannot sustain the HDCP handshake — causing intermittent freezes and blank screens as is sometimes seen.

Common Symptoms and What They Indicate

Symptom	Likely Cause
Screen freezes or goes blank immediately when source device is connected	HDCP authentication failure — splitter or display not compliant, or bandwidth exceeded
Screen works briefly then freezes after a few seconds	HDCP link integrity check failing after initial authentication — bandwidth or cable issue
Works at 1080p@30 but fails at 1080p@60	Splitter or cable bandwidth ceiling below 148 MHz
Audio continues but video is blank	Classic HDCP video blocking — audio is not subject to HDCP in the same way
Works with one source device but not another	Source device is outputting a resolution or HDCP version the splitter cannot handle

Diagnostic Steps

Work through these in order. Most passthrough issues are resolved or identified within the first three steps.

Step 1 — Identify every device in the signal chain

Before assuming any single device is faulty, map out the full path:

What is the source device? (Roku Ultra, Apple TV, cable box, etc.)
What resolution and frame rate is the source device set to output?
Is there a splitter? If so, what make and model? Is it passive or active? Is it HDMI or HDMI-CAT (HDMI over Ethernet)
What is the display? Is it HDCP 1.x or 2.x compliant?
Are there any other intermediate devices — AV receivers, distribution amplifiers, HDMI extenders over CAT cable?

Every one of these is a link in the chain. Document, or at least understand the chain, before proceeding.

Step 2 — Reduce the BrightSign output resolution

Reducing the BrightSign's output signal is a fast and easy toggle that solves most HDCP issues. Reducing the signal from 4K or 60Hz to 1080p or 30Hz lowers the signal load. For example, going from 1080p@60 to 1080p@30 halves the pixel clock from 148 MHz to 74 MHz. This can bring the setup within the bandwidth capability of a marginal splitter or cable and allow HDCP authentication to succeed.

How to change the resolution in LoopOS:

1. Login to LoopOS
2. Navigate to the Layout tab
3. Select the relevant device/Location from the dropdown menu
4. Select the Resolution tab
5. Change the resolution and/or frame rate to a lower setting
6. Save the setting

Important: This is a per-device setting. Saving it will automatically trigger the BrightSign to reboot and apply the new output mode. The device will be briefly offline during the reboot — typically 30–60 seconds. Note that this change affects all content output on that device, not just the passthrough signal.

Step 3 — Match source device output to BrightSign output

It is recommended that the source device output resolution and frame rate match the BrightSign's output mode. For example, if the BrightSign is set to 1080p@30, configure the Roku or Apple TV to also output 1080p@30. Mismatched resolutions — such as a source outputting 720p into a BrightSign set to 1080p@60 — can cause the video compositor to fail to establish a pipeline in time for the HDCP handshake, resulting in authentication failure.

Step 4 — Bypass the splitter temporarily

If a splitter is present, connect the BrightSign directly to a single display and test. If passthrough works correctly without the splitter, the splitter is either non-HDCP-compliant, bandwidth-limited, or passive. It will likely need to be replaced with an active, HDCP 2.2 compliant unit rated for the bandwidth your setup requires.

Step 5 — Check the HDMI cables

A cable that works for standard playback may not reliably sustain HDCP authentication for passthrough — particularly if the cable is long, cheap, or older. Try a shorter, known-good HDMI cable directly between the BrightSign output and the display, bypassing the splitter entirely. If the problem disappears, the cable or the splitter is the issue.

Step 6 — Consider replacing non-compliant hardware

If steps 1–5 confirm the splitter is the problem, it may need to be replaced. The recommended specifications for a replacement splitter in a passthrough setup is:

Active (powered) electronics
HDCP 2.2 compliant
HDMI 2.0 rated (18 Gbps) for 4K setups
HDMI 1.4 rated (10.2 Gbps minimum) for 1080p-only setups

Passive splitters and unbranded "plug splitters" should never be used in any setup that involves HDCP content — which includes any setup using Roku, Apple TV, cable boxes, or streaming devices.