How to Configure LED Signal Processing for High Refresh Rates

Why Signal Processing Matters at High Refresh Rates

LED displays at 200 Hz and above expose every mismatch between the source signal, the controller, and the panel. A 1080p source feeding a 120 Hz panel through a misconfigured controller will show flicker, banding, or color shifts even when the hardware itself is sound. The fix is almost always in the signal processing layer, not a hardware replacement.

Engineers who have built large-format installations know the difference between a clean 200 Hz output and a flickering one. The difference is in how the controller handles scan timing, color space, and frame interpolation. This guide walks through that process.

Prerequisites Before You Touch Settings

Before adjusting any LED controller parameters, confirm the following.

• The LED panels, cabinets, and controllers are powered and recognized in the controller software.
• You have a stable video source with a known refresh rate. A test generator or a media player set to a fixed output is ideal.
• You know the panel’s native scan mode. This is printed on the cabinet nameplate or listed in the panel datasheet.
• You have access to the controller’s firmware settings menu and can make changes without losing configuration.
• A colorimeter or at minimum a calibrated display is available for the final verification step.

If any of these are missing, fix them first. Configuring signal processing on an unstable installation creates confusion, not clarity.

Step 1: Set the Source Refresh Rate to Match the Target

In the controller software, set the input refresh rate to match the panel’s target. If the panel is rated for 120 Hz, set the controller input to 120 Hz. Do not leave this on auto-detect if you can avoid it. Auto-detect can lock onto 60 Hz, 59.94, or 75 Hz depending on the source, and that mismatch is the most common cause of flicker at high refresh rates.

The reason is simple. The controller builds its scan table based on the input rate. If the input says 60 Hz but the panel expects 120 Hz, the controller will try to stretch or drop frames, and the result is visible flicker, especially in dark scenes.

Step 2: Select the Correct Scan Mode

Scan mode determines how the controller drives the rows of LEDs. Common options include progressive scan, interlaced scan, and various row-interleave patterns. For high refresh rate work, progressive scan is almost always the correct choice unless the panel datasheet specifies otherwise.

Check the panel documentation. Some large-format panels use a specific row-interleave pattern to manage power draw and brightness. Using the wrong scan mode at high refresh rates causes row banding and uneven brightness across the panel.

Step 3: Match the Output Refresh Rate to the Panel

The output refresh rate in the controller must equal the panel’s rated refresh rate. This is separate from the input rate. The controller receives a signal, processes it, and sends a new signal to the panels. The output rate is what the panels actually see.

If the input is 120 Hz but the output is set to 60 Hz, the controller will drop frames. The display will look fine in a quick glance but will flicker under sustained viewing. Set the output to match the panel rating exactly.

Step 4: Configure Color Space and Gamma

LED controllers accept input color space settings such as RGB, YCbCr 4:2:2, or YCbCr 4:4:4. Set the input color space to match the source. If the source is a broadcast feed, it is likely YCbCr 4:2:2 or 4:4:4. If it is a computer-generated signal, it is almost always RGB.

Gamma correction is the next sub-step. Set the gamma curve to match the content type. For cinematic content, a gamma of 2.4 or 2.6 is typical. For graphics and data visualization, a gamma of 2.2 is more common. The controller’s gamma setting affects how midtones render, and a mismatch here creates a washed-out or muddy picture that can be mistaken for a hardware fault.

Step 5: Enable Frame Interpolation Only If Needed

Some controllers offer frame interpolation or motion compensation. This feature creates intermediate frames between input frames to smooth motion. At high refresh rates, this can help, but it can also introduce artifacts like ghosting, edge ringing, or soft edges on fast-moving content.

Start with frame interpolation disabled. Watch the display for a few minutes with mixed content. If you see noticeable judder in 60 Hz source material playing on a 120 Hz panel, enable interpolation and test again. If the image looks worse, turn it off. The reason is that interpolation algorithms are content-dependent, and a setting that improves one type of video can degrade another.

Step 6: Adjust Scan Timing and Delay

High refresh rate panels are sensitive to timing offsets. The controller’s scan timing controls the phase relationship between the video signal and the LED refresh cycle. A small offset, even a few milliseconds, can cause flicker in dark scenes or during fast color changes.

In the controller’s advanced settings, find the scan timing or phase adjustment. Set it to the default first, then make small adjustments while watching a test pattern. A solid black field with a 10% white dot moving horizontally is a good test. If you see a shimmer or a band moving with the dot, adjust the timing in small increments until the shimmer disappears.

Step 7: Verify with a Full-Panel Test Signal

After all settings are applied, run a full-panel test signal. This should include a solid black field, a solid white field, a 50% gray field, a color bar, and a moving pattern. Watch each zone of the display for at least two minutes.

The reason for the full-panel test is that controller settings can behave differently across zones if the display uses multiple controller boards or if there is a mismatch in zone configuration. A flicker in one zone that is absent in others points to a zone-level setting error, not a global one.

Common Mistakes That Cause Flicker at High Refresh Rates

The following mistakes appear in installations regularly.

Mistake	Symptom	Fix
Input rate set to auto-detect	Flicker in dark scenes, 60 Hz ghosting on 120 Hz panels	Set input to exact panel refresh rate
Output rate below panel rating	Visible flicker, dropped frames	Match output rate to panel rating
Wrong scan mode	Row banding, uneven brightness	Check panel datasheet and select correct mode
Interpolation enabled by default	Ghosting, soft edges on fast motion	Disable interpolation and test before re-enabling
Gamma mismatch	Washed-out or muddy midtones	Set gamma to match content type

These mistakes are not hardware failures. They are configuration errors that are easy to reverse but easy to overlook when the display looks “close enough” on a laptop preview.

Final Verification Step

The final step is the one that separates a passing installation from a reliable one. Sit in the normal viewing position, not at a close inspection distance. Watch a sustained scene for at least five minutes. Use content that includes dark areas, midtones, and fast motion.

Check for flicker at 60% of the normal viewing distance. If you see flicker at a distance where viewers will actually be, the display is not ready. Recheck the input rate, output rate, scan mode, and scan timing in that order. Most flicker issues at high refresh rates trace back to one of these four settings.

Do not rely on a single test. Run the verification at different times of day. Ambient light changes can mask or reveal flicker that was not visible under controlled conditions. A display that passes at noon may fail in low-light evening viewing.

When to Escalate to Hardware

If all controller settings are correct and the display still flickers, the issue is likely hardware. Check the controller board for signs of overheating, a failing fan, or a loose connection to the panel. Check the panel’s power supply for brownout conditions. Check the video cabling for damage or poor contact.

A flicker that appears only when the panel is at full brightness, or only after the display has been running for several hours, points to a power supply or thermal issue rather than a signal processing problem. In those cases, the controller settings are not the root cause, and escalating to hardware diagnostics is the correct next step.