When you price out a perimeter LED setup, the panels are the obvious cost. The next line item people wonder about is the LED processor — and whether it is a mandatory purchase or something you can skip. The honest answer is: sometimes you need one, and sometimes a PC with the right output does the same job. To decide, it helps to understand exactly what the processor does and what it does not.
What an LED processor actually does
An LED processor — also called a sending unit or video controller — sits between your video source and the panels. Its job is to take an incoming picture and turn it into the exact signal each panel needs. In practice it handles several things at the hardware level:
- Pixel mapping. It maps the flat video image onto the physical pixel layout of the panels, so a 40-metre ribbon shows the content in the right place across every module.
- Scaling. It resizes a standard input (say 1920×1080) to the non-standard total resolution of a long, thin perimeter surface.
- Refresh and grayscale. It drives a high refresh rate so cameras see no scan lines or flicker on broadcast.
- Brightness and calibration. It balances colour and brightness across panels at the hardware level so the whole surface looks uniform.
The player software never touches those electrical details. It just draws a picture. The chain looks like this:
Software player → PC video output → LED processor → perimeter panels
Processor vs. receiving cards vs. the PC
The terminology trips people up, so here is the chain in plain words. The PC and its player produce the content as a normal video image. The processor (sending unit) takes that image and converts it into the panel data stream. Inside each panel sits a receiving card that listens to the processor and lights the actual LEDs on that module. Every panel has a receiving card; you have one processor (or a simple sender) for the whole run; and one PC drives the show.
The key distinction: receiving cards are not optional — they are built into the panels. A dedicated processor is the choice you are actually making, and its alternative is a much simpler sender box (or in some cases the panel's own on-board input) fed directly by the computer.
When you DO need a dedicated processor
A separate, high-end processor earns its place when the installation grows past what a PC output can cleanly cover:
- Large total pixel counts. When the whole perimeter adds up to more pixels than a single PC output (or even a multi-output card) can carry, a processor stitches the wide canvas together.
- Multiple panel runs. Boards split across several sides of a pitch, or wrapping onto a second tier, are easier to feed and synchronize from one processor.
- Precise calibration. Broadcast venues need seam-free brightness and colour matching across hundreds of panels — a hardware processor does this far better than a raw video output.
- Permanent stadium installs. A fixed venue that hosts events season after season justifies dedicated, rack-mounted hardware for reliability.
- Non-standard resolutions. Very long, thin surfaces have odd total dimensions that a processor is designed to scale and map, whereas a plain graphics output is not.
When PC-based playback is enough
Plenty of real-world perimeters do not need a dedicated processor at all:
- Smaller or simpler perimeters. A modest ribbon whose total pixels fit within one or two PC video outputs can be driven straight from the computer.
- Panels with a standard-signal receiver. Many modern panels accept a normal HDMI or SDI feed through a small sender; the PC plugs in and the panels display it.
- Temporary or budget setups. Pop-up events, lower-league grounds and demo rigs rarely justify the cost of a full processor.
In these cases the software simply outputs a normal, full-screen image, and whatever is downstream — a simple sender or the panel's own receiver — captures that image exactly as it would any video input.
How the software layer stays independent of the processor choice
This is the part that makes the decision low-risk: the player software does not care which route you take. In the software you define the module and panel pixel dimensions of your surface — that is what the player draws to. It then outputs a standard video signal on the PC. Whether that signal goes into a high-end processor, a simple sender, or the panel's own receiver, the software behaves identically.
Because the output is hardware-independent, you are free to start with a PC-only setup and add a dedicated processor later without changing how you build playlists, run scenes or operate on match day. The processor decision is a hardware and budget question — not a software lock-in.
| Aspect | Dedicated processor | PC-based playback |
|---|---|---|
| Best for | Large / permanent stadium installs | Smaller, simple or temporary perimeters |
| Pixel capacity | High — stitches wide, multi-run canvases | Limited to the PC's video outputs |
| Calibration | Broadcast-grade, seam-free across panels | Basic — relies on panel / sender defaults |
| Cost | Higher up-front hardware cost | Low — a capable PC and a simple sender |
| Flexibility | Fixed, rack-mounted reliability | Portable, quick to redeploy |
A short buyer's checklist
Before you commit either way, run down these five questions:
- Total pixel resolution. Add up every panel — does the whole surface fit inside your PC's outputs?
- Number of panel runs. One straight ribbon, or several sides and tiers to synchronize?
- Calibration needs. Is this broadcast, where uniform brightness across panels matters, or in-house only?
- Permanent vs. temporary. A fixed seasonal venue or a pop-up event rig?
- Budget. Where does a dedicated processor sit against the rest of the project cost?
FAQ
Can I run LED panels without a dedicated processor?
Often yes. Many perimeter panels ship with a receiving card that accepts a standard HDMI or SDI signal through a simple sender, so a PC running the software can drive them directly. A dedicated processor becomes necessary as pixel counts, panel runs and calibration demands grow beyond what a basic sender can handle.
Does the software need a specific processor brand?
No. A software player that outputs a standard full-screen video signal is hardware-independent. It does not talk to the processor's control protocol; it simply produces an image on the PC's video output, and any processor or sender that captures that signal will display it — regardless of brand.
What resolution can a PC drive?
A single video output typically drives up to about 1920×1080 or 3840×2160, and a multi-output graphics card can span several outputs across a wide perimeter. If your total pixel canvas exceeds what the PC's outputs can cover, a dedicated processor is used to stitch and map the wider surface.
Is a capture card required?
Usually not. The PC connects to the processor or sender by cable, and the processor captures the image as a normal video input. A capture card is only needed in specific workflows where an incoming external feed has to be brought into the PC, not for standard playback out to the panels.