The feature was discussed on IRC #motion channel.
Here is the essential part.
- Lavr, the adjustment feature was on top of my list until the guy on the list got me to smartmask. I still prefer to call it setup_mode and not put too much into it. Or at least have some tings like text_changes separately available.
- what is adjustment feature ?
- setup_mode on or off is a nice name
We need to help the user setting all the different values fast and easy.
- Yes. We should start using it one day and put one thing after another into the mode until everything usefull is covered. The second goal should be to eliminate some parameters (except text_changes:-))
- As far as I can see it should not be difficult to redirect both smart mask OR motion image to the streaming webcam.
- That is an option but I'm still thinking about the coloured overlay idea.
- setup_mode motion
- 'motion' for all camera settings like noise, threshold and so on?
- I think it is easier to set noise_level and threshold by looking at a live webcam image showing detected pixels
- Exactly. But that can be part of the setup_mode. We can turn on some output (console or log) and enable the (lost) feature to see the 'real' diffs for noise_level adjust.
Your idea some time ago was to run it in non-daemon and use printf's
- "real diffs" would require not using the diff_fast
- Sure. Therefore setup_mode. This is IMHO the only way to properly adjust noise_level at night.
- Maybe. Maybe not. Any of you ever played with radio?
- For sure this will add some more if's in the main-loop. But I don't see a performance issue here - not even at 25fps.
- A two-way radio has a function called a squelch.
- As a user you adjust the squelch in 1 second using your ears.
You turn it up until the noise goes away and then a little notch more so variations do not open the speaker all the time.
- Well but if there's nothing to listen because diff_standard is a bit 'deaf'?
- If we have a webcam mode where you see the detected pixels all the time you turn up noise_level until they stop
And then a little more
to be safe
- Sure. But still you have to gather this information and must not supress it in diff_standard.
- Yes but instead of the numbers you get a visual image.
- Ummm nice ideas that will involve to implement a kind of dinamic filters
- Folkert changed a lot there when he optimized alg.c
- The idea is that this mode only runs like this when setup_mode = motion.
- Ahh - see the detected pixels - the motion-image you mean?
- Yes. And not depending on Motion detected. A real diff image of all changed pixels that are changed more than noise_level
- That is an option. Let's start installing motion in mind: You will have to setup the size first. Then noise and then threshold.
- Yes. Size is simple.
Then noise. You enable this setup_mode motion and connect your browser to the webcam stream.
- We need a method to show the user how many pixels have changed when he was dancing in front of his cam. He cannot look and dance simulanteously:-)
- rddtools is a nice option to show a graphics about changed pixels
- Then you increase / decrease the noise until the value is a little above where the pictures goes white.
What is nice about seeing the changed pixels is that the human brain can see the difference between noise and actual motion
- sack, we should better keep it simple.
Lavr, that's true
- Now that the noise_level is set we come to the "dancing part"
- I was too fast - as usual...
- Here we need the actual number for the threshold.
When Motion is detected the text_changes is fine. The problem is seeing what the real diffs are when Motion is not detected.
setup_mode = threshold could turn on outputting to console. It can turn on the text_changes. It can disable the alg_diff_fast
- Lavr, do you mean that the text_changes shown is not real when motion is not detected ? ( i thought it was )
- It shows 0.
- So you can dance and then review the console output.
sack, it did in older versions. But still not 'real' because of diff_fast
- joergw, ok ...
- When Motion is not detected the faster detection algoritm is used which only looks at a fraction of the pixels.
- i guess is not a good idea to show the output in console , better to show them in pictures , so activating output_all you can check easily
- (Kenneth wonders how much it cost to not have the fast - time for a little test)
Yes. I usually set the threshold low, record my dancing with text_changes, and then evaluate what the threshold value should be.
- If you don't have all the gimmicks on - not too much I guess. (Buy a new cam - 'd like to c ya dance:-))
The question is: Is there an easier option for a newbie? sack, tell us about rddtools and motion please
- well rrdtool is a tool used by draw graphics usually for bandwidth usage or memory / cpu usage , mrtg is using it
Do you know what i'm talking about ?
- BTW: sack, if you had an idea some minutes ago how to optimize noise_tune - go ahead. It's not working properly I guess...
I'm using mrtg but w/o rrdtools
- mrtg uses rrdtool AFAIK
anyway is a nice tool to draw any kind of graphics from any data you have
joergw, i'm not best guy to optimize that kind of things :-/
- sounds like a "related project" to me
I am running with only alg_standard now.
- Lavr, yes it can be
- With Kenneth's idea we should already have anything we need. noise_tune: no problem. We'll come to that one day
And I'll leave now. Good night. I'll keep this log tomorrow - Good ideas...
- 04 Dec 2004
Setup of Motion
It is generally complicated to configure Motion and my experience is that it is difficult to know why Motion is capturing a picture or not.
I would like to give my expectation concerning this point.
The first problem is that Motion has a lot of parameters and it is not possible to know which element need to be adjusted.
Is the threshold too high? Is minimum_motion_frame correctly setup, what about the gap?. The only solution that I see is that
Motion needs to display the current values in a report.
The value before the / is the measured value and the value after the trigger.
If the use could see such report, he could adjust the parameters correctly.
The format of the report should be easely be parsed by a program and readable directly.
Where should this report stored?
A solution would be to generate a file pro JPG picture, this can be helpfull for analysing why a picture was stored. But this can not work with the WebCam
, and so does not work for an interactive configuration.
An other solution is to put this report into the JPEG file itself. This can be done as text over the picture (like
,...) or better put it into the comment field of the JGP file. (The comment field is a free text field on which we found normally (C) notices.).
This have the advantage that the picture itself is not masked by any text.
I made an GUI extension to XMotion (version 0.5) for tuning Motion, and I really miss that I can not display some indicators.
- Tuning INterface of XMotion:
- 22 Jan 2005
A new nice setup feature has been added - first time in MotionRelease3x2x1snap5
Our hero is JoergWeber
who has done a great job with this feature.
- 17 Mar 2005