AV.io HD User Guide – Release Notes
2
On Windows 7, when AV.io HD is connected to the video source and capture computer, the AV.io
Config tool displays the device more than once in the device list.
Workaround:
Press the refresh icon to refresh the device list; only one AV.io HD device will now
properly display.
When AV.io HD is connected to the video source and capture computer on Windows 7, the AV.io
Config tool sometimes does not display AV.io HD on the device list despite showing up as an installed
device on the computer’s Device Manager.
Workaround:
Use AV.io Config on a different supported OS
to configure AV.io HD. Firmware
updates and configuration changes will be saved to the device. (Note that the AV.io HD device
still functions with the selected capture application on the original Windows 7 workstation
despite possible issues with the AV.io Config tool.)
Plugging in AV.io HD to a USB 3.0 port on Windows 8.1 causes the Windows Device Setup window to
freeze.
Workaround:
Close and ignore the frozen Device Setup window; AV.io HD is installed and
available for use.
On Windows 8.1/10, streaming is not possible when the capture computer with an ASMedia ASM1042A
USB 3.0 controller recovers from sleep mode.
In this scenario, AV.io HD is connected to both the capture computer and video source. Streaming is
initiated through the application, then stopped. The computer is then put in sleep mode, and upon
recovering from sleep, streaming cannot be resumed. This only occurs when using a capture computer
with an ASMedia ASM1042A USB 3.0 controller.
Workaround:
Connect to a different USB 3.0 controller. Use the lsusb command to list all USB
devices and connect to a different USB 3.0 controller that is not ASMedia.
Using Chromebook Apps (Clipchamp) and WebRTC on Google Chrome OS
v 43.0.2357.125 (64 bit), AV.io HD is not detected as a valid audio device.
Workaround:
Use Clipchamp and WebRTC for capturing video only, or use a different
Chromebook app to capture both video and audio.
In Ubuntu 14.04 LTS, the very first frame is always green in all streaming attempts (with the exception of
the first streaming attempt after device boot).
Workaround:
Remove the green frame in post-production editing. If streaming, begin stream
after the initial green frame as already been captured.
