If I had a penny for every unanswered post or stupid question I've posted on this forum I'd have enough for McDonalds Happy Meal (maybe two).
But the amount of intelligently answered posts I've received has amounted to two firsts in terms of grades that count so far and I'm hoping I can finish with a degree of the same. Patience is well rewarded.
On the other hand, I've been 11 meters in the bloody air with a fear of heights trying to do a big art installation. If I don't check the board - chances are I'm drinking myself through the floor from stress.
Patronization followsvideoEvent() is not a Processing method it was removed on the change from Alpha to Beta. Get that bloody thing out of your code like I told you to.
And...
The code works fine on my machine. I'm uploading a version I've made from yours - with an image of the camera capture in the background to illustrate what is going on.
If you look at what analyzeChangeVideo() is doing you'll see that it runs through all the pixels, looks for a change and then creates a lot of little motes where there is a change.
The downside is that you only have 10,000 particles. Those have to look after 307200 pixels! (640 * 480) Once they get used up, the code starts grabbing preused particles. Hence the motes end up at the bottom of the screen.
I tried making it skip lots of pixels at a time but it makes it look a bit crap.
My version.My advice if you like this thing and want to continue with it that you try to break it down into something simple. Or perhaps just put the code in another window and copy it by hand into processing whilst changing the name of each variable into something you understand. That way you know for sure what you're writing. It may be slow but if you're learning as opposed to trying to get a project together for a deadline, it's a good thing to do.