Neo Matrix - Project Sizing and Scalability

Modified on Tue, 9 Jun at 8:29 PM

This article covers the maximum limits for Neo Matrix projects, how to scale beyond a single matrix, and and when to move to OneIP instead.


Single Matrix Limits

ModelMax HDBaseT ZonesMax HDMI InputsAdditional Audio InputsAudio Output Zones
neo:444
neo:6a666 (Source Mode only)
neo:8a888 (Source Mode only) 
neo:XSR466 (Source and Sink Mode)
neo:X+88410 (Source and Sink Mode) 

All Neo Matrix models also include 2 additional HDMI outputs (local mirror). The neo:X+ HDMI outputs can be set to audio-only mode for AVR connection.


When You Need More Than One Matrix

Neo Matrix is a single-unit solution. If you need more zones than one matrix provides, the right answer is almost always OneIP — not a second Neo Matrix.

Stacking multiple Neo Matrix units looks attractive on paper but has a significant practical problem: to share sources between matrices you have to loop HDMI signals from one unit's local outputs into the next unit's inputs. This wastes HDBaseT output ports on the first matrix just to feed the second, and the additional hardware cost - a second matrix plus the wasted ports - quickly exceeds what a OneIP system would have cost from the outset. You also end up with multiple separate web interfaces, separate Cloud Monitoring entries, and more complex control system driver configuration.

Stacking Neo Matrix units is not a recommended scaling strategy. If your zone count exceeds what a single matrix provides, specify OneIP. It is purpose-built for unlimited scalability, costs less than multiple stacked matrices at larger zone counts, and is significantly simpler to commission and manage.

Scaling Beyond a Single Matrix

When a single matrix does not provide enough inputs, outputs, or audio zones, the solution is to add additional matrix units to the same installation. In practice, a second Neo Matrix on the same installation rapidly creates control system complexity and cost that exceeds what a OneIP system would have cost from the start.

Audio with a Neo Matrix

The neo:6a, neo:8a, neo:XSR, and neo:X+ all include per-source audio extraction outputs (optical and coax). These feed directly into a ProAudio matrix, which handles independent audio routing and volume control across all zones. Set the Neo Matrix to Source Mode so audio output zones are locked to HDMI inputs rather than following video routing.

Control System Integration

Each Neo Matrix is a separate device from the control system's perspective and requires its own driver instance and static IP address. For zone counts beyond a single matrix, specify OneIP from the outset rather than adding a second Neo Matrix.


Zone Count: Neo Matrix vs OneIP

Zones RequiredRecommended Approach
Up to 4neo:4 or neo:XSR (if 4K@60Hz 4:4:4 / ARC required)
Up to 6neo:6a
Up to 8neo:8a or neo:X+ (if built-in audio matrix required)
9 or moreOneIP — scales up to 32 devices without the source-sharing penalties of stacked HDBaseT matrices
The neo:X+ and neo:8a both have 2 local HDMI mirror outputs. These are useful for a rack monitor or a local display — they are not a scalable way to feed a second matrix.


Need help sizing a project? Our pre-sales team can review your zone count and source list.
UK: 01202 413 610 | US: (858) 748-8250 | sales@pulse-eight.com

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article