Here is the console output of an attempt to run the Recorder application in Sync, posted on the GitHub above:
ofxOpenNIDevice[0]: OF_LOG_WARNING: Using a NASTY hack to silence SIGNAL errors on exit - read the comments at line ~1712 of ofxOpenNI.cpp
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Init context...
ofxOpenNIDevice[0]: OF_VERBOSE: Context initilized status: OK
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Adding licence...
ofxOpenNIDevice[0]: OF_VERBOSE: Adding licence: PrimeSense 0KOIk2JeIBYClPWVnMoRKn5cdY4= status: OK
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Init device...
ofxOpenNIDevice[0]: OF_VERBOSE: Enumerate devices status: Can't create any node of the requested type!
ofxOpenNIDevice[0]: OF_LOG_WARNING: Device: PrimeSense/SensorKinect/5.1.0.25 failed: The device is not connected!
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Found 0 devices connected
ofxOpenNIDevice[0]: OF_LOG_WARNING: REAL Device could not be initialized - you can still use an ONI
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Starting ofxOpenNI with threading
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Adding generator type XN_NODE_TYPE_DEPTH
ofxOpenNIDevice[0]: OF_VERBOSE: Creating XN_NODE_TYPE_DEPTH generator status: Can't create any node of the requested type!
ofxOpenNIDevice[0]: OF_LOG_ERROR: setGeneratorResolution() called on invalid generator!
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Adding generator type XN_NODE_TYPE_IMAGE
ofxOpenNIDevice[0]: OF_VERBOSE: Creating XN_NODE_TYPE_IMAGE generator status: Can't create any node of the requested type!
ofxOpenNIDevice[0]: OF_LOG_ERROR: setGeneratorResolution() called on invalid generator!
ofxOpenNIDevice[0]: OF_VERBOSE: Depth generator is not on
ofxOpenNIDevice[0]: OF_LOG_NOTICE: Adding generator type XN_NODE_TYPE_USER
ofxOpenNIDevice[0]: OF_VERBOSE: Creating XN_NODE_TYPE_USER generator status: Can't create any node of the requested type!
ofxOpenNIDevice[0]: OF_VERBOSE: Starting XN_NODE_TYPE_USER generator status: Can't create any node of the requested type!
“On Mac OSX I’ve compiled the OpenNI, NITE and SensorKinect drivers and then modified the dylibs so they can sit in the bin/data/openni/libs folder. These are truly portable.”
Those instructions in your link are building/installing, not making dylibs. I can’t see how those instructions would replace multiple copies of myapp/data/openni/ for all of your projects.
You can also extract libusb-1.0.0.dylib via the Homebrew binary path.
Those instructions in your link are building/installing, not making dylibs.
Is wrong, they are for making dylibs.
Basically, the link I showed you before allows you to take advantage of all the new API features in the latest release - but these wouldn’t be cleanly exposed via the ofxOpenNI interface.