From: Simon Walls <simonwalls@ya...> - 2007-04-12 10:25:33
Hello all. My first time posting on this list.
I have done a bit of research on the low_cpu feature recently.
The control over frame rate if low_cpu is set >0 is dependent
upon the variable 'detecting_motion'.
I found that detecting_motion is a global variable. Should it
not be a per-thread variable? The effect is that if motion is
detected on *any* thread, *all* threads using low_cpu will have
their frame rate increased to the 'full' rate (and consequent
CPU usage due to higher rate of Jpeg decompression and
alg_diff_standard being used also).
A slightly fuller paragraph on this subject can be found under
SupportQuestion2007x04x07x065120 where I realised what was
Currently motion does not offer 'connections' or programmed
cause-and-effect between threads, ie. one thread detecting
motion 'kicks off' other threads. This has in the past been
recommended to be done by on_xxxx commands.
I could prepare a patch to make detecting_motion a per-thread
variable (not global) in the near future if it would be useful.