T
TopGun53786
Guest
With all the distance learning stuff, i figured my old kinect would work great as a 1080p webcam for Zoom sessions. Issue is, it refuses to send any kind of visual data to apps beyond the applications included in the kinect SDK.
Now, it is manually modified to send the required 12v through a 12v 3a power brick directly to the PCB rather than shelling out for the official adapter, but i made certain that all the connections are solid, electrically isolated from one another, connected safely through plugs, and that no excess heat was put into the board, and the data connection is done with a USB 3.0 type A to USB 3.0 type B cord. I'm fairly confident i didn't damage it in this process, as if i run the Kinect Configuration Verifier or Kinect Studio v2.0, everything works fine. I click the button to connect, and color 1080p, depth, IR, body, you name it, it works. But if i try to use any other app, i.e. camera app, discord, zoom, windows hello, etc., it "connects", but either buffers forever or displays a black screen. 3D scan says "Initializing sensor" in the corner forever. Thanks to updating the driver in an earlier step, though, they at least recognize the Kinect by name, for example the camera app recognizes it as "Kinect V2 Video Sensor" with the correct quality of 1080p 30fps.
The Kinect Configuration Verifier runs mostly fine with everything getting a checkmark except:
-"Update Configuration Definitions" returned "Failed to update, using last known good definitions"
-"USB Controller" returned "Unknown USB 3.0 port detected. Your USB configuration may support Kinect for Windows"
I've searched as much as i can to fix it from other posts online, among the things i've tried:
I can't for the life of me figure out what's going wrong, since Kinect Studio V2 clearly shows me that my kinect is both successfully communicating with my machine, as well as successfully sending color video, depth video, and IR video at the full 30 fps.
A few extra things to note:
I've exhausted all the options i can think of, so you guys are my last hope to get it working - any help would be greatly appreciated!
Continue reading...
Now, it is manually modified to send the required 12v through a 12v 3a power brick directly to the PCB rather than shelling out for the official adapter, but i made certain that all the connections are solid, electrically isolated from one another, connected safely through plugs, and that no excess heat was put into the board, and the data connection is done with a USB 3.0 type A to USB 3.0 type B cord. I'm fairly confident i didn't damage it in this process, as if i run the Kinect Configuration Verifier or Kinect Studio v2.0, everything works fine. I click the button to connect, and color 1080p, depth, IR, body, you name it, it works. But if i try to use any other app, i.e. camera app, discord, zoom, windows hello, etc., it "connects", but either buffers forever or displays a black screen. 3D scan says "Initializing sensor" in the corner forever. Thanks to updating the driver in an earlier step, though, they at least recognize the Kinect by name, for example the camera app recognizes it as "Kinect V2 Video Sensor" with the correct quality of 1080p 30fps.
The Kinect Configuration Verifier runs mostly fine with everything getting a checkmark except:
-"Update Configuration Definitions" returned "Failed to update, using last known good definitions"
-"USB Controller" returned "Unknown USB 3.0 port detected. Your USB configuration may support Kinect for Windows"
I've searched as much as i can to fix it from other posts online, among the things i've tried:
-Updated WDF KinectSensor Interface 0 driver to 2.2.1905.16000
-Checked that it is connected to an intel USB controller (selecting Xbox NUI Sensor and going to View>Devices by connection shows it as being under "Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)")
-Updated windows from the "windows update" tab in settings
-Forced it to use my 1080ti in Nvidia Control Panel
-Tried a variety of apps, including online webcam testing sites, one of which showed an odd static for some reason
-Installed KinectSDK v2.0_1409
-Tried all ports on my machine (only the front two work, which i assume to be the only ones using the intel controller)
-Made sure to enable webcam access for any apps i wanted to test in windows privacy settings
I can't for the life of me figure out what's going wrong, since Kinect Studio V2 clearly shows me that my kinect is both successfully communicating with my machine, as well as successfully sending color video, depth video, and IR video at the full 30 fps.
A few extra things to note:
-Audio works perfectly EVERYWHERE, unlike video, so i can open up audacity or discord and use the kinect's mic perfectly fine
-I'm running on an SSD with an i7-8700k, 1080ti, 32GB RAM, on an ASUS ROG Strix Z370-E board
-I also tried using it on my laptop, but the same thing happens - works in Kinect Studio, but nowhere else
-I restarted my pc several times throughout troubleshooting to see if it helped, as well as again before starting this post
-I'm running three monitors at the moment, and i found that if any of them are not set to 60hz, the kinect will run choppily at a couple frames per second in Kinect Studio. Found this out when it worked fine (in K studio) on my laptop, but not my desktop which has a 144hz monitor
I've exhausted all the options i can think of, so you guys are my last hope to get it working - any help would be greatly appreciated!
Continue reading...