Ask three people what "controls the LED perimeter boards" and you will get three answers: the panels, the processor, the software. All three are involved, but they do very different things. The quickest way to understand a perimeter LED system is to see it as two layers — a hardware layer that lights up pixels, and a software layer that decides what those pixels should show. Confuse the two and you either overspend or end up with a wall you cannot actually operate on match day.
The two layers of a perimeter LED system
A perimeter installation is built from physical parts and a control chain. The panels are the modular LED tiles that form the ribbon around the pitch. Driving them is a processor (also called a controller, sending unit or video controller). Together, panels and processor are the hardware layer — the muscle.
Sitting above that is the content software — the brain. The software is where an operator decides which sponsor plays, in what order, and exactly when. It is worth knowing that the apps bundled by panel and processor vendors — the tools that ship with systems from manufacturers such as Colosseo, Chyron and others — are firmly on the hardware side. They focus on calibration, pixel mapping and signal handling, and they are usually tied to one brand's equipment. Excellent at what they do, but that is not the same job as running an event.
What a hardware controller / LED processor actually does
The LED processor is a dedicated piece of hardware with one core responsibility: take an incoming video signal and turn it into correctly lit pixels across many panels. Concretely, it:
- Receives a video signal from a source — typically the video output of a PC over HDMI or SDI.
- Maps pixels across panels, so a single image is split and distributed to the right tile in the right position, even when the ribbon wraps or bends.
- Handles brightness and calibration at the electrical level, matching colour and luminance across modules that may have been made in different batches.
- Stays fixed in the install. Once configured, a processor is set-and-forget; you are not reconfiguring it every match.
What the processor does not do is decide the content. Give it nothing and the wall is dark; give it a signal and it faithfully displays whatever that signal contains. Deciding the "whatever" is the software's job.
What perimeter software adds
Perimeter software is the operational layer that produces the signal the processor displays. It is built around the event, not the electronics:
- Media library and normalization. Import sponsor clips and stills, and normalize each one to the exact pixel dimensions of your perimeter — one long strip, or a strip that wraps to a second line.
- Playlists and timed rotations. Arrange the media into a running order, set the dwell time for each item, and loop the sequence for the length of a match.
- Named scenes, triggered live. Save layouts — a goal celebration, a substitution board, a half-time sponsor — and fire them instantly during play.
- Ticker and live messages. Push a scrolling message across the boards without stopping the show.
- Brightness of the sent image. Adjust the luminance of the content itself, on top of whatever the processor calibrated at the panel level.
- Proof-of-play reporting. Log exactly what was shown and when, so a sponsor can be given evidence of their contracted exposures.
Crucially, all of this is hardware-independent. A well-built player outputs a standard full-screen video signal, captured over HDMI or SDI. It does not need to know the brand of your panels — only the pixel size of the surface it is drawing.
Software vs. hardware controllers at a glance
The clearest way to see the split is side by side. Notice how few rows actually overlap: these tools mostly solve different problems.
| Concern | Hardware controller / vendor app | Perimeter software player |
|---|---|---|
| Primary job | Drive, map and calibrate the panels | Build and run the content show |
| Tied to hardware | Usually one brand / model | Hardware-independent (any processor) |
| Live match control | Limited | Scenes, ticker, brightness, instant swaps |
| Sponsor reporting | Rare | Proof-of-play logs per exposure |
| Content updates | Install-time / technical | Drag-and-drop, any time before or during an event |
| Vendor lock-in | High — swap hardware, swap tools | Low — content workflow survives a hardware change |
Do they compete, or work together?
They do not really compete, because they sit at different layers of the same system. The vendor tool configures the wall; the software runs the event on that wall. The signal flows in one direction:
Software player → PC video output → LED processor → perimeter panels
In practice, most venues run both. The manufacturer's tool is used once — at install time — to calibrate the panels, map the pixels and set the electrical baseline. After that, it is rarely touched. The perimeter software is what an operator opens every single event to build playlists, trigger scenes and produce the reports a sponsor contract requires. One is a setup tool; the other is a match-day tool.
Which do you need?
It depends entirely on where you are starting from.
You already have panels and a processor
Then the hardware layer is done. You are almost certainly missing the software layer — the part that turns a configured wall into a controllable, sellable advertising surface. Adding a hardware-independent perimeter player gives you playlists, live control and reporting without touching the existing install, and without committing you to your current panel brand forever.
You are building from scratch (greenfield)
Then budget for both. You will need panels and a processor to physically drive them, and you will need perimeter software to operate them. Choosing a hardware-independent software player up front is the safer call: it means a future panel or processor upgrade will not force you to relearn your entire content workflow.