HDfury Vertex
BEGINNER / SIGNAL DIAGNOSTICS

WHAT IS VERTEX
ACTUALLY SEEING?

Do not troubleshoot from the player menu alone. Vertex sits in the HDMI path and can show you what signal is really arriving and what is being sent onward. Read the line from left to right.

Example:
4K59.94   422   BT2020   12b   HDR   594MHz   2.2
(line from the manual, p.19: resolution + refresh, chroma, colorimetry, bit depth, HDR flag, TMDS clock, HDCP version. With TV-led Dolby Vision the line shows RGB and 8b — that is normal, manual p.113.)
4K59.940

Resolution + refresh rate. “4K” is the picture resolution; 59.940 is roughly 60 frames/Hz timing. A movie may instead show about 23.976/24.

593 MHz

HDMI/TMDS signal clock class. Around 594 MHz is near the top of the original Vertex 18Gbps HDMI 2.0-class transport. It does not mean 593 Hz display refresh.

RGB / YCbCr

Color encoding. RGB and YCbCr are different ways of carrying picture/color information. YCbCr may additionally be 4:4:4, 4:2:2 or 4:2:0.

8b / 10b / 12b

Bit depth. This is color precision per component. HDR commonly uses 10-bit-class output; Dolby Vision/LLDV paths can use formats such as 12-bit 4:2:2 depending on source and workflow.

HDR / DV / LLDV

Dynamic-range / metadata state. Use this together with the display's own HDR mode. A DV-capability EDID does not by itself prove the display is native Dolby Vision.

HDCP 1.x / 2.2

Copy protection handshake. A black screen can be HDCP-related, but do not assume HDCP is the cause before checking resolution, EDID and cables.

RX and TX — the easiest way to find the fault

RX = what Vertex RECEIVES.
If RX is wrong, look upstream: source settings, source cable, source EDID interpretation.
TX = what Vertex TRANSMITS.
If RX is correct but TX/display is wrong, look downstream: Vertex routing/scaling, output cable, AVR/display capability or HDMI input mode.
Simple rule: first compare RX with what you expected from the source. Then compare TX with what the display can actually accept.

Common readings in plain English

WHAT YOU SEEWHAT IT USUALLY MEANSWHAT TO CHECK NEXT
1080p when you expected 4KThe source has selected a lower mode or the EDID/path does not advertise the expected 4K capability.Check active EDID, source resolution and HDMI input enhancement mode.
4K24 works, 4K60 failsThe higher-bandwidth path is failing or not being advertised.Check display/AVR Enhanced mode, Vertex EDID, cable quality and chroma/bit depth.
RX correct, display blackThe source-to-Vertex side is working; investigate the output side.Test Vertex → display directly, one output, simpler format, then AVR/second display.
HDR content but no HDR stateHDR is not being output, advertised or recognized somewhere in the chain.Prove known HDR10 content, inspect EDID/HDR capability and display HDMI mode.
Only stereo audio availableThe EDID presented to the source may advertise 2-channel audio.Check Automix/custom audio flags and the actual AVR/audio path.
DV option disappearsThe source no longer sees the required DV capability in EDID.Check the selected Vertex EDID, then force a fresh handshake/restart the source.
Bandwidth matters: the original Vertex is an 18Gbps / 600MHz HDMI 2.0-class device. HDMI 2.1 FRL modes (4K120 10-bit or 4:4:4, VRR, 48Gbps) are outside its signal path; 4K120 4:2:0 8-bit and 8K30 4:2:0 8-bit fit within 600MHz. A newer TV/projector may support those modes directly even though Vertex does not.

Use this troubleshooting order

1. One source → Vertex → one display.
2. Get SDR picture.
3. Get normal HDR10.
4. Compare Vertex RX and TX.
5. Add custom EDID / LLDV only now.
6. Add AVR and second display last.

CD-R Nederland / HDfury · Postbus 274, 8070 AG Nunspeet · KvK 08073694 · VAT NL002139420B84