All geek questions in one place

Kinect engine control through processing

I am hacking Kinect with some simple openni-based applications for the discussion that I am planning in the near future, and I have found an API that seems to control the engine. There is a moveKinect method that seems to be added to the main ContextWrapper interface, but I can't get it to work. Looking through svn history and release notes, it seems to have been added last year with a note explaining that it does not work with the latest drivers (5.1.02, Linux64). I tried calling a method giving it values ​​in degress and radians, but nothing happens. I have no mistake and no movement. Has anyone else played with this? I work from the second to the latest version 2.0 (the link to processing 2.0.1 does not work) and the last SImpleOpenNI package that I could download.

+4
source share
1 answer

SimpleOpenNI is an OpenNI shell that provides access to RGB / IR / Depth streams and middleware for body / arm detection, but does not allow access to hardware such as an LED, accelerometer, or motor.

You should try Kinect P5 , which uses libfreenect behind the scenes and supports engine management. It doesn’t matter that you don’t have middleware support.

If you need both middleware and access to hardware, you can try OpenFrameworks with ofxOpenNI . It has a hardware class that runs on OSX and Linux (like sudo), allowing you to use both middleware and the engine.

0
source

Source: https://habr.com/ru/post/1487917/

More articles:


All Articles