Mocolo has been sometimes defined a “camera sensor”, since its business is monitoring video streams in order to “detect interactions”.
Mocolo has been sometimes defined a “camera sensor”, since its business is monitoring video streams in order to “detect interactions”.
People entering an “intraction area” is an example of interaction detected by Mocolo.
Mocolo isn’t exactly a blob tracking application; it’s more appropriate to define it a “presence and motion detector” (the name “Mocolo” comes from the words “Motion” and “Oculus”).
It has been developed keeping in mind the needs of interactive exhibits. It is a stand-alone Windows application which can deliver realtime data to client applications.
Here you see Mocolo monitoring four video sources and sending corresponding data to four client applications.
Client applications can be running on different machines - in the sample, Client0 and Client1 are running on PC0, Client2 is running on PC1 and Client3 is running on PC3 along with Mocolo.
Note: Mocolo is a Windows application, but can send data to any application running on any platform.
Mocolo has been used in a variety of projects. Here are a couple of samples:
“VIP CSC”, a project from the Xtend3dlab group. Here Mocolo provides interaction data to VVVV for visuals and to MAX/MSP for audio.
“Loghi in fuga”, an OrfWare project. Mocolo provides “presence data” to a proprietary (C++ & Direct3D) interactive particle system.
Mocolo instantiates a thread for each processed video source, thus allowing an efficient use of multicore CPUs.
Every source analyzer can be configured in order to achieve good accuracy and low CPU consumption (See later Granularity and Drop Frames in "Image Analysis").