BUG: recording fps rate : notice and fix (motion-3.2.12-trunk.r557)

Though the addition of the cnt->process_thisframe variable and associated "if(cnt->process_thisframe)" tests greatly reduces processor utilization with minimal functional impact, an unfortunate side-effect of the new variable and test is the frame-rate of recorded video is reduced to the rate limit (i.e. cnt->lastrate / 3), which at present is 3fps.

One (of many) implemented and tested options which will correct the probem is to replace the three occurances of "if(cnt->process_thisframe)" tests in the motion.c source-code file with "if((cnt->process_thisframe || cnt->detecting_motion)" tests. Again, this change to the three lines of source-code in motion.c was tested and - in my environment - corrected the problem with no negative impact.

Environment

Motion version:	3.2.12-trunk.r557
ffmpeg version:	tested with 0.7.8 thru 0.11.2
Shared libraries:	ffmpeg
Server OS:	Slackware 14.0 distribution ; edited uuname -a output: Linux europa 3.2.29 #2 SMP Mon Sep 17 14:19:22 CDT 2012 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux

-- BernieK - 20 Oct 2012

Follow up

Fix record