Pro Tips
Practical tips on Dolby Vision, Windows GUI scaling, AVI InfoFrame examples, iRule, ARC audio and reported frame rates.
ALL CHAPTERS
Pro Tips
Dolby Vision: DV mode 0 and 1 travels thru 8b RGB container, so it is normal that Vertex report RGB 8b when playing such DV mode. If Vertex is not directly connected to your DV TV and you have equipment in between, please first connect Vertex bottom output to your TV input and let Vertex boot up. Then disconnect and insert equipment in between. Vertex will sniff your TV EDID and present it to your source, therefore allowing you to go thru equipment that doesn’t support Dolby Vision.
If Windows GUI does not display nicely on your screen:
→ See: USB GUI for Windows- Make sure the GUI isn't already running, then right click the GUI exe file (the regular one, there's no need to do this with the 200dpi version)
- Click the "Compatibility" tab.
- Look down for "Override high DPI scaling behavior" and check the box.
- For the drop-down under "Scaling Performed by" choose "System - Enhanced"
- Start the GUI and revel in how it works normally now.
Bot Output is CEC/ARC capable
Ex of AVI InfoFrame:
BT.2020 RGB 00:E8:64:5D:00
BT.2020 YCbCr 4:2:2 20:E8:64:5D:00
BT.2020 YCbCr 4:4:4 40:E8:64:5D:00
BT.2020 YCbCr 4:2:0 60:E8:64:5D:00
4k24 422 709 ycbcr no-bt2020 20:88:00:00
4k24 422 ycbcr bt2020 20:c8:60:00
4k24 444 709 ycbcr no-bt2020 40:88:00:00
4k24 444 ycbcr bt2020 40:c8:60:00
1080p 422 709 ycbcr no-bt2020 20:88:00:10
1080p 422 ycbcr bt2020 20:c8:60:10
iRule use \x0D instead of \r (or \x0A for /n) to terminate the RS232 command string.
→ See: RS232 controlSome sources like X1S or K8500 might need to have powercord removed/reconnected between EDID changes
Atmos via ARC require HDMI Cable that support 192khz ARC, even if a cable support 600MHz video signal it can still fail for 192khz audio signal.
You can read one, or mix two connected Sink EDIDs, apply forced flags and algo to it and then save it as an EDID file, thus creating your own Custom EDID variation.
Any 4:2:2 signals is always processed at 12b and never clipped. That’s why it mentions “up to 12b”.
Source VS Vertex frame rate reported: Actually very few devices will report the correct frame rate. It is all about the clock frequency, the theory is 24/1.001 = 23.976023976
BUT there is no PLL (https://en.wikipedia.org/wiki/Phase-locked_loop) at the source that actually gives a corresponding clock which would yield that. So once a signal leaves the source, the clock is always off and usually ebbs and flows, means changes all the time. We just decided to show what it really is from the particular source rather than approximating what it should be as many are doing since they cannot report exact frame rate like we are doing with Vertex.
Team HDfury thanks you for your support
For help visit our support server or contact us.

www.HDfury.com
Vertex was built with love and passion for our 10th Anniversary.
Source: official User Manual 4K Vertex, Rev 1.30. Text and figures © HDfury, reproduced for Vertex owners.