Perhaps it seems strange posting this news here, but with my thirst to be cutting edge, to be dynamic with design.
I can see the future of being able to use a kinect in a installation which with the use of processing language and visuals we will be able to interact on a new level with the art we are viewing.. much more interactively than matt pikes Nokia, ambient media installations.
the Kinect is 150pound kit which is able to 3d map environments, on XYZ! it is able to perceive depth which has until now been impossible for the consumer market.
Originally developed by Israeli military technology, it was brought to the consumer market.
Apple wanted to tie this up in so much privacy and DMCA etc rights that the company who produced it then moved onto Microsoft. I CANT WAIT ONEDAY TILL THIS IS HACKED FULLY SO WE CAN PAINT, USE THEM IN INSTALLATION ART, AND INTERACTIVE DESIGN.
NEWS SO FAR WITH REGARD TO HACKED DRIVERS!
LibFreenect - Open Source PC Drivers for Kinect
>> Marcan released the first Open Source Drivers for Kinect:
[QUOTE]
Horribly hacky first take at a Kinect Camera driver. Does RGB and Depth.
main.c implements a simple OpenGL visualization. Hopefully it should be mostly self-explanatory... You pretty much just open the USB device, call cams_init(dev, depthimg, rgbimg), and your depthimg and rgbimg callbacks getcalled as libusb processes events.
TODO:
- TONS of cleanup. I mean LOTS.
- Proper buildsystem (CMake probably)
- Determine exactly what the inits do
- Bayer to RGB conversion that doesn't suck
- Integrate support for the servo and accelerometer (which have already been reverse engineered)
BIG TODO: audio. The audio chip (the Marvell) requires firmware and more init and does a TON of stuff including the crypto authentication to prove that it is an original Kinect and not a clone. Who knows what this thing does to the incoming audio. This should be interesting to look at.[/QUOTE]
[QUOTE]
Horribly hacky first take at a Kinect Camera driver. Does RGB and Depth.
main.c implements a simple OpenGL visualization. Hopefully it should be mostly self-explanatory... You pretty much just open the USB device, call cams_init(dev, depthimg, rgbimg), and your depthimg and rgbimg callbacks getcalled as libusb processes events.
TODO:
- TONS of cleanup. I mean LOTS.
- Proper buildsystem (CMake probably)
- Determine exactly what the inits do
- Bayer to RGB conversion that doesn't suck
- Integrate support for the servo and accelerometer (which have already been reverse engineered)
BIG TODO: audio. The audio chip (the Marvell) requires firmware and more init and does a TON of stuff including the crypto authentication to prove that it is an original Kinect and not a clone. Who knows what this thing does to the incoming audio. This should be interesting to look at.[/QUOTE]
No comments:
Post a Comment