Description
Movid is an acronym; it stands for 'Modular Open Vision Interaction Daemon'. It's a cross-platform and Open Source vision tracker, designed to be as modular as possible. Although the project is pretty young, it already features more than 20 modules, including blob and fiducial trackers as well as TUIO output. Movid is coded in C++, and uses WOscLIB, cJSON, libevent, libfidtrack, jpeg-8 and XgetOpt.
Movid has several key characteristics:
Cross-platform: It works under Windows, Linux and MacOSX.
Daemon: You can run the program without a GUI and control it from another computer over the network.
Threading: Each module can be run inside a thread. This means that you can finally fully utilize your multi-core processor!
Remote API: The daemon can be controlled with a JSON API. This also means that you can write your own GUI, e.g. in Flash, and the daemon can be controlled from any application that can make http requests!
Full HTML5 embedded administration: By default, the daemon acts as a HTTP server. You can control and modify the tracking pipeline in real-time and adjust many parameters.
Image streaming: Most modules process images. For your application or GUI, you can get the output image via a stream. So your applications can show any image from the piepline or use it for advanced features
Flexible pipeline: Unlike other applications, Movid allows you to fine-tune your image processing pipeline if you are an expert. You can create new pipelines, add modules/filters and change their parameters in real time.
However, Movid is not ready for users yet, since we are missing a few modules, like calibration. Right now, we are searching developers to support us with the further development.
Licence: QPL (Open Source)
Website: http://movid.org/
Documentation: http://movid.org/Documentation/Index
How to contribute: http://movid.org/Documentation/HowToContribute
Source Code: http://github.com/tito/Movid
Developers ML: http://groups.google.com/group/movid-dev
Vimeo videos: http://vimeo.com/groups/41681/
Fiducial tracking: http://vimeo.com/11047041
Introduction to Movid: http://vimeo.com/11056184
If the videos are not working yet, you can check these mirrors:
http://txzone.net/files/projects/movid/screencast-fiducial.ogv
http://the-space-station.com/~dennda/gallery/mt/movid.m4v
Media
Activity
5782 11 9
Comments 9
Well I'm looking at it from a user's perspective, not from a programmer's point of view.
And as a user, I get two frameworks which basicly do the same thing (I'm not involved in Squidy by the way). I would rather have one complete framework than two half finished ones.
But of course it's up to you to prove me wrong and get this thing ready for field use quickly ;)
From an user perspective, i totally agree. Having a ton of linux doesn't help the user. I didn't check deeper Squidy, but Movid is also like a playground. Create the software from start, be able to code your exact vision of the project is something you can't achieve by joining a new project. That, plus the language and architecture choice.
Maybe it's the same idea from Squidy, but definitively not the same way :) We are in c++ / html5 / web api... you're in Java :)
It's not a troll, but i just don't like to code in Java... and avoid everyday to not use java :/
It's my ethical choice !
What makes it different from Squidy? The pipes and filters architecture seems just the same.
In my humble opinion it would benefit the community much more if you combined your efforts (since you have some filters that Squidy is missing and vice versa).
This is ill. I use Max/MSP/Jitter for making quick prototypes. This looks much better.