Joined
·
229 Posts
This is the thread for discussing the HDFury Vertex as well as support.
-General Support-
Please be descriptive in your support question and follow this format:
Source Brand/Model > length of HDMI cable (and type: copper/active/fiber) > Brand/Model > length of HDMI cable (and type: copper/active/fiber) > Brand/Model > etc...
In a setup with X1X, Vertex, X4200 and LG C7, in one chain, it would look like:
X1X > 6ft copper > Vertex > 6ft copper > X4200 > 6ft copper > LG C7
In a setup with X1X, Vertex, X4200 and LG C7, in split chain, it would look like:
X1X > 6ft copper > Vertex > 6ft copper > LG C7
---------------------------------> 6ft copper > X4200
Additional info we would like:
- FW in use and config (if possible)
- Confirmation that lock Icon is visible or not on OLED screen.
- Issue Description
- Link to any active or fiber cable in use.
- For users with any active or fiber cable, Test by replacing with copper: solve issue or not
- Test by power on sequence (power sink at outputs first, then source at input): solve issue or not.
Driver installation:
There are two different Silabs Drivers; v4.0.0 and v3.9.2. Try to install v.4.0.0 first and if you get a message saying cannot find any drivers for your system, then cancel and install v3.9.2 instead.
3.9.2 are mandatory for WinXP only.
To download Silabs Driver v4.0.0: http://www.hdfury.com/tools/Silabs_Driver_v4.zip
- Unzip it and navigate to the inner most Silabs_Driver_v4 folder. USBXpressInstaller_x64 application file is for Windows 64-bit. USBXpressInstaller_x86 for Windows 32-bit. Right mouse click on the correct version for your Windows and select Run As Administrator to install the driver.
To download Silabs Driver v3.9.2: http://www.hdfury.com/tools/Silabs_Driver_v3.zip
- Unzip it and navigate to the inner most Silabs_Driver_v3 folder. Right mouse click on USBXpressInstaller application file and select Run as Administrator.
After installation of the Silabs driver is complete, reboot your PC, connect your device and wait for USB notification sound (first connection after drivers install always take more time than next one).
~Courtesy of Claw
GoBlue update procedure: https://www.youtube.com/watch?time_continue=3&v=tJQVu4z_2ko
Fix for HIGH DPI settings with the VERTEX GUI:
Many of you may have noticed that by default the Vertex GUI doesn't play nicely with high resolution displays and/or scaling. Particularly with Windows 10.
The GUI is near-unusable (certainly unreadable) unless you drop to a lower DPI and/or resolution - at which point it may be very hard to read.
This is easy to fix in Windows 10, and I believe 8 as well:
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.
If you are like me and have a 4k PJ/TV and use 300% DPI scaling for the desktop you will seriously appreciate this.
~Courtesy of Ix
====Firmware as of 21-December-18====
====Q&A====
-Does the Vertex do frame rate conversion
No
-How do I connect the Vertex to a computer for firmware upgrade? Does it need less current in this case as for normal operation and and it is not required to have it connected to the power supply or are both Vertex and computer connected to the two USB ports of the power adapter and how exactly (port with one dot, port with two dots)?
-You connect the supplied USB powercord between your computer USB port and the Vertex USB port. If you just connect Vertex without any signal going through, power consumption is ridiculous, even if you play a signal at max speed power consumption doesn't exceed 1A, you would need to matrix two 18Gbps streams to go over 1A. Most computer USB port comes by 2 or 4, when 4 ports are available, it's usually one HUB ic sharing 5V2A for all 4 USB ports so each can get at least 0,5A (or 500mA) if they are all in use. So make sure if you want to use Vertex GUI software and play a signal at the same time that you don't have too many USB devices taking power at the same time. the Power adapter have 2 USB for convenience only, you can use any of them, so you can power Vertex and charge your phone at the same time if you want, or your joypad or your tablet, whatever...
-Okay, I have everything installed, but where do I begin?-
Here is a good starting point via HDFury:
-Is there Macro Control for the different modes?-
Yes, so far there is control for the JVC Projectors:
JVC calibration auto switch: 3D/x.v.color/SDR/HDR/HLG calibration autoswitch for 2015+ JVC PJs
JVC Macro not working?
Set the JVC to any mode but USER 1 [Note: in older models, RS-232 and IP control can't work at the same time, you have to select one or the other.
In 2015+ (and I think 2014 models) this isn't necessary and IP control works at the same time as RS-232].
Go to the RS232 tab in the Vertex GUI
Click "send test"
Until the JVC goes into User1, the RS232 control isn't working, so it's your cable (or the JVC) that doesn't work. It has nothing to do with the JVC Macro feature.
Please report back once you've got a working RS232-cable if you still have issues with the JVC Macro.
Recommended cables are listed in the original post about the Vertex JVC Macro feature, along with the pin assignment if you use your own cable.
See first post of the JVC Autocal thread in my sig for links to the Vertex related posts.
-OSD With Irule macro-
https://www.avsforum.com/forum/37-v...ury-vertex-owners-thread-26.html#post55210652
-Can I get ARC sound?-
If you want Vertex to retrieve ARC sound with Vertex, then VERTEX must be set as AUDIO SYSTEM with ARC under CEC devices settings (CEC must be enabled too).
Once this is done, the bottom output of Vertex must be connected to your TV ARC input and then you will have the TV ARC sound available at Vertex optical/analog out.
Optical is up to 5.1 and up to stereo for analog.
You can also just connect AVR ARC to TV ARC input and use Vertex thru another TV input if you don't want to use Vertex for ARC.
Latest Vertex firmware also allow to extract DD+ and ATMOS from TV APP and forward to AVR via optical (assuming your AVR support 192khz on optical input, very rare)
-What is the voltage of the TX/RX rs232 pins on the Vertex? I'm thinking of attaching it to raspberry pi serial port pins and need to know if it requires a level shifter from the default 3.3V levels on the pi.-
Yes need level shifter, Vertex is standard RS232, not an UART port.
voltage is around +-5V
Do not attach Pi to it without level shifter !
-What cables have been tested? or How should I place them-
- Any certified copper, active powered or fiber powered cable are ok.
For user with active cable non powered, read below.

-General Support-
Please be descriptive in your support question and follow this format:
Source Brand/Model > length of HDMI cable (and type: copper/active/fiber) > Brand/Model > length of HDMI cable (and type: copper/active/fiber) > Brand/Model > etc...
In a setup with X1X, Vertex, X4200 and LG C7, in one chain, it would look like:
X1X > 6ft copper > Vertex > 6ft copper > X4200 > 6ft copper > LG C7
In a setup with X1X, Vertex, X4200 and LG C7, in split chain, it would look like:
X1X > 6ft copper > Vertex > 6ft copper > LG C7
---------------------------------> 6ft copper > X4200
Additional info we would like:
- FW in use and config (if possible)
- Confirmation that lock Icon is visible or not on OLED screen.
- Issue Description
- Link to any active or fiber cable in use.
- For users with any active or fiber cable, Test by replacing with copper: solve issue or not
- Test by power on sequence (power sink at outputs first, then source at input): solve issue or not.
Driver installation:
There are two different Silabs Drivers; v4.0.0 and v3.9.2. Try to install v.4.0.0 first and if you get a message saying cannot find any drivers for your system, then cancel and install v3.9.2 instead.
3.9.2 are mandatory for WinXP only.
To download Silabs Driver v4.0.0: http://www.hdfury.com/tools/Silabs_Driver_v4.zip
- Unzip it and navigate to the inner most Silabs_Driver_v4 folder. USBXpressInstaller_x64 application file is for Windows 64-bit. USBXpressInstaller_x86 for Windows 32-bit. Right mouse click on the correct version for your Windows and select Run As Administrator to install the driver.
To download Silabs Driver v3.9.2: http://www.hdfury.com/tools/Silabs_Driver_v3.zip
- Unzip it and navigate to the inner most Silabs_Driver_v3 folder. Right mouse click on USBXpressInstaller application file and select Run as Administrator.
After installation of the Silabs driver is complete, reboot your PC, connect your device and wait for USB notification sound (first connection after drivers install always take more time than next one).
~Courtesy of Claw
GoBlue update procedure: https://www.youtube.com/watch?time_continue=3&v=tJQVu4z_2ko
Fix for HIGH DPI settings with the VERTEX GUI:
Many of you may have noticed that by default the Vertex GUI doesn't play nicely with high resolution displays and/or scaling. Particularly with Windows 10.
The GUI is near-unusable (certainly unreadable) unless you drop to a lower DPI and/or resolution - at which point it may be very hard to read.
This is easy to fix in Windows 10, and I believe 8 as well:
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.
If you are like me and have a 4k PJ/TV and use 300% DPI scaling for the desktop you will seriously appreciate this.
~Courtesy of Ix
====Firmware as of 21-December-18====
Vertex FW1.36.1.43 and GUI 1.34
Make sure to install Silabs driver first if you haven't yet done so.
This update IS mandatory (In case of any issue, it will be asked that you first update to this firmware version)
- Remember that after FPGA update, you must power cycle the Vertex and when you connect it back, the OLED will stay OFF for about 15s (time to apply the update internally), wait till OLED is back ON and then you can proceed normally.
- Easiest/Fastest/Recommended way: Update MCU, then Update FPGA, then powercycle. (if you was running FW1.36.37 or 1.36.1.41 or 1.36.1.42, you can skip MCU update)
- If you fine tuned your unit config and settings, export your config before update and import it back once update is completed.
- Once update is completed you might see a lock icon on the OLED top right corner, please do the combo trick: HOLD RST and PRESS INP 2 times, OLED will prompt for powercycle, simply remove/reconnect USB powercord (if you exported your config before update and imported back after update, you don't need to repeat this trick, the lock icon won't be visible)
##########> What's new/fixed in 1.36.1.43 and GUI 1.34
1. Oled showed HDR outgoing even when HDR was disabled - fixed
2. Improved autosense routines which would convert in some case to deep color even if input is not deep color. Modified and improved autosensing throughout direct paths, upscaling paths and downscaling paths.
3. Cleared Oled display bug that popped up since 1.36.1.41 (flashing character and extra character on some oled page)
4. Updated input routine for 4K24 422 12b and 4K60 422 12b now supporting more sources even if their timing are slightly off.
Download Link: https://hdfury.com/tools/Vertex_1.36.1.43_GUI_1.34.zip
The default Auto-Sense mode for Auto-Scaling (SCALE slide on AUTOSCALING) coupled with default Custom EDID (EDID slide on CUSTOM) should be enough to give you a picture in any setup.
If not, please remember than when using AUTOSCALING, you have access to 10 quick-presets that are specifically introduced for the TOP port down-scaling. (refer to usermanual p.14)
Auto Sense also upscale automatically except if manually turned OFF from GUI/APP/IR/RS232.
KNOWN ISSUES:
- For users of the first Vertex PCB version (PCB1) with HDMI active cable non powered by their own power supply, please refer to that post if you are experiencing issue. (You can easily isolate the issue by testing with 6-12ft copper)
For any support issue/question:
- Please export your vertexconfig.txt (GUI > FILE > EXPORT) when trying the signal through and having the issue (if possible) and attach it as a txt file in your post.
- If you cannot provide config file, then it's mandatory to confirm you are running the latest firmware 1.36.1.43.
- Issue Description, ultimately with Link to Display and/or AVR usermanual in PDF format and Link to any active or fiber cable in use.
- Always make conclusion and bug report using Wall Plug Adapter to power Vertex.
- If you have a lock icon on OLED top right corner: HOLD RST and press INP 2 times, Vertex OLED will prompt for powercycle (Remove/Reconnect USB powercord > lock icon will disappear after restart)
- Always describe your video chain path with brand/model of all equipment as well as hdmi cable length and type between them (ex: SOURCE Brand/Model > 6ft copper > Vertex INP0-OUT1> 6ft copper > AVR Brand/Model > etc...)
Example of video chain description:
Source Brand/Model > length of HDMI cable (and type: copper/active/fiber) > Brand/Model > length of HDMI cable (and type: copper/active/fiber) > Brand/Model > etc...
In a setup with X1X, Vertex, X4200 and LG C7, in one chain, it would look like:
X1X > 6ft copper > Vertex > 6ft copper > X4200 > 6ft copper > LG C7
In a setup with X1X, Vertex, X4200 and LG C7, in split chain, it would look like:
X1X > 6ft copper > Vertex > 6ft copper > LG C7
---------------------------------> 6ft copper > X4200
====Q&A====
-Does the Vertex do frame rate conversion
No
-How do I connect the Vertex to a computer for firmware upgrade? Does it need less current in this case as for normal operation and and it is not required to have it connected to the power supply or are both Vertex and computer connected to the two USB ports of the power adapter and how exactly (port with one dot, port with two dots)?
-You connect the supplied USB powercord between your computer USB port and the Vertex USB port. If you just connect Vertex without any signal going through, power consumption is ridiculous, even if you play a signal at max speed power consumption doesn't exceed 1A, you would need to matrix two 18Gbps streams to go over 1A. Most computer USB port comes by 2 or 4, when 4 ports are available, it's usually one HUB ic sharing 5V2A for all 4 USB ports so each can get at least 0,5A (or 500mA) if they are all in use. So make sure if you want to use Vertex GUI software and play a signal at the same time that you don't have too many USB devices taking power at the same time. the Power adapter have 2 USB for convenience only, you can use any of them, so you can power Vertex and charge your phone at the same time if you want, or your joypad or your tablet, whatever...
-Okay, I have everything installed, but where do I begin?-
Here is a good starting point via HDFury:
To make it more easy for everyone, there is 2 easy way for Vertex:
1. AUTOMIX + NO SCALING (source will send a signal that always match max mixed capabilities of both displays), Note that if AVR support 300MHz and display support 600MHz, it might try to send 600MHz with full sound, in such case, you need to change automix algo from MAX VIDEO/MAX AUDIO, to MIN VIDEO/MAX AUDIO.
2. CUSTOM EDID + AUTOSCALING (This should be default testing setup for everyone)
The other way possible is if sinks support the capabilities set by CUSTOM EDID (CUSTOM EDID+ NO SCALING), for ex, if you have 18Gbps/600MHz sinks, you might want to use that mode.
Finally the advanced users way is CUSTOM EDID + CUSTOM SCALING. (it cannot work if sinks are not both 600MHz until you manually set CUSTOM SCALING rules)
All above is assuming Custom EDID is default MAX.
Reminder that the EDID determines what your source is seeing and will send. SCALER determines what Vertex will do with that signal and how it will output it.
-Is there Macro Control for the different modes?-
Yes, so far there is control for the JVC Projectors:
JVC calibration auto switch: 3D/x.v.color/SDR/HDR/HLG calibration autoswitch for 2015+ JVC PJs
JVC Macro not working?
Set the JVC to any mode but USER 1 [Note: in older models, RS-232 and IP control can't work at the same time, you have to select one or the other.
In 2015+ (and I think 2014 models) this isn't necessary and IP control works at the same time as RS-232].
Go to the RS232 tab in the Vertex GUI
Click "send test"
Until the JVC goes into User1, the RS232 control isn't working, so it's your cable (or the JVC) that doesn't work. It has nothing to do with the JVC Macro feature.
Please report back once you've got a working RS232-cable if you still have issues with the JVC Macro.
Recommended cables are listed in the original post about the Vertex JVC Macro feature, along with the pin assignment if you use your own cable.
See first post of the JVC Autocal thread in my sig for links to the Vertex related posts.
-OSD With Irule macro-
https://www.avsforum.com/forum/37-v...ury-vertex-owners-thread-26.html#post55210652
-Can I get ARC sound?-
If you want Vertex to retrieve ARC sound with Vertex, then VERTEX must be set as AUDIO SYSTEM with ARC under CEC devices settings (CEC must be enabled too).
Once this is done, the bottom output of Vertex must be connected to your TV ARC input and then you will have the TV ARC sound available at Vertex optical/analog out.
Optical is up to 5.1 and up to stereo for analog.
You can also just connect AVR ARC to TV ARC input and use Vertex thru another TV input if you don't want to use Vertex for ARC.
Latest Vertex firmware also allow to extract DD+ and ATMOS from TV APP and forward to AVR via optical (assuming your AVR support 192khz on optical input, very rare)
-What is the voltage of the TX/RX rs232 pins on the Vertex? I'm thinking of attaching it to raspberry pi serial port pins and need to know if it requires a level shifter from the default 3.3V levels on the pi.-
Yes need level shifter, Vertex is standard RS232, not an UART port.
voltage is around +-5V
Do not attach Pi to it without level shifter !
-What cables have been tested? or How should I place them-
- Any certified copper, active powered or fiber powered cable are ok.
For user with active cable non powered, read below.
Monoprice Active & NON-POWERED cable was received and tested today. (50ft version: order page)
First of all, my apologies because in my mind active cable meant powered.
It appears that Vertex have zero issue with any Active or Fiber as long as they are powered (that's why celerity tek had no issue in our tests, they are powered)
If people remember from Linker or Integral experience, when users had issue when trying to do:
... > AVR > 6ft HMDI > Integral or Linker > Long distance active not powered > Display
The recommendation was always to do:
... > AVR > Long distance active not powered > Integral or Linker > 6ft HDMI > Display
And the reason given was:
An AVR will always supply better 5V at output than a 5V device as driving copper is not powering active.
Well, it happens that the exact same situation apply to Vertex
As we ran and completed the cable tests, here is the data, info and conclusion we can make:
- Its an active cable that draws power from the +5 pin of the connector. It takes around 70mA which is like 350mW. It should give issue with some sources but not after an AVR.
- When connected to PC USB port, we get no signal (PC USB Port too weak, the cable does not activate at all). We measured around 4.23V at the +5 V pin and this apparently does not allow it to work at all. Too low.
- When connected to the Fury supply we measure around 4.5V at the +5 pin and we can see a picture but get little white dots here and there randomly which we know exactly are signal integrity issues and they are produced by the monoprice cable. (or any unpowered active cables)
- When connected a +5V source from our lab equipment rack then we get around 4.8V at the +5 pin and with this config we cannot see any white dots.
The issue is that those 5v cable drew too much voltage or that Vertex (or Integral or Linker) doesn't provide enough for them.
The snow/stripes customer sees are not related to sync or hdcp, they are signal integrity issues (which can ultimately lead to sync issue)
Tests were made with 50ft, shorter might give better results, longer surely worst. The longer the cable the more underpowered it will be.
And when device is underpowered, anything can happen, Vertex might not sync since there is nothing to sync with Or vertex sees a device which suddenly goes away or in an endless loop.
Two possibilities/solutions: (that also apply to Linker/Integral)
1. Using shorter/thicker USB cord from PSU to Vertex can help. We will of course also start sourcing thicker cable and start shipping them with all our devices as it can help supporting such cables.
Thicker cable will have less Voltage loss.
2. Use 5.15V or so Power supply. We will there also also modify our power supply to offer more support for such cables in the future, this might takes a while for us.
You can try using tablet or smartphone charger in the meantime or a specialized USB power source.
Current power supply gives 5V, but since Vertex takes like 0.6A and some of the voltage is lost on the cable itself. At the input of Vertex USB, the voltage is already like 4.75
increasing to 5.1 or 5.2V means that under heavy load the input voltage is around 4.8-4.85 and under light load could be exactly 5.0
right now using the 5.0V supply the light load voltage is around 4.8-4.85 (some might work better than others)
All the above is really ONLY relevant for such non-powered active cables and exclusively at output.
Bottom line for Vertex users with such non powered active cable at Vertex output:
- You can move Vertex after it, so active cable is at input.
- You can replace it by powered active or fiber.
- You can try getting thicker/shorter USB powercord.
- You can try another PSU from smartphone or tablet
- You can use a specialized USB power source.
- You can try power injector (take care of artifacts at 600MHz)
- You can use our Universal Power Supply, output 1 offers 5.25V