OpenKinect-for-Processing icon indicating copy to clipboard operation
OpenKinect-for-Processing copied to clipboard

There are no kinects, returning null

Open Michelleyaooooo opened this issue 7 years ago • 7 comments

Hi there,

I'm currently working on the OpenKinect-for-Processing library according to Daniel's tutorial. But I can't get the Kinect connected. Here's the error log in the console when running the point cloud from the library example:

Found path: /Users/MichelleYAO/Documents/Processing/libraries/openkinect_processing/library/v1/mac/ Loaded freenect from /Users/MichelleYAO/Documents/Processing/libraries/openkinect_processing/library/v1/mac/libfreenect.dylib No Kinect devices found. Failed to open camera subdevice or it is not disabled.Failed to open audio subdevice or it is not disabled.There are no kinects, returning null

I'm using a Mac OSX Serria (10.12.6) and my processing is 3.3.6. Hardware: Kinect v1 (1414)

I've browsed through all possible solutions on Github and Processing Forum, tried (1)unplug and plug again for a thousand times (2)Try it on another computer

There's other comments mentioned about USB 3.0 and 2.0. But not sure what it means since the mac I use only has USB3.0. I could found the device through system report(see the pic attached). For my laptop, I connected the Kinect with a power cable and a USB cable.

Please help;( Thank you so much in advance screen shot 2018-03-13 at 17 39 03

Michelleyaooooo avatar Mar 14 '18 00:03 Michelleyaooooo

Try with this SimpleOpenni

totovr avatar Mar 15 '18 11:03 totovr

I tried it;( Still not working. But it works when I changed to Kinect v2.

Michelleyaooooo avatar Mar 26 '18 17:03 Michelleyaooooo

same problem here with kinect 1414, what can i try?

marcoctn avatar Jun 18 '18 09:06 marcoctn

same problem, with kinect 1414 in a Raspberry Pi 3

BrunoLerner avatar Oct 04 '18 22:10 BrunoLerner

Same problem with a 1414 on MacOS Mojave 10.14.3, I see the same thing in System Report, and get the same message in Processing

jasonamri avatar Mar 12 '19 04:03 jasonamri

I had the same problem. I got it to work by uninstalling the Microsoft Kinect SDK and the Microsoft Kinect drivers. Used Zadig instead.

hamiltonbelinda0 avatar Feb 02 '20 19:02 hamiltonbelinda0

I had the same problem. I got it to work by uninstalling the Microsoft Kinect SDK and the Microsoft Kinect drivers. Used Zadig instead.

Bismillah,..

Its Working I thank you for it, and pray that God will bless you.

MuhammadAgni avatar Sep 30 '20 14:09 MuhammadAgni