My explanation why processing can be a good choice

This post comes from my reply on Michal's query

https://www.assembla.com/flows/show/bvDxR8itur3OtTeJe5afGb

For Video Processing:
I looked for whether Processing 1.0 can be used for Video processing. Using this API we would be able to capture videos in real time (offline capturing can be done as well with the loadvideo() method of this library) and I could wrote sample codes for capturing videos in real time using this API. I could also extract frames from the captured videos using this API. Images of .gif , .jpg , .png , .tga formats can be processed with this API. After extracting the frames I could also load pixels of the images in pixels[] array. I could even crop frames using this API. Some other features like Frame difference (to know changes between two frames) and background removal can also be done using Processing API which we might use to retrieve the finger positions and other information. I showed the demo to our teammates and now we all are looking to the features of this API. This can be presented on next Monday’s class as a proof of concept

One more thing is that this api support video capturing using webcam which would be of very little cost. I used one Logitech WebCam of cost 25$

Benefits of using this API
1. Java based
2. Can be used in Eclipse
3. Well documented
4. Less Codes
5. Rich Library for Video Processing

Demerits:
1. Might not be able to run in Linux as this API need Apple’s Quick Time installed which is not yet released for Linux.

Alternatives of Processing 1.0
Peter is now looking into Processing 1.0 to compare the ImageJ API with it. We would soon figure out but as from our meeting on last Friday we are impressed with Processing 1.0

For Signal Processing :

I did not look much for signal processing but while looking for video processing , I found some guys wrote signal processing applications using Processing 1.0 API as well and those are well documented too (links are given in the first post of this message). I believe if we can be consistent for choosing tools for both Visual and Signal Processing Team using Processing 1.0 rather using MatLab or some other signal processing tools then it would be helpful when we would collaborate. I think Signal Processing Team can try writing some sample codes and look whether this API can be used for signal processing or not.

Note: It would be worth looking into the features of this API to get a glimpse of it to feel whether it would be useful or not. I might be wrong. All of our Visual Team members are looking at it. Anyone else interested can look into the wikis with some external links that I wrote here :
https://www.assembla.com/wiki/show/atmr/All_About_Processing_1-0