Vertex settings for Dolby Vision & LLDV

0. Before you start

1. Put all three slide switches in the middleEDID slide · HDCP slide · SCALE slide (on the unit)Middle position (Custom Use/BT · Auto/GUI · Custom Scaling/GUI)Only in the middle position does the Vertex follow the GUI, IR, RS232 and app settings (manual p.8, 11, 12).
2. Use the supplied power supplyMini-USB power inputVertex 5 V / 2 A USB supplyToo little power is a common reason for an OLED that stays off (manual p.6, 111).
3. Install the USB driver and the GUIWindows PC → Silabs USBXpress driverDriver 4.0.0 for Windows 10/11 (3.9.2 for XP)Needed for the Windows GUI and for firmware updates. Use the GUI/updater folder that matches the driver version (manual p.20).
4. Check the firmwareVertex GUI → top-right box "FW:" and "GUI:"Latest: FW 1.38.1.45 with GUI 1.34 (09-01-2020)Update with the "Update FPGA" and "Update MCU" programs in the firmware package, then unplug and replug the power. No light for about 15 seconds after the FPGA update is normal. If a lock icon appears afterwards: hold RST, press INP twice, release (manual p.13, 21–24).
5. Save your settingsGUI → Config → EXPORTSave the config fileYou can restore it with Config → IMPORT, for example after a firmware update (manual p.43).
6. Know the two outputsBOTTOM output = TX0 · TOP output = TX1Dolby Vision TV → BOTTOM · HDCP 1.x / 1080p devices → TOPThe Vertex reads a TV's Dolby Vision data only from the BOTTOM output; BOTTOM is also the CEC/ARC port. The TOP output is the downscale port and must be used for HDMI/HDCP 1.x devices (manual p.5, 36, 113).
7. Start from a known-good stateGUI → EDID MANAGER → CUSTOM → PORT 0: "11 - 4K60-444 600MHz HDR BT2020 All Sound" · SCALER → NO SCALINGProve normal HDR10 firstIf HDR10 does not work, Dolby Vision will not either. Factory reset if needed: hold RST for more than 10 seconds, or CONFIG → RESET TO FACTORY DEFAULTS (manual p.7, 33).

A. Native Dolby Vision to a Dolby Vision TV

The TV does the Dolby Vision processing. The Vertex must show the source the TV's Dolby Vision capability and pass the signal through unchanged.

1. Connect the TV to the BOTTOM outputVertex BOTTOM output (TX0) → TV HDMI input with full 4K HDR bandwidthTV input in its full-bandwidth mode (see the TV guide)The Vertex captures the TV's Dolby Vision block only from BOTTOM (manual p.36, 113).
2. Let the Vertex read the TVBoot the Vertex with the TV connected directly to BOTTOM · GUI → DV / IF tab → "CAPTURED DOLBY VISION METADATA BLOCK [BOT output]"A hex string with decoded values appearsThat proves the Vertex has stored the TV's Dolby Vision data (manual p.36).
3. Choose the EDIDGUI → EDID MANAGERCOPY BOT SINK (simplest) — or AUTOMIX with "DV Force Metadata" ticked — or CUSTOM "2 - CUSTOM 2 [FULL + LG DV]" / "3 - CUSTOM 3 [FULL + Vizio DV]"Copy BOT Sink presents the TV's own EDID. Automix builds one EDID from both outputs; "DV Force Metadata" keeps Dolby Vision in it using the captured TV block (manual p.15, 28–29, 36).
4. Leave these Automix flags offEDID MANAGER → Automix flags"DV Remove" OFF · "DV Limit 300MHz" only if the TV accepts Dolby Vision only up to 300 MHzDV Remove deletes Dolby Vision from the EDID (manual p.28).
5. No scalingSCALE slide → No Scaling/Passthru (or GUI → SCALER → NO SCALING)PassthroughTV-led Dolby Vision travels inside an RGB 8-bit signal. Converting it would destroy the Dolby Vision data (manual p.113).
6. InfoFrame tools offGUI → HDR IF tab and AVI/VSI IF tab"Enable Custom HDR", "Disable HDR", "Enable Custom AVI/VSI", "Disable AVI", "Disable VSI": all OFFDolby Vision is signalled in the vendor-specific InfoFrame; changing InfoFrames can stop the TV from detecting it (manual p.32–35).
7. HDCP on AutoHDCP slide → middle (Auto/GUI)AutoUHD Blu-ray and streaming apps need HDCP 2.2 to the TV; Auto always outputs a working level (manual p.11).
8. Select Dolby Vision on the sourceSee the guide of your playerTV-led / standard Dolby VisionA source that re-reads the EDID may need a hot-plug: GUI → CONFIG → ISSUE HOTPLUG, a short press on RST, or unplug the source's power (manual p.7, 41, 113).
9. Check the OLEDVertex OLED page 1 "Info", lines INP and TX0RGB · 8b while Dolby Vision playsThe manual says RGB 8-bit is normal for Dolby Vision (p.113). The TV's own info banner should show Dolby Vision.

B. Dolby Vision (LLDV) on an HDR10 projector or TV

With LLDV the source converts the Dolby Vision content itself and sends a finished HDR picture. The source only does this when the EDID it sees advertises low-latency Dolby Vision. The Vertex has no built-in LLDV table, so you upload an LLDV EDID file.

