View source for Multiple Kinects v2 on a Single PC

{{Note|Starting from version [[iPi_Recorder_Release_Notes#ver._4.2.0.70|4.2.0]]}}

[[iPi Recorder]] supports multiple Kinects v2 on a single PC using [https://github.com/OpenKinect/libfreenect2 libfreenect2] instead of Microsoft Kinect SDK v2.

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)'''.

<center><table border=0><tr>
<td>[[File:Enable-Kinect2-libfreenect2.png|thumb|240px]]</td>
<td>[[File:Add-Device-Kinect2-multiple.png|thumb|610px]]</td>
</tr></table></center>

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.

= UsbDk =

Just [https://github.com/daynix/UsbDk/releases 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.

{{Tip|We recommend to [https://www.howtogeek.com/236241/how-to-enable-disable-and-customize-autoplay-in-windows-10/ disable Windows Autoplay feature] for Kinect devices (set it to '''Take no action''') when using UsbDk. Otherwise, an autoplay action may trigger once in a while when using Kinects in iPi Recorder.}}

= libusbK =

This driver can be installed using [https://zadig.akeo.ie/ 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.

== Install ==

# 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'''.
#: [[File:Zadig-device-list-settings.png|400px|Device list settings]]
# Then select '''Xbox NUI Sensor (Composite Parent)''' from the device combo.
#: [[File:Zadig-select-Xbox-NUI-Composite.png|400px|Select Xbox NUI Sensor]]
# Select '''libusbK''' driver and hit '''Replace Driver''' button.
#: [[File:Zadig-replace-driver.png|400px|Replace driver]]
# 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.

{{Tip|There is no need to install the driver for each of Kinect devices you plan to use on that PC. After installing for one, all others will take new driver when connected.}}

== Uninstall ==

# Connect Kinect v2 to a PC.
# Open Windows Device Manager.
# Locate '''Xbox NUI Sensor (Composite Parent)''' device, right-click and select '''Uninstall device'''.
#: [[File:Device-Manager-uninstall-libusbK.png|400px|Uninstall device]]
# In uninstall dialog, check '''Delete the driver software for this device'''.
#: [[File:Device-Manager-delete-libusbK.png|400px|Delete driver]]
# 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.
*:{{Tip|PCIe cards with multiple μ720202 chips onboard exist that should be capable of connecting 1 Kinect device per chip.}}
*:* [http://www.amazon.com/gp/product/B00HJZE9VK/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B00HJZE9VK&linkCode=as2&tag=wwwipisoftcom-20&linkId=PQTOLAJFTO7X7OJM StarTech PEXUSB3S42V] with 2 chips
*:* [http://www.amazon.com/gp/product/B00HJZEA2S/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B00HJZEA2S&linkCode=as2&tag=wwwipisoftcom-20&linkId=YI76ZKZOGLKPPHFM StarTech PEXUSB3S44V] with 4 chips
* 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.