The SKT 1.2 binaries are working great so far on windows 7 (64 bit)! I just had to copy the msvcr100d.dll file to the same directory in which the SKT-1.2.exe is located and everything ran smoothly!
Any tips about how and where to locate the kinect in order to get good tracking results? I noticed than when I place the kinect very close to the surface (less than 50 cms or 1.5 feet) it doesn’t track my fingers, at which distance from the surface do you think the kinect tracks best with SKT?.
Does SKT tracks better when the kinect camera/projector points perpendicularly to the surface? or it can be placed at any angle?
Hi Fike, Thanks for the feedback!, on this page you can find some details on calibration : http://code.google.com/p/simple-kinect-touch/ . Hope you can access now. If you can’t let me know and I’ll put it here.
The distance depends on the surface size. Probably the best is the closest that allows the Kinect to see the hole area you will be using, but less than 50 cm is not possible because Kinect doesn’t give distance data that close.
Perpendicular is simpler and easier to calibrate, but by changing the parameters you can make another directions work very good as well.
Hi, I have the following issue with SKT windows binaries (command line output):
Desk : 1920,1080 Screen : 1920,1080
Parameter file: settings.xml - not found. Using default values.
Host : localhost Port : 3333
init done opengl support available Kinect opening ... done.
FPS Given by Device : 0
Could not open the device.
At the same time OpenNI work fine. Any thoughts about it? Is it avin2 driver’s problem or something else?
Hi 3dmark, did you tried the suggestions we gave in the google group? ( http://groups.google.com/group/simple-kinect-touch/browse_frm/thread/20844f0a19be2cd ) If you did please send the details. That output is for a failed connection with the device. If the NiViewer sample works SKT should work… so we need a bit more info for it would be the first time that one works and the other doesn’t. Regards.
Thanks for your reply, NZRock.
The case is that NiViewer and other OpenNI samples works properly so i’m sure kinect is connected correctly.
I finally got to get SKT to work and i think it was some kind of “x86-x64 conflict” cause i had both OpenNI-x86 and OpenNI-x64 installed (on 64-bit OS). I removed them and installed only 64-bit version and it solved the problem.
By the way on the other machine, which had MS SDK, I’ve got the same error as vNakamura on google group topic from your link.
But uninstalling SDK and reinstalling avin driver didnt’t solved it for me :\
Good to know you made it work!. Strange about the conflict but I guess OpenCV might get confused with two versions (using a different version of avin2 than openni).
On the windows machine that had the Microsoft SDK, NiViewer also works?
Yes, NiViewer works with MS SDK installed and without it..
I’ve compiled SKT-1.4 from sources on that machine and got even more confused now
With that binaries I’m not getting an “OpenCV error ...”, but “Could not open the device” appears again
Hi 3dmark, good to know you made it work! strange about the other machine you said, don’t know what might be the problem… The only thing i can think might help is a complete removal of openni, avin2, microsoft sdk, libfreenect and primesensor (if you have them installed) and re-installation of openni and avin2 only. If that or any other thing you try works (or doesn’t) please keep us posted (so we can put it in troubleshooting and it might help others). good luck!
Hi again,
I’ve solved the problem by installing the 32-bit version of OpenNI, PrimeSence and Nite and complete removal of all its x64 components.
It seems to me the case is that the OpenCV doesn’t recognizes x64 libs by some reason.
Hi, thanks for the info!, it has just been included in the troubleshooting wiki of the google code page. Probably the problem is that the distributed version of OpenCV we included was compiled in a 32 bit machine with 32 bit OpenNi and Avin2.
We have uploaded a new version (2.0.1), with source rewritten and a couple of improvements (including the simplest direct mouse events for windows and linux, better calibration, etc...). We would be very happy to receive some feedback (bugs, ideas, etc...)
have fun!
