OS X Lion+MAX 5+OpenNI+OSCeleton INFO
Hello everyone some information about OS X Lion+MAX 5+OpenNI+OSCeleton.
I work on a Mac Mini Core 2 Duo 2.4Ghz 8GB and OS X Lion.
The latest CMake update works perfectly with OS X Lion and MAX 5.
The latest MacPorts update works perfectly with OS X Lion and MAX 5.
The latest OpenNI update works perfectly with OS X Lion and MAX 5.
OpenNI Unstable Build for MacOSX 10.6 Universal x86/x64 (32/64-bit) v188.8.131.52
PrimeSense NITE Unstable Build for MacOSX 10.6 Universal x86/x64 (32/64-bit) v184.108.40.206
Another information for option outputs !the joint rotation data! you will find here :
OSCeleton uses 26% CPU on my MAC Mini.
I just realize that by writing I have not yet installed the update avin2/SensorKinect
but the old avin2/SensorKinect works well.
I hope this information will help you
Ok with the update avin2-SensorKinect-2d13967
good to know! thanks!
argh, this has not been smooth, Lion broke OSCeleton and all it’s dependencies… re-install has been painful and OSCeleton is hanging and not recognizing new users. Jit.freenect.grab also appears to break under Lion.
One workaround… possibbly… Synapse: Works way better than OSCeleton on 10.6 at least: http://synapsekinect.tumblr.com/post/6305020721/download
that looks great! though it doesn’t appear that it can output joint rotation matrixes as the new OSCeleton does. Certainly looks far easier to install if you’ve never set things up the old way (which is torture even if you’ve done it before)
Anyway I reverted to SL from a backup and everything seems to be fine again (a 24 hour mistake I will not soon make again)
* Of note it appears it is only the latest build of Max that kills jit.freenect.grab not Lion specifically
@LLT Did you have any problem with ONI file record or playback? Everytime I try to save a ONI file, I have Segmentation Fault: 11 error. And when I try to play a ONI (using the arg -i) I have the error: "Initializing…
There was a problem initializing kinect… Make sure you have connected both usb and power cables and that the driver and OpenNI framework are correctly installed."