"Controller" and "processor" show up on the same datasheet for the same product, with different feature claims. That ambiguity is fine when you're browsing — and lethal when you're writing a tender.
This piece sets out the definitions we use at VVT and shows where each architecture (FPGA, PC-based, hybrid presentation switcher) actually fits.
The right question isn't “controller or processor?” — it's “how many sources, how often, how live?”
01
Working definitions
- Video wall controller: the device that takes one or more inputs and lays them out across many displays as a single canvas. May or may not scale individual sources.
- Video wall processor: a controller with heavy real-time scaling, windowing, layering, recording and integration capability — usually PC-based with GPUs.
- Matrix switcher with video wall mode: a hybrid like SEADA G44-HDMI — a 4-in / 4-out 4K switcher that can also drive a 2×2 wall.
02
The three architectures behind every product
- FPGA / crossbar — Drita DT4000 FPGA, SEADA SolarWall Micro. Virus-free, deterministic, 24/7-stable. Layout flexibility is constrained by firmware.
- PC-based — Jupiter Catalyst V, Drita DT4000 Windows. Rich Canvas / WMS software, IP stream decoding, recording, full control-room workflows.
- Hybrid presentation switchers — SEADA G44-HDMI. Small rooms, 2×2 walls, seamless switching with HDCP and EDID handling out of the box.
03
When you need a controller (not a processor)
- 2×2 or 3×3 walls in retail flagships, lobbies, branches.
- Static or scheduled content — menu boards, dashboards, signage loops.
- One or two sources at peak; no IP cameras.
- Budget-tight projects where uptime requirement is "business hours", not 24/7.
04
When you need a processor (not just a controller)
- Control rooms with 16+ inputs — RTSP IP cameras, SCADA, video conferencing, web pages, KVM.
- Dynamic incident-response layouts and scenario presets.
- Recording, audit logs, role-based access.
- 24/7 mission-critical with redundant PSU and RAID.
05
Comparison table
- Typical inputs
- Controller (FPGA): 4–16 HDMI · Processor (PC): up to 64 mixed · Hybrid switcher: 4 HDMI
- IP stream decoding
- Controller: limited · Processor: 120+ (Catalyst V) · Hybrid: none
- Layout flexibility
- Controller: pre-set · Processor: free-form scenarios · Hybrid: pre-set
- 24/7 mission-critical
- Controller: yes · Processor: yes (with RAID/PSU) · Hybrid: business hours only
- Software
- Controller: embedded web UI · Processor: Canvas / WMS · Hybrid: web UI / OSD
- Typical use
- Controller: retail, branches · Processor: control rooms · Hybrid: boardrooms
- Example
- Controller: SEADA SWMicro / DT4000 FPGA · Processor: Jupiter Catalyst V / DT4000 Windows · Hybrid: SEADA G44-HDMI
06
The questions to ask before you pick
- How many concurrent sources at peak?
- Are any of them RTSP / IP camera streams?
- Do you need recording or audit logs?
- 24/7 or 8×5?
- Do operators need to draw new layouts on the fly, or are presets enough?
How VVT helps
VVT carries Jupiter, Drita and SEADA — covering all three architectures — and recommends based on your workflow, not whatever box has the best margin this quarter. Send us your input list and uptime profile; we'll come back with a controller or processor recommendation in 24 hours.
Frequently asked questions
Yes — Drita DT4000 ships in two flavours (FPGA and Windows) inside the same chassis. Most premium PC-based processors (Catalyst V) cover the controller job too. Pure-FPGA boxes can't do everything a PC-based processor can.