Kinect sensor not giving depth or rgb feedback

[Zach Davis]

Skanect detects my gpu and sensor, but once I get to the record tab, my sensor doesnt detect anything.  Nothing in the bounding box, and the 3 display windows are gray.  I am running the latest version of Skanect (v1.8.4) with a kinect 360 as a scanner and my gpu is a msi geforce gtx 1050 ti.  My Geforce Game Ready driver is up to date and I am using the kinect for windows v1.8 drivers.  I am getting 3 warnings in my log file

warning 1: Cant' determine number of cores. Unknown SM version 6.1!

warning 2: Kinect for windows: could not set near mode

warning 3: Kinect for windows: must be an Xbox kinect

CUDA is still pretty foreign to me.  Is there another driver for CUDA that I need to install?  The only thing I can find is the CUDA driver tool kit, but that seems to be for developers.....


Everything worked fine for the most part with my old GPU, but I was getting really low framerates (under 10fps) so I purchased the new gpu and now I have this problem.  Any help would be much appreciated, as setting Skanect and other 3D scanning softwares up is apparently the hardest thing to do in the world.


Here is my full log file:




INFO: Starting Skanect 1.8.4 (64 bits)
INFO: Configuration file: C:/Users/Haywire/AppData/Roaming/ManCTL/Skanect.ini
INFO: License configuration file: C:/Users/Haywire/AppData/Roaming/ManCTL/SkanectLicense.ini
INFO: Number of CUDA devices: 1
INFO: Device 0:  "GeForce GTX 1050 Ti"  3726Mb / 4096Mb
WARNING: Can't determine number of cores. Unknown SM version 6.1!
INFO: Device 0: sm_61, 0 cores
INFO: Device 0: Driver/Runtime ver.8.0/8.0
INFO: CUDA major: 6
INFO: CUDA GeForce GTX 1050 Ti, global memory: 4096M
INFO: CUDA device specs seem ok.
INFO: Could instanciate a GPU fusion successfully.
INFO: License type: FREE
WARNING: Can't determine number of cores. Unknown SM version 6.1!
INFO: No support for Kinect One SDK.
INFO: Initializing Kin4Win driver

INFO: Number of Kinect for Windows devices found: 1.
INFO: OpenNI2: Number of devices: 0
INFO: No support for softkinetic, skipping.
INFO: [Kinect 5fb2c40] connecting

INFO: Kinect for Windows: initialized successfully

INFO: Kinect for Windows: color stream opened.

INFO: Kinect for Windows: depth stream opened.

WARNING: Kinect for Windows: could not set near mode

WARNING: Kinect for Windows: must be an Xbox Kinect.

INFO: Kinect for Windows: flags set.

[Nicolas Burrus]

Hi Zach,

GTX 10xx support will come soon with Skanect 1.9. The Kinect for Xbox warnings are expected if you are indeed using a Kinect for Xbox 360 and not a Kinect for Windows.

--
You received this message because you are subscribed to the Google Groups "Skanect" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skanect+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Zach Davis]

Hey Nicolas, thanks for your reply. I could definitely be wrong on both of these as I can't find any documentation from skanect, but I saw on the forums that v1.8.4 should have support for the 10xx series? Perhaps it's limited?/ also, gpu aside, shouldnt I at least be able to get feedback through the cpu recording feedback setting g, or does it require a supported gpu for that too?

[Nicolas Burrus]

Sorry I answered too fast, the GTX 1050 should indeed already be supported by 1.8.4 indeed, even if the log says that it could not find out the number of cores. The log file still says that it could instantiate a GPU fusion, so everything should work properly.

Are not not seeing any depth/color feed in the Record tab?

Are you able to run any sample from the Microsoft Kinect for Windows drivers? Maybe try other USB ports for the Kinect?

On Mon, Feb 13, 2017 at 2:22 PM, Zach Davis <musicly...@gmail.com> wrote:

