|
 |
Motion detection working great. Or at least well enough. I'm happy. Look, I
wave my hand and it tells me how fast I'm waving. Now I just have to
integrate it into the other program. Difficult only because they're both
experimental kludges.
Three hours later, I go back to do that, and WTF? The motion detector code
isn't working. Razin'frazin' piece of crap! How could it be broken? I didn't
even recompile it! And now all I get is speckles, and it barely shows me
any edges it's finding. Oh, wait... Hold on.
Sun went down. Turn on lights. Much better. Suddenly working again. Whew.
--
Darren New, San Diego CA, USA (PST)
The question in today's corporate environment is not
so much "what color is your parachute?" as it is
"what color is your nose?"
Post a reply to this message
|
|
|
|
Darren New wrote:
> Sun went down. Turn on lights. Much better. Suddenly working again. Whew.
>
I had a similar moment working with motion detection in AS3. The testing
environment made a big difference in how well it worked.
The better moment was when my boss wanted to have the projected result
of the motion detection, it created a Jackson Pollock-like painting from
movement, behind the person using it. Feedback doesn't have the same
meaning to everyone, and it took some doing to convince why this would
not be a great idea.
Short version: With enough filtering, you can prevent paint splatters
from triggering motion detection. It just stops working when the lights
get dim or the background color changes from white to black.
Post a reply to this message
|
|
