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

OpenKinect does not work

Open Dhammikalks opened this issue 9 years ago • 8 comments

I am new to kinect and I am using kinect 1414 model on windows 8 ,processing 3 Every time I run open kinect for processing on windows 8 Bellow error message is print out on console "64 windows There are no kinects, returning null Could not open camera: -12 Failed to open camera subdevice or it is not disabled.Failed to open motor subddevice or it is not disabled.Failed to open audio subdevice or it is not disabled."

Still my kinect 1414 is working on windows kinect Studio

Dhammikalks avatar Jan 21 '16 14:01 Dhammikalks

for windows you need to install the lubusbZ drivers via zadig

https://github.com/shiffman/OpenKinect-for-Processing#windows

https://github.com/OpenKinect/libfreenect#windows

ThomasLengeling avatar Jan 22 '16 10:01 ThomasLengeling

i installed lubusbZ drivers also but my porblem is same

Dhammikalks avatar Jan 23 '16 01:01 Dhammikalks

if the kinect is still working on the kinect studio that means that you haven't correctly installed the liibusbZ drivers.

ThomasLengeling avatar Jan 23 '16 11:01 ThomasLengeling

yes now it is not working with kinect studio but also the still error message is same also on drivers list only Kinect USB Audio and Xbox Nui Motor appeared as connected drivers

Dhammikalks avatar Jan 31 '16 03:01 Dhammikalks

I have also issues with Openkinect. Working with kinect 1414 with Processing 3 on MAC OSX. AveragePointTracking, DepthThreshold working fine most of the time but sometimes I get these errors: Could not claim interface on camera: -3 Failed to open camera subdevice or it is not disabled.Failed to open motor subddevice or it is not disabled.Failed to open audio subdevice or it is not disabled.There are no kinects, returning null

MultiKinect (tested with just one device) working with no errors untill I press 'i' key for options, then I get these messages from the console: [Stream 70] Expected 1748 data bytes, but got 948 [Stream 70] Expected 1748 data bytes, but got 948 [Stream 70] Expected 1132 data bytes, but got 316

PointCloud working randomly; sometimes I got the following error message: send_cmd: Bad len 0004 != 000c freenect_fetch_reg_pad_info: send_cmd read -1 bytes (expected 8) freenect_camera_init(): Failed to fetch registration pad info for device There are no kinects, returning null

RGBDepthTest often I get several random different error messages. Most of the time the following 2: 1) java.lang.IndexOutOfBoundsException at java.nio.Buffer.checkIndex(Buffer.java:540) at java.nio.DirectByteBuffer.get(DirectByteBuffer.java:253) at org.openkinect.processing.RGBImage.data(Unknown Source) at org.openkinect.processing.Kinect$2.onFrameReceived(Unknown Source) at org.openkinect.freenect.Freenect$NativeDevice$1.callback(Unknown Source) at org.openkinect.freenect.Freenect.freenect_process_events(Native Method) at org.openkinect.freenect.Freenect.access$500(Unknown Source) at org.openkinect.freenect.Freenect$EventThread.run(Unknown Source) Could not run the sketch (Target VM failed to initialize). For more information, read revisions.txt and Help → Troubleshooting. 2) Could not claim interface on camera: -3 Failed to open camera subdevice or it is not disabled.Failed to open motor subddevice or it is not disabled.Failed to open audio subdevice or it is not disabled.There are no kinects, returning null

PointCloudOGL got the following error message: The method vertexAttribPointer(intm int, boolean, int, int) in the type PGL is not applicable for the arguments (int, int, int, boolean, int, FloatBuffer)

SetupandDraw avatar Mar 21 '16 10:03 SetupandDraw

Did you ever get this error resolved?

The method vertexAttribPointer(intm int, boolean, int, int) in the type PGL is not applicable for the arguments (int, int, int, boolean, int, FloatBuffer).

I also get it when I try to run this: DepthPointCloud2

zhannar avatar Jun 02 '16 00:06 zhannar

getting same issue .. anyone resolved this ?

AbdullahAslam avatar Mar 28 '17 06:03 AbdullahAslam

The method vertexAttribPointer(intm int, boolean, int, int) in the type PGL is not applicable for the arguments (int, int, int, boolean, int, FloatBuffer)

is solved by changing pgl.vertexAttribPointer(vertLoc, 3, PGL.FLOAT, false, 0, depthPositions); to pgl.vertexAttribPointer(vertLoc, 3, PGL.FLOAT, false, Float.BYTES * 3, 0 );

jango-fx avatar Mar 31 '17 09:03 jango-fx