Hehe, it looks like you're getting a rough welcome Vincimus. Let me start by saying "Welcome to Anandtech!"
What you're trying to accomplish may not be feasible, but I see no reason to let that stop you from trying. If you get even 10% of the way to your final goal I still think you will learn quite a bit. As long as the education is your true goal and the software you're writing is the means to that end, I think it could be a valuable use of your time.
I'm not a programmer by most people's standards, but I do dabble in a few languages and I've recently worked with some image analysis. It wasn't real time, but as CycloWizard mentioned, videos are just a simple series of still images anyway (as long as you're not converting from analogue video and dealing with interlacing etc, but that can be dealt with as well), so, I think you're right to start with still image analysis and then you can experiment with make it as efficient as possible.
I worked in a programming language called LabView. If you haven't heard of it, it is a graphical programming language that is specifically designed to interface with instruments. Over the years, it has developed into a pretty extensive general programming language as well, but its roots are in acquisition and control. As you can imagine, "machine vision" is one of their specialties. From what I hear, it is growing in popularity with industry for use in things like motion control and plant operations, so if your a programmer, it may be a good program to be familiar with. My university (Case Western Reserve) had a car in the DARPA challenge that used LabView for sensors and feedback.
Here is a link to LabView's manual for "vision concepts". It is specific to LabView, but has a lot of good general image analysis information similar to the edge detection and morphological transformations CycloWizard referred to. If you're wanting to know more about image analysis in general, I found it to be pretty helpful for me starting with very little knowledge in either image analysis or programming.
http://digital.ni.com/manuals....F7701F8625731500701D23
LabView did a lot of the hard work for my program. I was analyzing the movement of particles with time and wrote a program that:
1) Identifies all 200 or so particles in each of about 100 frames that I collected from a camera attached to my microscope. The x,y location of these particles is then written to a text file, one file per image processed.
2) Analyzes the locations with time to match particles between frames and outputs a new text file for each particle detailing its changing location with time.
With ~200 particles and 100 frames, my computer (P4-2.8GHz) takes about 3 seconds for step 1 and 17 seconds for step 2. As you can see, the simple image analysis occurs at essentially real-time speeds (30 Hz on a full desktop), but my more elaborate analysis is much slower.
Another resource you may want to consider is the anandtech programming forum. Might be helpful for you.
http://forums.anandtech.com/ca...tid=70&flcache=2884092
-Tim
Edit: I really should remember to spell check.