A complete guide to the LED display signal chain, and how to tell the two devices apart

Two very different boxes sit between your video source and your LED wall, and they are constantly confused with one another. One prepares the image. The other delivers it to every single LED. Get the division of labour right and your display looks stable, sharp and camera-friendly. Get it wrong and you either pay for hardware you do not need, or spend months chasing flicker, banding, black screens and colour drift.

What Do an LED Processor and an LED Controller Do?

Two very different boxes sit between your video source and your LED wall, and they are constantly confused with one another. One prepares the image. The other delivers it to every single LED. Get the division of labour right and your display looks stable, sharp and camera-friendly. Get it wrong and you either pay for hardware you do not need, or spend months chasing flicker, banding, black screens and colour drift.

Key takeaways

• LED processor = video processing.Scaling, input switching, colour management, layers, HDR, latency control and EDID/HDCP handling.
• LED controller = pixel distribution and drive.A sending card splits the image into port streams; receiving cards inside each cabinet decode, calibrate and drive the LEDs.
• They answer different questions.The processor decides what the image looks like; the controller decides where each pixel lands and how it is refreshed.
• One Gigabit output port typically carries about 650,000 pixelsat 8-bit colour and 60 Hz, so port count and pixel mapping drive the whole system design.
• Refresh rate, grayscale depth and scan mode are controller-side specsand they decide whether the wall looks clean on camera or flickers and bands.
• A well-tuned processor and controller pair adds roughly 1-2 frames of latency(16-33 ms) from source to light.

LED processor vs LED controller at a glance

If you only remember one table from this guide, make it this one. It summarises the difference between an LED processor and an LED controller in the terms that actually matter when you specify a system.

What is an LED processor?

An LED processor, also sold as a video processor, video wall processor, image processor or simply a scaler, is the device that receives video from sources such as media players, cameras, computers, switchers and IP streams, and converts it into a signal that an LED display can reproduce accurately.

That conversion is essential because an LED wall is not a monitor. It has a fixed virtual resolution, an unusual aspect ratio, no built-in scaling and no concept of a standard video mode. Nothing inside the cabinet can enlarge a 1080p feed to a 10-metre-wide screen, crop it, or switch between a laptop and a camera without a glitch. The processor does all of that before the pixels are ever distributed.

The seven core jobs of an LED processor

1.  Input switching and routing.Connect several sources at once and send any of them to the wall, on request, without re-cabling.
2.  Scaling and de-interlacing.Resize and clean up mismatched formats so that 1080i broadcast feeds, 4K graphics and phone clips all fill the screen correctly.
3.  Frame rate conversion and genlock.Match the display refresh to the source, and lock multiple screens or cameras to a shared reference.
4.  Colour management.Apply gamma curves, 3D LUTs, white point and gamut mapping so Rec.709, DCI-P3 or HDR content looks correct on the panel.
5.  Multi-window layout.Place picture-in-picture, side-by-side, layers and overlays so one screen can show several sources at once.
6.  EDID and HDCP handshakes.Present a valid, editable EDID to every source and manage HDCP 2.2 / 2.3 so protected content plays without a black screen.
7.  Latency control.Choose between processing quality and speed, or bypass processing entirely for critical live work.

Specs that separate a professional processor from a cheap scaler

• Signal support:HDMI 2.0 / 2.1, 12G-SDI and quad-SDI, DisplayPort 1.4, and increasingly SMPTE ST 2110 IP video.
• Pipeline quality:4K60 at 4:4:4 with 10-bit or 12-bit internal processing, so gradients stay smooth and on-screen text stays crisp.
• Latency:sub-frame to one frame for the processor stage alone, with a documented low-latency or bypass mode.
• Reliability:redundant power supplies, hot-swappable input cards, and a control interface (web UI, protocol or API) that your control system can talk to.

Figure 1. Inside an LED video processor: inputs are normalised, corrected and laid out, then output in the format the LED controller expects.

What is an LED controller?

An LED controller is the system that takes the prepared video signal and drives the physical LEDs. In a synchronous LED display it is made up of the sending card (the controller box that sits near the processor or video source), the receiving cards inside every cabinet, the hub cards that fan signals out to the LED driver ICs, and the software that maps, calibrates and monitors the screen.

The word controller is used loosely in the industry, and that causes most of the confusion. Sometimes it means the sending card box, sometimes the complete drive chain including receiving cards, and sometimes a standalone media player that also drives the screen. When you are comparing products, always ask which of those three a vendor means.

The sending card: traffic controller for your LED wall

The sending card captures the processed video, divides it into the pixel blocks that each output port will carry, and transmits them over Gigabit Ethernet. It also owns the practical settings that operators touch every day: brightness, colour temperature, gamma, test patterns, presets, scheduling, and the pixel map that tells the system which cabinet is where.

