From: John B. <jb...@dr...> - 2016-08-11 20:18:48
|
Right, so we have a number of issues here: 1. threshold is a number of pixels, not a percentage. 2. lightswitch is a percentage change, not a number of pixels. 3. If I read correctly, a lower lightswitch value implies "filter more", ie a lightswitch figure of 95 would mean a 'motion frame' would be dropped if 96+% of pixels had changed. Am I correct ref (3)? I wonder if this process can be simplified, starting with using a percentage for (1), or allowing both threshold and lightswitch to be specified as pixels or %? On Thu, Aug 11, 2016, at 08:59 PM, Joerg Weber wrote: > John, > > let me be more clear about it: > > Motion is detecting motion in a way, where it compares frame by frame at > pixel level with an internal reference frame. > If the number of changed pixels is above 'threshold', then this > particular frame is declared a 'motion frame'. > > The lightswitch option can suppress this frame for not being a 'motion > frame', when the percentage of changed pixels is above 'lightswitch' > percent. Nothing more and nothing less. > > For a 'normal' use case, it is probably not a good idea to set > 'lightswitch' to a value of 1 or 2. But we have tried to make motion as > flexible as possible, so that people can use it for tasks, which we were > not even able to think of. That's why it is not so easy to always > recommend a typical value for certain options. But l believe that a > typical range for lightswitch could be from 40 to 80 maybe. > > > Brgds Joerg. |