Hey Nicolas, thanks for your reply. I could definitely be wrong on both of these as I can't find any documentation from skanect, but I saw on the forums that v1.8.4 should have support for the 10xx series? Perhaps it's limited?/ also, gpu aside, shouldnt I at least be able to get feedback through the cpu recording feedback setting g, or does it require a supported gpu for that too?

[Zach Davis]

I am not seeing a depth or color feed in the record tab. I am also not seeing anything within the bounding box. I would assume they are both related to the same problem. If I try to record anyway, it doesn't have anything to record.
I have tried different USB ports and the kinect is connected to the wall outlet.
Are you referring to different driver versions of the kinect sdk? I have tried v1.7 and v1.8. Both have the same issue. I think I should also note that under device manager, it shows up as kinect for Windows as opposed to primesense.

[Nicolas Burrus]

I was referring to testing something like Kinect Studio, one of the apps that come with the Kinect for Windows 1.8 SDK.If the Microsoft app is able to stream, then we should be too. Did you install the Kinect for Windows 1.8 SDK from our link http://download.microsoft.com/download/E/1/D/E1DEC243-0389-4A23-87BF-F47DE869FC1A/KinectSDK-v1.8-Setup.exe ? Please also remove any primesense driver first, as they might conflict.

[Zach Davis]

I am using the kinect for Windows v1.8 sdk drivers and there isn't anything showing up as primesense in device manager, just kinect for windows.
I ran kinect studio, connected to skanect, and in KS, I get an rgb feed, but the other two boxes are still empty. The live feed has a low frame rate, but clear image. When I record, it appears the frame rate improves quite a bit, but still a little choppy. When I stop the recording in KS, I noticed that what I had just recorded gets outputted to Skanect's rgb feed box. It doesn't activate the ability to record though. If I start a new project in skanect, the last frame of the recordING is all that I see under the record tab. If I close skanect and re open it, everything goes back to no feed whatsoever, basically where I started with the problem.

[Nicolas Burrus]

Could you try the Kinect on another computer? It almost looks like a hardware issue at this stage, if even Kinect Studio cannot stream depth.

On Wed, Feb 15, 2017 at 5:51 PM, Zach Davis <musicly...@gmail.com> wrote:

I am using the kinect for Windows v1.8 sdk drivers and there isn't anything showing up as primesense in device manager, just kinect for windows.
I ran kinect studio, connected to skanect, and in KS, I get an rgb feed, but the other two boxes are still empty. The live feed has a low frame rate, but clear image. When I record, it appears the frame rate improves quite a bit, but still a little choppy. When I stop the recording in KS, I noticed that what I had just recorded gets outputted to Skanect's rgb feed box. It doesn't activate the ability to record though. If I start a new project in skanect, the last frame of the recordING is all that I see under the record tab. If I close skanect and re open it, everything goes back to no feed whatsoever, basically where I started with the problem.

[Zach Davis]

I can give it a try, but I won't be able to get access to another computer that meets the system requirements until the weekend.
I can say that everything was working fine until I upgraded my gpu, but I was getting low fps and support said it was because of my gpu, so I upgraded and now I can't record at all. All of the hardware for my computer is new as of November 2016 too, with the exception of the gpu.
Before I go through the trouble of using my friends computer, he lives far away, can you tell me if the original geforce titan is supported? I would think it is, but just want to make sure because that is what he has.

[Nicolas Burrus]

The Titan should work with Skanect 1.8.4. But in any case you can test streaming on any machine, it does not have to meet the GPU requirements. You will see the live feed and will be able to do a CPU scan with live feedback quality set to medium or low. So to check if the sensor is working, you don't need a powerful computer.

[Zach Davis]

Ok, so I have identified the problem. I was using a usb extension cable and I guess it was messing with the signal. Plugging the kinect directly into the computers usb port fixed the problem. It is odd because I was using the extender with skanect before. I wonder what changed?