• Splits a large canvas into port streams, typically around 650,000 pixels per Gigabit port at 8-bit and 60 Hz.
• Stores the pixel map, so cabinets can be re-ordered or replaced without rebuilding the whole layout.
• Handles global brightness, low-brightness performance, colour temperature and per-screen presets.
• Provides redundancy options: dual senders, loop-through cabling and automatic failover cabling.
• Reports cabinet status back to the operator through the return path.

The receiving card: the pixel engine inside every cabinet

Every cabinet contains at least one receiving card. It decodes the incoming stream for its own area of the image, applies the calibration coefficients that were measured for that specific cabinet, and passes the data to the hub card and LED driver ICs. This is where refresh rate, grayscale depth, scan mode and low-latency behaviour are actually implemented.

Hub cards, driver ICs and LED modules

The hub card distributes data channels to the driver ICs on each module. The driver ICs switch current through the RGB LEDs using pulse-width modulation (PWM). Their quality, together with the receiving card settings, decides how smooth the lowest grey levels look, whether there is ghosting on fast motion, and how well the panel holds colour at low brightness.

Five types of LED controller you will meet

• Synchronous sending-card system.The standard for fixed and rental LED walls: a controller box plus receiving cards, fed by a processor.
• All-in-one processor and controller.HDMI or SDI input, scaling and sending ports in a single unit, ideal for simple single-source screens.
• Asynchronous media player controller.Plays stored content from internal storage or the cloud, with no live video input, common in digital signage.
• Wireless or IoT controller.Manages screens remotely over Wi-Fi, LTE or a CMS, often with brightness sensors and fault alerts.

Figure 2. Inside an LED controller system: one sending card feeds many receiving cards over Gigabit Ethernet, each cabinet decoding and driving its own pixels.

The full LED signal chain, step by step

Understanding the order of the chain is the fastest way to diagnose problems, because each stage can only work with what the previous stage gives it.

1.  Content and source.A media player, camera, computer, switcher or streaming decoder produces a video signal.
2.  Transport and switching.The signal travels over HDMI, SDI, DisplayPort or IP, optionally through a switcher or matrix.
3.  Processing.The LED processor scales, de-interlaces, converts the frame rate, corrects colour and arranges layers into the wall’s virtual resolution.
4.  Output to the controller.The processed image is handed to the sending card, in the same box or over HDMI, DVI or a network link.
5.  Pixel mapping and splitting.The sending card divides the canvas into port outputs, typically about 650,000 pixels per Gigabit port.
6.  Network distribution.Data travels over Cat5e or Cat6 cable, or fibre for long runs and electrical isolation.
7.  Receiving and calibration.Each receiving card takes its own region of the image and applies the cabinet’s calibration coefficients.
8.  Driving the LEDs.Hub cards and driver ICs convert the data into PWM current pulses that light the red, green and blue LEDs.

Figure 3. The LED display signal chain: the processing zone defines what the image looks like, the control zone defines where every pixel goes.

Do you need both, or is a controller enough?

Not every project needs a separate processor. The deciding factors are how many sources you have, whether they must switch without a visible glitch, and whether the screen will be filmed.

• One source, simple content.An all-in-one controller with an HDMI or SDI input is usually enough. You save cost and rack space, and there is one fewer device to fail.
• Several sources or live switching.Add a dedicated processor. It brings scaling, layers, picture-in-picture and seamless switching, and it protects the wall from source changes.
• Broadcast, studio or virtual production.You need both, and both must be specified for camera work: genlock, shutter sync, HDR handling on the processor side, and high refresh rate with fine grayscale on the controller side.

Figure 4. Deciding between an all-in-one controller and a dedicated processor, based on source count and whether the wall is filmed.

Why controller specs decide how good your wall looks on camera

Two identical LED walls driven by different controllers can look completely different on television. The variables below are set in the controller and receiving cards, not in the processor.

• Refresh rate.Measured in Hz, it describes how often the whole panel is rewritten. Higher rates reduce flicker and banding when a camera films the screen.
• Grayscale depth.14-bit to 16-bit internal processing keeps dark scenes free of banding and stepping.
• Scan mode and duty cycle.Static or low-scan designs (1/8, 1/16) drive each LED for longer, which helps brightness and camera stability.
• Low-latency mode.Cuts the buffering between input and light output, which matters for IMAG, live performance and XR stages.

Refresh rate is a controller specification, which is why two walls with the same LED panels from different brands can behave completely differently in front of a camera.

Sizing the system: from pixels to ports

