Strong Contender Already For Adafruit's Kinect Challenge
sammyF70 writes "Adafruit's bounty on open source drivers for Microsoft's Kinect may have been already won. Someone called 'KinectMan2' has posted videos of Kinect's output as seen on Windows 7 to YouTube. That was fast. Hopefully Linux drivers are coming soon."
A few more details are available on a forum post the man made. Adafruit said the bounty could be his if he posts the source code, and they also upped the reward to $3,000 in response to another silly statement from Microsoft.
The internal OS is WinCE, so the interface is either serial or USB.
Beyond that, there isn't much to it besides identifying the commands and responses. MS isn't particularly deft in hiding their protocols.
Microsoft issued a pretty nasty response the last time this was posted in the public. That could have... helped.
There is an article on engadget that says the guy doesn't necessarily want to publish his driver :
http://www.engadget.com/2010/11/07/kinect-does-hackers-bidding-but-not-for-fortune-or-fame-video/
Maybe that's why the bounty was raised.
The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
I have a more generic question: I have written a few old style drivers for DOS, some USB drivers for Windows using LibUsb and I'm working on some more complex Linux driver. But that was on devices that we designed and whose specs I knew. Now I have a monitor calibration device I'd like to get working on Linux. I don't expect the driver to be very complicated (it's just a color sensor), but I have no idea how to get started without specs. Is it possible to intercept the USB communications while the device runs in VirtualBox for instance ?
Non-Linux Penguins ?
Not only is it legal but they should provide the source code and schematics to help!
All they have to do, is keep sending these messages, pushing the bounty up higher and higher until it bankrupts Adafruit. (And maybe then release their own driver and cash in on the bounty, or are they excluded from the contest?)
But that report is from July 2009 and only has sales figures through March 2009. I've played with this gadget, its taken the Xbox away from me and given it to my wife and kids.
Stop being an attention whoring second rate electronics kit seller for third rate geeks and build your own damn hardware. You have a moderately bright staff and you're wasting resources on tacky PR.
Stallman's had it right from the start: unless you must, don't tie yourself into something someone else has built and doesn't want to share. This applies as much for hardware, protocols and interfaces as for code proper.
I mean really, there is a video showing a Microsoft product interacting with a Microsoft OS. So basicly we have an open-source-endorsing company paying for something that will only benefit Microsoft. Why can't they give the money to someone who makes a good game (or something else) for Linux?
PlusFive Slashdot reader for Android. Can post comments.
hah now the bounty is 10k which is about right for a good driver
http://nuigc.com/johny5
Hey, Microsoft, this is all this "hack" will likely ever be: figuring out the protocol and encryption so that the device can be used with any computer. Hardware modification would make it much less usable to people, so it's unlikely.
But this is very interesting, as the above statement from Microsoft could probably used as a defense when Microsoft inevitably sues people once an open-source driver is released. "But your honor, Microsoft itself stated that this is not a hack, in any way!"
I get the feeling that Microsoft's real target is not those writing a driver, but investors and developers for whom an open-source driver is a threat. Apparently this device is being sold near cost, or even lower, in order to help establish it in homes so that game developers will use it. If its protocol were unlocked, then Microsoft might have to raise its price, which would lower sales and thus reduce the number that go into homes.
it does look promising but it has me wondering if it's real since they have what Adafruit required in functionality but want an extra $7k($3k+$7k=$10k) to release the code and documentation. The original designer of the Kinect device technology( PrimeSense ) provides an SDK and DDK to work with it's reference design. What's to say what we're seeing in this video is not the PrimeSense SDK and driver and not a hack of the Microsoft Kinect USB data streams?
It could be real but it has my antenna up wondering how real it is. If PrimeSense didn't create the design and Microsoft did, then I'd be less prone to question this but we all know that the Kinect is a PrimeSense product with Microsoft's tweaking. It would be great if Microsoft did not encrypt or munge the USB data and it is to the original PrimeSense ref spec since PrimeSense is probably more inclined to want to sell chips and license the design as opposed to wanting to limit sales and tie sales to only one other device.
So show us that the supposed demo of Kinect's output is really from custom made software and not something either pulled from Microsoft or PrimeSense. Show us you're not just using their code to get $10K to do the real work of creating something which can be open sourced.
LoB
"Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
From what I can tell it seems that there are two versions of the Kinect. One version is designed for people who already own an Xbox 360 and are buying the Kinect to add to it. That version requires a separate power supply and (presumably) has a standard USB port. The other version comes with the new 360 Slim/Kinect bundle. That version does not require a separate power supply - it gets its power from some kind of special port on the back of the new Xbox that kinda-sorta looks roughly like a USB port but is clearly different.
I wonder if the driver will be the same for both? At first, no doubt the drivers will be designed for the sold-separately Kinect, but as time goes on and more bundles are sold, more people will have the version with the special connector.
I wonder if that was a kindness by Microsoft (so we don't need yet another Wall Wart), or a cost-saving measure (don't have to sjip power supplies), or a proprietary thing (using a special connector that no one else has in order to prevent this kind of reverse engineering). Probably some of all three.