I’ve built a FTRI set up, with infra red LED’s and tested them in mtMini and tbeta. I’ve got them configured and working in tbeta, so I know I can pick up blobs effectively (See video: http://www.youtube.com/watch?v=VbP2PWR66Is)
I can compile and run any of the examples in openframeworks through codeblocks. But when I do if I touch the compliant surface, I don’t get any interaction inside the example application. I’ve read the FAQ’s, wiki and these forums, but I can’t figure out what I’m missing.
If anyone could explain, in basic terms, how the interfacing between camera and software work (Merely in terms of configuration, e.g. how does the program know what is a blob and what is just noise?) that would be great.
Specs:
Webcam: 8megapixel webcam, infra red filter applied, (USB 2.0)
**Software: **Code:Blocks with Openframeworks (Compiles and runs fine) Hardware: FTRI (See: http://www.flickr.com/photos/34918513@N06/, acrylic, compliant surface=sulky solvy.
Unless you want to write your own blob tracking code, you can use tbeta for this task. Just keep it running and make sure to tick the box to send tuio messages.
To receive these messages in a OF project, you will need the ofxTuio addon (http://addons.openframeworks.cc/projects/show/ofxtuio) and the ofxOsc addon (latest version here http://frey.co.nz/projects/ofxosc). The latest tuio addon (0.2) uses Poco to handle event callbacks. If you want to use it, you will have to upgrade OF to the 0.573 version, which I would probably recommend (this is the route I have taken).
Finally you can use the example program packaged with ofxTuio as a template for your own program. By doing this, you will have abstracted all the hard work, and will ony be dealing with 3 function callbacks triggered when a blob appears, when it is updated and finally when it is lost.
Unless you want to write your own blob tracking code, you can use tbeta for this task. Just keep it running and make sure to tick the box to send tuio messages.
To receive these messages in a OF project, you will need the ofxTuio addon (http://addons.openframeworks.cc/projects/show/ofxtuio) and the ofxOsc addon (latest version here http://frey.co.nz/projects/ofxosc). The latest tuio addon (0.2) uses Poco to handle event callbacks. If you want to use it, you will have to upgrade OF to the 0.573 version, which I would probably recommend (this is the route I have taken).
Finally you can use the example program packaged with ofxTuio as a template for your own program. By doing this, you will have abstracted all the hard work, and will ony be dealing with 3 function callbacks triggered when a blob appears, when it is updated and finally when it is lost.
I currently use the 0.2 version of ofxTuio in combination with the 0.3 version of ofxOsc (again note this requires you to use version 0.573 of OF). If you go this route, you might have the compiler complain about a series of functions receiving string objects where char arrays are expected. I just appended a “.c_str()” to these strings to solve the problem.
I’ll try out the alterations to the files tomorrow. It could always be an OF issue with regards to version number. Once I find the 573 version I’ll try a new build. I do have version _5 but it doesn’t give me the minor and increment version numbers to do a full comparison.
it should’nt be too difficult to extend the ofxTuio example. The hard work is done by the addons.
You should only concern yourself with the events called in the “tuioDown”, “tuioMoved” and “tuioUp” functions. They behave similarly to mouse events (mousePressed, mouseDragged and mouseReleased). If you have existing examples relying on mouse input, it should be possible to adapt them to the Tuio input.