Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: lightswitch (Joerg Weber)
2. Re: lightswitch (Joerg Weber)
3. Re: lightswitch (John Baker)
4. Re: lightswitch (Joerg Weber)
----------------------------------------------------------------------
Message: 1
Date: Thu, 11 Aug 2016 19:44:18 +0000
From: "Joerg Weber" <[email protected]>
Subject: Re: [Motion-user] lightswitch
To: "Motion discussion list" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Mike,
that's exactly how it is working. You are invited to rephrase the description
to something more accurate.
Most of these descritptions were written by non native English speakers...
Brgds Joerg.
11. August 2016 19:41 Uhr, "Mike Wilson" schrieb:
I'm not certain either and agree that clarification is needed, but I always
assumed it was to set the percent of change that gets ignored. If you set it to
10 and >10% of the image changed in a single frame it would be ignored. Set it
to 80 and 80% needs to change in a single frame.
On Thu, Aug 11, 2016 at 12:45 PM John Baker wrote: So is it a higher value
makes it less sensitive?
I think the conf file documentation needs improving.
On Thu, Aug 11, 2016, at 01:36 PM, Joerg Weber wrote:
> Hey John,
>
> if you set it to 30 and all of a sudden, there is motion which affects
> 30% of the (pixels of your) image, then this is ignored. Don't set to too
> low, as you might miss real motion then. But that depends on the
> situation actually. If you expect large objects, be careful to not ignore
> them.
>
> If you combine lightswitch with minimum_motion_frames, you can further
> reduce such false positives.
>
> Brgds Joerg.
>
>
> 11. August 2016 14:19 Uhr, "John Baker" schrieb:
> > I get a lot of false readings from motion due to light changes. There's
> > a setting:
> >
> > # Ignore sudden massive light intensity changes given as a percentage of
> > the picture
> > # area that changed intensity. Valid range: 0 - 100 , default: 0 =
> > disabled
> > lightswitch 0
> >
> > If 0 is disabled, what is 1 or 100? Does 1 mean, a little attempt and
> > 100, a lot of attempt to detect, ie more likely to miss movement?
> >
> > ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> > planning reports. http://sdm.link/zohodev2dev (http://sdm.link/zohodev2dev)
> > _______________________________________________
> > Motion-user mailing list
> > [email protected] (mailto:[email protected])
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > (https://lists.sourceforge.net/lists/listinfo/motion-user)
> > http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> > (http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome)
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev (http://sdm.link/zohodev2dev)
> _______________________________________________
> Motion-user mailing list
> [email protected] (mailto:[email protected])
> https://lists.sourceforge.net/lists/listinfo/motion-user
> (https://lists.sourceforge.net/lists/listinfo/motion-user)
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
> (http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome)
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev (http://sdm.link/zohodev2dev)
_______________________________________________
Motion-user mailing list
[email protected] (mailto:[email protected])
https://lists.sourceforge.net/lists/listinfo/motion-user
(https://lists.sourceforge.net/lists/listinfo/motion-user)
http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
(http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome)
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Thu, 11 Aug 2016 19:59:26 +0000
From: "Joerg Weber" <[email protected]>
Subject: Re: [Motion-user] lightswitch
To: "Motion discussion list" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
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.
11. August 2016 18:45 Uhr, "John Baker" <[email protected]> schrieb:
> So is it a higher value makes it less sensitive?
>
> I think the conf file documentation needs improving.
>
> On Thu, Aug 11, 2016, at 01:36 PM, Joerg Weber wrote:
>
>> Hey John,
>>
>> if you set it to 30 and all of a sudden, there is motion which affects
>> 30% of the (pixels of your) image, then this is ignored. Don't set to too
>> low, as you might miss real motion then. But that depends on the
>> situation actually. If you expect large objects, be careful to not ignore
>> them.
>>
>> If you combine lightswitch with minimum_motion_frames, you can further
>> reduce such false positives.
>>
>> Brgds Joerg.
>>
>> 11. August 2016 14:19 Uhr, "John Baker" <[email protected]> schrieb:
>>> I get a lot of false readings from motion due to light changes. There's
>>> a setting:
>>>
>>> # Ignore sudden massive light intensity changes given as a percentage of
>>> the picture
>>> # area that changed intensity. Valid range: 0 - 100 , default: 0 =
>>> disabled
>>> lightswitch 0
>>>
>>> If 0 is disabled, what is 1 or 100? Does 1 mean, a little attempt and
>>> 100, a lot of attempt to detect, ie more likely to miss movement?
>>>
>>> ------------------------------------------------------------------------------
>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
>>> patterns at an interface-level. Reveals which users, apps, and protocols are
>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>> planning reports. http://sdm.link/zohodev2dev
>>> _______________________________________________
>>> Motion-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>
>> ------------------------------------------------------------------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports. http://sdm.link/zohodev2dev
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
Message: 3
Date: Thu, 11 Aug 2016 21:18:41 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] lightswitch
To: [email protected]
Message-ID:
<1470946721.1395691.692869985.21a39...@webmail.messagingengine.com>
Content-Type: text/plain
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.
------------------------------
Message: 4
Date: Thu, 11 Aug 2016 20:34:14 +0000
From: "Joerg Weber" <[email protected]>
Subject: Re: [Motion-user] lightswitch
To: "Motion discussion list" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
John,
Yes, you are correct ref (3).
Defining 'threshold' in percent would be much more inaccurate than pixels,
giving less flexibility to the user.
Defining 'lightswitch' in pixels is unnecessarily complex, as the user has to
be aware of the total number of pixels in a frame at his specific resolution in
order to get an idea of a good value to start with.
There are a few more places, where we have different units - like frames vs.
seconds - in pre_capture and post_capture. I know that it is confusing and we
may change it in the future where it makes sense.
Brgds Joerg.
11. August 2016 22:19 Uhr, "John Baker" <[email protected]> schrieb:
> 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.
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
------------------------------
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 123, Issue 31
********************************************
