Multiple Kinects v2 on a Single PC
To use this, first you need to enable corresponding camera type in iPi Recorder. Open Camera Types panel and hit ENABLE next to Microsoft Kinect 2 (libfreenect2). Alternatively, open Add Device dropdown and select Kinect 2 for Windows (multiple sensors per PC).
Next you need to install a driver for Kinect that makes it accessible to libfreenect2. There are two options - UsbDk and libusbK.
We recommend to start with UsbDk as an easier option. And turn to libusbK if:
- You have troubles installing UsbDk.
- It doesn't work as expected. E.g. Kinect is not visible in iPi Recorder when libfreenect2 support is on, or works unstable.
- It causes problems with other USB devices.
Just download and install the latest release (1.0.19 as of the moment of writing) and you are done. iPi Recorder can use Kinect v2 devices via libfreenect2. Moreover, because of the smart way UsbDk handles driver replacement you can still use other programs which work with Kinect in a standard way via MS Kinect SDK 2.0.
This driver can be installed using Zadig tool. There are few drawbacks compared to UsbDk:
- (Un)installation of the driver is more complicated (see below).
- While libusbK driver is installed for Kinect, programs which rely on MS Kinect SDK won't see the device.
- Run Zadig tool (2.4 as of the moment of writing).
- Connect Kinect v2 to a PC.
- Under Options menu, check List All Devices and uncheck Ignore Hubs or Composite Parents.
- Then select Xbox NUI Sensor (Composite Parent) from the device combo.
- Select libusbK driver and hit Replace Driver button.
- Click Yes in confirmation dialog which appears after a few seconds.
- Upon successful installation of the driver close Zadig.
Now Kinect is available to libfreenect2 in iPi Recorder.
- Connect Kinect v2 to a PC.
- Open Windows Device Manager.
- Locate Xbox NUI Sensor (Composite Parent) device, right-click and select Uninstall device.
- In uninstall dialog, check Delete the driver software for this device.
- Scan for hardware changes, and MS Kinect SDK driver will be restored automatically.
Connecting to PC
We have tested libfreenect2 support with a number of USB 3.0 controllers. Here are some findings:
- Intel (built-in), 200 series and above chipsets
- Stable work of dual Kinects with occasional frame drops.
- Intel (built-in) other
- Stable work of a single Kinect. With two connected, there are frame drops and low frame rate issues.
- Works with 5m active USB 3.0 extension cable.
- No depth data with 1.8m passive USB 3.0 extension cable.
- NEC μ720202 (PCIe card)
- Stable work of a single Kinect. With two connected, Windows reports insufficient USB bandwidth for one of them.
- Unstable work with 5m active USB 3.0 extension cable - frame drops.
- Unstable work with 1.8m passive USB 3.0 extension cable - frame drops, low frame rate.
- ASMedia ASM1042A (built-in).
- Stable work of two Kinects with rare FPS issues.
- VIA VL800 (PCIe card). Doesn't work.
- Etron EJ168 (built-in). Doesn't work.