here is as far as i got (see file)
here are all the last infos i got from the TSPS maker
The messages are event based; so, to track each time something enters the field of view, listen for “TSPS/personEntered/”; to listen for objects as they move (which is I think what you’re going to want), listen for “TSPS/personMoved/”. Did you see the parameters in the src? The OSC message is structured like this:
0 - int - blob ID
1 - int - blob age
2 - float - blob center x
3 - float - blob center y
4 - float - blob velocity x
5 - float - blob velocity y
6 - float - blob bounding rectangle x (e.g. the top left corner of the blob)
7 - float - blob bounding rectangle y
8 - float - blob bounding rectangle width
9 - float - blob bounding rectangle height
10 - float - average optical flow at center x
11 - float - average optical flow at center y
if you are sending contours, the rest of the osc message is filled with contour
arguments, starting at message12 + message13 and continuing until the end
12 - float - contour0 x
13 - float - contour0 y
…
hope that helps! basically, what we’ve done in the examples is a process like this:
1 - create an array to put TSPSPerson objects in
2 - listen for “TSPS/personEntered/” to add a new object to the array
- keep track of the blob ID, x and y, etc
3 - listen for "TSPS/personMoved/ to update your objects
- look them up in the array via their IDs
4 - listen for “TSPS/personWillLeave/” to delete objects from the array
edit: you can change the OSC host + port if you’re having troubles. these variables are in the “communication” tab. here, you must set the IP address to the IP of whatever computer you’re sending to (or to localhost if the apps are on the same computer), and the OSC port to whatever port your TSPS catcher is on.
is anybody abble to understand better than me where are the rest of the tracked blobs ?
tsps osc vvvv.v4p (24.6 kB)