Neo Matrix — Transmitter, Receiver and HDBaseT Range Guide

Modified on Sat, 25 Apr at 1:06 AM

This article covers the HDBaseT transmission distances for all current Pulse-Eight Neo Matrix models and receivers, and which receivers are compatible with which matrices. Always check both the matrix limit and the receiver limit — the lower of the two figures is the effective maximum range for that combination.


Matrix HDBaseT Transmission Ranges

The following distances apply to the HDBaseT outputs on each matrix model. Cat5e or better is required for all runs; Cat6 or Cat6a is recommended for longer runs and 4K.

Matrix Model4K Max Distance1080p Max DistanceHDBaseT ClassIncluded Receivers
neo:440m70mClass B4x neo:Lite
neo:6a40m70mClass B6x neo:Lite
neo:8a40m70mClass B8x neo:Lite
neo:XSR40m100mClass C + DSC4x neo:Ultra
neo:X+100m (standard)
100m+ on request
100mClass C + DSC8x neo:Ultra
The neo:X+ supports 4K up to 100 metres as standard. Extended range beyond 100m is available on request — contact Pulse-Eight sales for details.

Receiver HDBaseT Transmission Ranges

ReceiverHDBaseT Class4K Max Distance1080p Max DistanceDSC SupportARC SupportEthernet Pass-through
neo:LiteClass B40m70mNoNoNo
neo:ProClass C70m (4K@60Hz 4:2:0)100mNoYesNo
neo:UltraClass C + DSC100m (4K@60Hz 4:4:4)100mYesYesYes
neo:Lite3Class C + DSC40m (4K@60Hz 4:4:4, uncompressed)40mYesNoNo
The neo:Lite3 is switchable between transmitter and receiver modes. It supports uncompressed 18Gbps 4K@60Hz 4:4:4 up to 40m and requires Cat6a. It is compatible with all current neo matrices.

Matrix and Receiver Compatibility

All current Pulse-Eight receivers are compatible with all current Pulse-Eight neo matrices via the HDBaseT connection. The effective range for the combination is determined by the lower of the two limits — matrix or receiver — whichever is smaller.

When using a higher-spec receiver than the included receivers on a matrix, the matrix's own HDBaseT output limits still apply as the ceiling. For example, fitting neo:Ultra receivers on a neo:8a will not extend the 4K range beyond 40m, because the neo:8a's Class B outputs cap out there regardless of receiver capability.

Matrixneo:Lite receiverneo:Pro receiverneo:Ultra receiverneo:Lite3
neo:44K: 40m / 1080p: 70m4K: 40m / 1080p: 70m4K: 40m / 1080p: 70m4K: 40m / 1080p: 40m
neo:6a4K: 40m / 1080p: 70m4K: 40m / 1080p: 70m4K: 40m / 1080p: 70m4K: 40m / 1080p: 40m
neo:8a4K: 40m / 1080p: 70m4K: 40m / 1080p: 70m4K: 40m / 1080p: 70m4K: 40m / 1080p: 40m
neo:XSR4K: 40m / 1080p: 70m4K: 40m / 1080p: 100m4K: 40m / 1080p: 100m4K: 40m / 1080p: 40m
neo:X+4K: 40m / 1080p: 70m4K: 70m / 1080p: 100m4K: 100m / 1080p: 100m4K: 40m / 1080p: 40m
Always use the lower limit. If an installer says the cable run is 90m and they are using a neo:8a with neo:Pro receivers, the effective 4K limit is 40m (the matrix limit), not 70m (the receiver limit). The neo:8a simply cannot transmit 4K beyond 40m regardless of which receiver is used.

Important Notes on Cabling

  • Minimum cable spec: Cat5e for all runs. Cat6 or Cat6a is strongly recommended for runs approaching the maximum distance or for 4K.
  • Do not use EZ crimps or non-standard RJ45 crimps. These are a common cause of intermittent link quality issues even on short runs. See: Why should you not use EZ crimps or any non-standard RJ45 crimps?
  • Distances quoted are for straight runs. Patch panels, surface-run cable, tight bends, and poor terminations all reduce effective range. If a run is close to the limit, treat it as exceeding the limit until link quality has been verified.
  • Verify with the Link Quality test. Always run the HDBaseT Link Quality test on any run approaching the distance limit. See: HDBaseT Link Quality — How & What am I looking at?
Need help selecting the right receiver for an installation?
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