Limitations and Known Issues

This section includes known issues or limitations that affect functionality or usability for the current release and offers workarounds these them.

• Video grabber may not be recognized by the system after reboot.
  Workaround: Physically disconnect the video grabber from the computer's USB port and reconnect it. If this workaround poses a problem for your specific use case, consider purchasing a new DVI2USB 3.0; a hardware update resolved this problem permanently for devices with serial number 358800 and higher.
• Capturing HDMI sources with Adobe RGB 32 color space (argb32) can cause image corruption.
  Workaround: If you see image corruption with this color space, switch to another color space.
• Opening the video signal in multiple applications at the same time on your video workstation affects signal performance. For the best performance during live streaming and recording, we recommend that you close any unnecessary applications that access the video signal. For example, if you aren't using the Epiphan Capture Tool for live streaming or to record, close the tool after you finish configuring the video grabber.
• DVI2USB 3.0 doesn't capture on Ubuntu 18.04 and 16.04 systems with AMD Ryzen5 (1600) AMD USB 3.0 controllers when audio is enabled.
  Workaround: In the Epiphan Capture Tool, disable Enable Audio Capture under Capture or update your USB 3.0 controllers to AMD Ryzen5 (2600).

• DVI2USB 3.0 doesn't capture on Windows 10 (64-bit) 1709 systems with AMD Ryzen5 (1600) AMD USB 3.0 controllers when audio is enabled and captures at a very slow frame rate when audio is disabled using the Epiphan Capture Tool.
  Workaround: Update your USB 3.0 controllers to AMD Ryzen5 (2600).

• The Epiphan Capture Tool labels VGA input signals that are 1400x1050 @ 60fps as 1680x1050 in the window title, even though the actual signal is 1400x1050. The input signal is not impacted and you can either disregard the text in the title or add a custom video mode that is 1400x1050 @ 60fps.