Use this when one connected display should define the source capabilities. Vertex reads that sink EDID and presents it to the source.
Which Vertex EDID mode should I use?
EDID is simply the capability list Vertex shows to your source. Choose the mode according to the problem you are solving.
Use this when two connected sinks must coexist. Vertex builds an EDID from their capabilities. Start without unnecessary forced flags.
Use this as a conservative troubleshooting EDID when you simply need to establish a picture. The manual's Fixed EDID is 4K60 4:2:0 8-bit 300MHz with stereo audio; it is not suitable for Full HD-only or 4K30-max displays.
Use a specific preloaded/custom EDID when you intentionally need a defined capability set — for example a controlled HDR/DV workflow.
In AUTOMIX mode the flags 2.0 Stereo, 5.1 Multi, 7.1 Full, Native and TOP MAX change what audio capability the source sees; in CUSTOM mode the audio comes from the table you pick ("All Sound", "SPDIF" or "Stereo"). Do not advertise 7.1 merely because it sounds better; the downstream audio path must actually handle it.
Vertex can assign different EDIDs to its inputs. This is useful when two sources need different behavior.
Selecting a table in the GUI sends a hot-plug; otherwise CONFIG → ISSUE HOTPLUG or a short press on RST. Then check the source's newly available output modes and read the actual Vertex signal.
- The EDID mode has a clear purpose.
- The source has re-read EDID after changes.
- Advertised audio/video capability matches the real downstream chain.
- A custom DV/LLDV EDID is not introduced before basic HDR10 is stable.
If it does not work
I have two very different displays
Start by testing each alone. Automix is the logical next step when both must operate together; scaling may also be needed for 4K + 1080p combinations.
My source suddenly outputs stereo
The EDID/audio flags may advertise only 2-channel audio. Inspect the selected EDID/Automix audio setting.
I forced Dolby Vision but get no usable picture
Advertising a capability does not make the display capable of it. Return to the known-good HDR10 EDID and rebuild the intended LLDV/native-DV path carefully.