Before choosing hardware, calculate how many pixels you are actually driving. A Gigabit output port typically carries about 650,000 pixels at 8-bit colour and 60 Hz. Higher refresh rates, deeper grayscale and higher frame rates all reduce that figure, so always leave 15 to 30 percent headroom.

Figure 5. Screen resolution drives controller port count: 4K needs roughly 13 Gigabit ports before headroom, 8K roughly 52.

Where LED processors and controllers are used

How to choose: a ten-point checklist

1.  Count your sources and decide whether they must switch seamlessly.
2.  Write down the wall’s virtual resolution and total pixel count, then calculate ports with headroom.
3.  Confirm the refresh rate the application needs, especially if cameras are involved.
4.  Check grayscale depth and scan mode for low-brightness and camera performance.
5.  List the signal formats and standards you must support: HDMI 2.1, 12G-SDI, DisplayPort, ST 2110.
6.  Confirm HDCP and EDID flexibility, because protected content and laptops are the usual cause of black screens.
7.  Specify latency requirements for live work and verify a real bypass or low-latency mode exists.
8.  Plan redundancy: dual power supplies, backup senders, loop cabling, spare ports.

Troubleshooting: which box is causing the problem?

What is changing in LED processing and control

• Fine-pitch and COB panels push pixel counts up.A single square metre of P1.2 now holds far more pixels than older panels, so port planning and controller capacity matter more than ever.
• Higher-bandwidth links.HDMI 2.1, 12G-SDI and SMPTE ST 2110 IP video carry 4K and 8K over fewer cables and integrate with broadcast infrastructure.
• Virtual production requirements.Genlock, shutter sync, sub-frame latency and 7680 Hz refresh are now baseline expectations for XR and in-camera VFX stages.
• Remote monitoring and predictive maintenance.Return-path data lets operators see cabinet temperature, voltage and pixel faults before a screen fails in public.
• Smarter processing.AI-assisted scaling, automatic aspect fitting and content-aware brightness control reduce the manual work of running mixed-source screens.

Frequently asked questions

What is the difference between an LED processor and an LED controller?

An LED processor handles the video: scaling, switching, colour management and frame-rate conversion. An LED controller handles the pixels: it splits the image, maps it to cabinets and drives the LEDs. The processor sits closest to your sources, the controller sits closest to the screen.

Do I need a separate processor if my LED controller already has an HDMI input?

Only if you have multiple sources, need seamless switching, layers or picture-in-picture, or must guarantee consistent colour and timing. Many all-in-one controllers accept one or two direct inputs and are perfectly adequate for single-source signage.

How many pixels can one sending card output port handle?

A Gigabit output port typically carries around 650,000 pixels at 8-bit colour and 60 Hz. Higher grayscale depth, higher frame rates and higher refresh rates reduce that number, which is why experienced integrators plan for 15 to 30 percent headroom.

What refresh rate does my LED display need?

Indoor signage that is never filmed can work at 1920 Hz or lower. Anything that will appear on camera should run at 3840 Hz or higher, and broadcast, high-speed and virtual production work benefits from 7680 Hz.

What is a receiving card and why does every cabinet have one?

The receiving card sits inside the cabinet and converts the incoming network data into the signals that drive the LEDs in that panel. It also stores the cabinet’s calibration coefficients (chroma, brightness, and often module-level data), which is why a replacement cabinet needs its receiving card data restored.

Can LED processors handle 8K and 12G-SDI?

Yes. Professional processors support HDMI 2.1 and 12G-SDI or quad-SDI inputs for 4K and 8K sources, sometimes with IP video inputs such as SMPTE ST 2110. Check that the processing pipeline, not just the connector, supports the resolution and frame rate you need.

Does an LED processor add noticeable delay to live video?

A well-tuned processor and controller pair typically adds about 1 to 2 frames, or 16 to 33 milliseconds, from source to light. Low-latency or bypass modes reduce this further, which matters for IMAG screens, live performance and virtual production.

Summary

An LED processor and an LED controller solve two different problems, and once you separate them the equipment list becomes obvious. The processor is the video-side brain: it takes sources such as players, cameras and computers, then scales, switches, colour-manages and re-times them into the wall’s virtual resolution. The controller is the pixel-side drive system: a sending card splits that image into port streams of roughly 650,000 pixels each, and receiving cards inside every cabinet decode, calibrate and drive the LEDs.

So the practical rule is simple: the processor defines what the image looks like, and the controller defines where every pixel lands and how it is refreshed. Buy a dedicated processor when you have several sources, need glitch-free switching, or film the screen. Buy a high-refresh, deep-grayscale controller whenever a camera is involved, and always size port count with 15 to 30 percent headroom. Do those three things and your LED wall will stay stable, uniform and camera-friendly for years.