1. Prove HDR10 firstSource → Vertex (EDID table 11, No Scaling) → displayHDR10 content shows as HDR on the displayThis rules out cables and bandwidth before you change the EDID.
2. Get an LLDV EDID fileHDfury EDID collection (Vertex download page) or the EDIDs linked in HDfury's LLDV articleAn EDID with a low-latency Dolby Vision block (for example the Sony A1 LLDV EDID, or a custom BT2020 / DCI-P3 LLDV EDID)HDfury pairs each EDID with a matching colour profile on the display: BT2020 EDID → BT.2020, DCI-P3 EDID → DCI-P3.
3. Upload it into a free custom slotGUI → EDID MANAGER → Load from File → choose the .bin file → Upload EDIDUse an empty slot: CUSTOM 4 to CUSTOM 10Leave CUSTOM 1–3 as they are; they are the factory tables (manual p.15, 29).
4. Select it for the input of your LLDV sourceEDID MANAGER → CUSTOM → PORT 0 (input 0) or PORT 1 (input 1) → your slotEach input can have its own EDID; the other port can "Follow PORT 0 EDID"Selecting a table sends a hot-plug, so the source re-reads the EDID (manual p.28–29).
5. Check what the source now seesEDID MANAGER → Read RX EDIDThe Dolby Vision block of your LLDV EDID is presentYou can save it to a file and open it in an EDID viewer (manual p.29).
6. No scalingSCALE slide → No Scaling/PassthruPassthroughThere is nothing to convert; owners report that LLDV arrives as YCbCr 4:2:2 12-bit.
7. Select Dolby Vision on the sourceSee the guide of your playerThe Dolby Vision / player-led optionSome sources need a restart or a power-cord pull before they offer Dolby Vision after an EDID change.
8. Make the display switch to HDRSee part B2 belowProjector forced into HDR, or Vertex "Enable Custom HDR"LLDV carries no HDR10 flag, so many displays stay in SDR mode by themselves. HDfury: with the original Vertex, LLDV works with a JVC projector using a custom gamma curve, or with a display that can be forced into HDR mode.

B2. Make the display switch to HDR

Each display guide says which route works for that model. There are three:

1. Route 1 — force HDR on the displayDisplay menu (for example Epson: Signal → Dynamic Range → HDR10; JVC NZ: Content Type → HDR10; Sony projectors: Picture → Expert Setting → HDR → HDR10)HDR10 / PQ by hand, colour space BT.2020Nothing to change on the Vertex. Set the display back to Auto for normal SDR and HDR10 viewing.
2. Route 2 — let the Vertex send an HDR10 InfoFrameGUI → HDR IF tab → CUSTOM HDR METADATA GENERATOR: EOTF "SMPTE ST 2084" · Primaries (match your EDID: ITU-R BT2020-2 or DCI P3) · White Point D65 · Max/Min Luminance · MaxCLL · MaxFALL → Create IF → Send HDR"Enable Custom HDR" becomes tickedThe manual: Enable Custom HDR "will turn ON the HDR mode of any HDR display" (p.32). Needed for displays that only switch to HDR on an HDR10 flag (BenQ, Optoma, Samsung and others). The factory values are ST 2084, DCI-P3, D65, 4000 / 0.005 nits, MaxCLL 1000, MaxFALL 400; HDfury publishes no recommended LLDV values.
3. Route 3 — JVC custom gammaGUI → HDR IF tab → Disable HDR (JVC PJ mode) + a custom gamma curve on the JVCDisable HDR ONCancels all incoming HDR metadata so the JVC's own gamma is used (manual p.32; HDfury LLDV article).
4. Important: Custom HDR stays onEnable Custom HDR · IR codes vertex_hdrcustomon / vertex_hdrcustomoff · RS232 #set hdrcustom on|offSwitch it OFF when you watch SDR or normal HDR10It survives hot-plugs and power cycles and is added to every signal, so SDR would also be shown in HDR mode (manual p.32, 51, 77–78). Exception: a source set to send everything as Dolby Vision.

C. Two outputs, AV receiver, audio

1. Dolby Vision TV + AV receiver for soundTV → BOTTOM output · AVR → TOP output · EDID: AUTOMIX (algorithm "Max Audio, Max Video" or "Bot Output Priority")CONFIG → MUTE BOT TX AUDIO = ON if the AVR plays the soundThe TV gets the picture, the AVR gets the audio (manual p.28, 42).
2. AVR between Vertex and a Dolby Vision TVFirst connect the TV directly to BOTTOM and boot the Vertex, then put the AVR back in betweenAUTOMIX with "DV Force Metadata"The Vertex keeps offering the TV's Dolby Vision capability, even through equipment without Dolby Vision (manual p.113).
3. Dolby Vision TV and a non-DV projector on one VertexBoth outputs carry the same source signal (splitter mode)Not both in Dolby Vision at the same timeTV-led DV looks wrong on a projector, and LLDV is not native DV on the TV. Switch the EDID per viewing, for example with the IR codes for the EDID tables. Matrix mode (hold INP for 2 seconds) lets each output show a different input (manual p.10).
4. Audio follows the EDIDAutomix flags 2.0 Stereo / 5.1 Multi / 7.1 Full / Native / TOP MAX, or a CUSTOM table named "All Sound", "SPDIF" or "Stereo"Match your real audio systemAn LLDV EDID file brings its own audio block; check it with Read RX EDID. Lossless formats (TrueHD, DTS-HD MA, Atmos) only pass over HDMI; the 3.5 mm D/A jack gives stereo analog or up to 5.1 optical (manual p.15, 28, 104).

D. Read the signal on the Vertex

E. Common problems