Small patch adding pwc configuration options
Description of Patch
The patch adds 3 configuration options to control the behavior of the pwc tracking code. Our Logitech Sphere's seem to work best with "750, 1000, 4", instead of the default "1000, 1000, 10". If this combination is incorrect, the camera will move slow (the case with the default settings), or it still moves when motion restarts motion tracking (even worse). I think the defaults are best left untouched, but the configuration options are handy when needed. (we needed the extra speed to not lose walking people)
Installation of Patch
Download the patch file (motion-pwc.patch
). If it is packed as a gz or tar.gz unpack it first. Then copy it to the motion source directory and issue the command (assuming the patch file is called filename_of_patch_file.diff)
patch < filename_of_patch_file.diff
Then re-build Motion and test the patch.
Change History of Patch
Thanks for the patch.
The defaults that we have today were never really well tested so maybe your 750 is a better default value?
Do we actually need the config parameters if the defaults were 750/1000/4? Would you need to change them yourself?
I am trying to avoid new config options unless they add significant value. But if they do I am prepared to add them.
The patch you have made is very neat. You have chosen the config names well. I have not yet tried your patch. In fact I have not played with the auto tracking for a while.
If you pick todays daily snap (today is 15 Nov 2005). Or actually the one from last night you will find a new config option track_auto which you can use to enable auto tracking.
- 15 Nov 2005
We only use Sphere's and 750/1000/4 is the best for our situation, but it might be to much for other cams, especially with other motors.
1000/1000/10 is fast enough when the moving objects are far away or moving slower then walking humans
I noticed the best values are not so much camera dependant as they are environment dependant, when motion should more precisely locate the moving object it is a good idea to enlarge x_speed, but when the object might deside to turn around quickly move_wait should be al small as posible (3 works ok with low (400) speeds here), wich might be usefull to track a face.
We use motion to track people in a 20m^2 room, that don't usualy walk away, but do walk around now and then.
1000/1000/10 won't break on much cam's but 750/1000/4 might, as i don't know any other pwc cam's, so manualy changing is a better idea I think.
Also, the track_auto option comes in very handy!
- 15 Nov 2005
I decided to integrate a modified and more generic version of the patch.
I wanted the changes to also fit my plans for a more generic tracking feature. I renamed the options and changed the value to be the angle in degrees. This means that you will have to choose either 7 or 8 degrees instead of 7.5 (750) which I am sure is fine in practical.
I added 3 new tracking options: track_step_angle_x, track_step_angle_y, and track_move_wait. The options track_step_angle control the movement during auto tracking and are currently only active for the pwc type tracking. The idea is that they can later also be used for the generic tracking as it evolves. The track_move_wait controls the number of frames after the camera has moved (auto or manual) during which motion detection is disabled. This option should be set so low that the motion detection is re-enabled the minute the camera is standing still again. Thanks for the patch. The new code will be in the daily snap for 01 December 2005 and later in 3.2.4_snap6.
- 30 Nov 2005