Hacker News Reader

All we need now is a more responsive kinect.

As a proof of concept this kind of interface is fine but for real use it's slow and unresponsive.

Isn't the latency experienced with the games arising in software (the algorithms running on the xbox, not the Kinect itself)?

According to the web, "The depth sensor uses a monochrome image sensor. Looking at the signals from the sensor, resolution appears to be 1200x960 pixels at a framerate of 30Hz." It would perhaps be better to be able to run it at a lower resolution and a higher framerate; maybe it's possible. Processing 35M pixels per second does sound like something that could use up a CPU cycle or two. It also sounds like something that OpenCL would be good at handling, doesn't it?

http://openkinect.org/wiki/Hardware_info

My guess would be that the high resolution is required to interpret the IR pattern at the maximum distance supported by the kinect (tens of feet). I'm wondering if the 30Hz is a limitation of the camera sensor or the pattern matching.

Reply on news.ycombinator.com