Re: [Video] Alternative Kinect Control (using depth images)
Posted: Tue Jul 08, 2014 5:36 am
Thanks Veer for your comments! Im going to recode most of it in c++ to get rid of that latency. I just moved to the US and dont have a kinect yet, so it might take some days for me to get started. I couldnt get it working in IR light rich envirnments either. I wanted to measure the detection accuracy using a motion capture system..but no change. Too much IR reflection. Let me know if oyu think any new features should be added before i start implementing the c++ version.Veerachart wrote:Some more investigations showed me that trying to do screencast uses quite considerable resources and cause some delays. Without doing that (and a little bit modification on numpy matrix manipulations - not sure how much this helps), I experience the delay less; most of the time no problem, but sometimes it just comes out of nowhere.
About the detection size: for my case I start using the Kinect to control the flie since taking off. To make it detectable, I have to put a box on the floor as the take-off stand, so that the difference from the background is large enough. Also in my case, the detected size is smaller when the flie is on the box, as the part closer to the box has too small difference to be detected. Setting wider range of detection size already solved this problem (or at least seems so.) (I also found a little problem with part of my lab's wall, that it somehow reflects the IR light weirdly, causing too much noise which are around the same size as the flie, so they got detected. Anyway, I solved this by using partitions to block those materials and everything comes to a peaceful state )
Changing from freenect to OpenNI also works well, just need to change rosdep in the manifest file.
Cheers