Matrox alternative — Craft Wall vs Matrox Mura

Matrox is the original software-controlled hardware-card video wall vendor. Their model — drop capture/output cards into a Windows server, drive it with MuraControl — is decades old and still the right answer in certain niches. This page lays out where Craft Wall, with no proprietary cards, wins, and where Matrox still has the edge.

What Matrox sells

The Mura family covers IPX (4K capture / encode / decode PCIe cards), MPX (control-room oriented), and Mura DVW (display wall controller). On top sits MuraControl and the higher-end ControlDesk software, plus QuadHead2Go for small-format multi-output. Distribution runs through B&H, CDW, AVendor and similar resellers. Marketing tagline is "low-cost, premium performance".

Verified pricing signals

• Mura DVW software bundle: ≈ €2,700 via B&H listings.
• QuadHead2Go small-format hardware floor: ≈ €1,150 per unit.
• Capture / output cards (Mura IPX class): roughly $1,500-2,500 per card, with cost scaling linearly per source and per output. No public per-display rate card beyond that.

Where Craft Wall is different

• Software-only. Craft Wall runs on a single standard Linux server with an NVIDIA GPU. Matrox needs at least one Mura card per source group plus a Windows host to drive them.
• Per-server perpetual licence. €2,500 paid once for an unlimited number of canvases on one server, compared with Matrox's per-card economics where adding sources or outputs means buying more silicon.
• Browser-based control. Operators reach Craft Wall from a browser on a laptop or tablet. MuraControl and ControlDesk are Windows desktop applications.
• Source mix. Craft Wall takes NDI, RTSP/SRT, RDP/VNC and web-page sources natively from the IP fabric. Matrox-IPX paths assume you'll feed sources into capture cards first.

Where Matrox is the better fit

• Workflows that require deterministic sub-frame latency from a baseband SDI or HDMI source straight onto the wall — Matrox cards solve this with no compromise.
• Sites that already standardise on Mura cards in adjacent rooms and want a consistent stack across multiple control rooms.
• Highly regulated facilities that specifically require Matrox-class hardware in tender language (rare outside broadcast).

Common operator complaint

A recurring Reddit thread (r/CommercialAV, r/AV) points out that Matrox multi-output cards "perform very poorly for real-time rendering" compared with a stock NVIDIA card in a generic wall controller — the cards are excellent for capture but were not designed as a GPU. Software platforms on modern NVIDIA hardware close the gap and often beat it for layered composition.

Migration considerations

Moving from Mura to Craft Wall usually means: extract sources off the capture cards (most become NDI or RTSP on the network), retire the Windows MuraControl host, and run Craft Wall on a new Linux server with NVIDIA GPUs sized for the displays. The Mura cards often find a second life as ingest appliances elsewhere in the estate.

Other comparisons

• Datapath Fx4 alternative: WallControl 10
• Barco TransForm N and CTRL alternative
• Userful alternative: Linux and zero-client