Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- PatrickRyan001 March 2015
- shiffman March 2015
Open-Kinect Kinect V2 and Kinect for Xbox One.
Hi I'm in the process of finishing up my proposal and i had a few more questions. I want to add support for the newer Kinect using Libfreenect2. I think processing is eventually going to need support for the newer Kinect as the old one was recently discontinued. The newer version is a lot more powerful. I think it would be exciting and beneficial to the processing community to be able to use the newer Kinect.
Libfreenect2 is not backwards compatible with the old Kinect, but the API calls look really similar. I think i could use some of the code from the original Open-Kinect for processing. My first question is should I propose to make separate library or extend Open-Kinect?
Libfreenect2 doesn't have a clean java wrapper like its prior version, but i can use JNA to bridge the c API already created. I think the work would be minimal but I'm worried that would be working to far away from processing. My intent is to make the new Kinects available to processing users without the windows SDK on any operating system. Is this to much work not directly with processing even though the end result is for processing?
The main features i want users to be able to retrieve are an RGB, IR, and Depth Image. OpenNI2 works on the kinect V2 with the sdk and i recently found a fork that allows it to function with Libfreenect2. Should i focus purely on Open-Kinect?
Sorry for the late questions, I've been trying to get a good feel for libfreenect and libfreenect2.
Comments
From my standpoint, a good goal for Processing is easy cross-platform access from one library to depth, RGB, and IR images from as many kinects as possible. The Open Kinect library (build on the original libfreenect) is a good reference, but in some ways it needs to started over from scratch since so much has changed. I agree JNA is a good path. I believe that this work fits the scope of GSOC well.
https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/pjryan/5629499534213120