Yes, trace would be great. And what exact version of iPi Recorder do you currently use?

Attached to original message
v2.0.0.12

Quick update - on the laptop, SDK 1.5 works perfectly.
Even detects calibration plane way better than I had on this machine which uses PrimeSense drivers, this is very strange.

Can you please provide us a screenshot of how Kinects are looking in Device Manager when using Kinect SDK drivers?

Let me reproduce it first - with PrimeSense drivers everything works so I deinstalled SDK 1.5 already.

2Aktion:

Today got the same "not powered" issue from once more customer by email. Later he wrote that they've bought another Kinect, and it works fine. So maybe it is some hardware problem in specific instances of Kinect. It is strange that it is also computer-dependant, as you say your Kinects work fine connected to laptop.

Anyway, your Device Manager screenshot definitely shows that there is some problem between your devices and Kinect SDK drivers. Instead of "Microsoft Kinect Audio Array Control" devices under "Microsoft Kinect" node there are "Kinect USB Audio" devices under "Other devices" node. You can find the "correct" picture in Device Manager on this page.
Also, here there is a sequence of connecting Kinect to PC:

1. Connect the power supply for your Kinect to an external power source.

2. Connect the Kinect to a USB port on your PC and wait for Windows to recognize it.

3. All the drivers, including audio, will load seamlessly.

I think, order of steps 1 and 2 can make a difference.

I'm getting this problem as well. One Kinect is recognized, the other tells me to plug in the power (and of course it is plugged in). They're both recognized in Device Manager. I'm using the latest software 2.0.0.13. They're both Xbox Kinects. Any ideas?

I just tried it on two different computers, same issue. I reinstalled ipiRecorder version 1 and it works fine. I guess Microsoft wants us to buy MS Kinects to use their SDK? Is there any confirmation that this might fix the problem?

Hi
As I can remember, there were no reports about this issue from Kinect for Windows users. However, I cannot say for sure that they have no this issue at all. Most of our users have Kinects for XBOX and they are working normal with the new version.
I only may suppose that there is some little "defect" in particular instances of Kinects that had no effect with Kinect SDK 1.0, and started failing with Kinect SDK 1.5 (which is used by Recorder v2). Try switching to PrimeSense drivers instead of Kinect SDK.