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 (Mr Dave)
2. Re: lightswitch (John Baker)
3. Re: The New Motion and the New RPI (Joseph Heenan)
4. compilation error on Xenial (odroid C1) (Dimitris Roussos)
----------------------------------------------------------------------
Message: 1
Date: Thu, 11 Aug 2016 18:55:59 -0600
From: Mr Dave <[email protected]>
Subject: Re: [Motion-user] lightswitch
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
I would agree that the documentation of these options could be better.
I'd like to ask if others can assist in making sure that things are
logged as issues or edit the wiki directly to make it clear. With
respect to adding a slider and making a more intuitive web interface,
I'll go back to keeping the Motion application simple. Various
applications such as MotionEye which is actively being developed are
taking the role of putting a user friendly web interface on top of
Motion for those that desire it.
Dave
On 8/11/2016 2:52 PM, John Baker wrote:
> Thank you for the clarification. I think we've got too much computer
> science. :)
>
> Lightswitch: More is less. How about it's inversed, so a larger figure
> means ignore more light? "Keep increasing until the light changes stop
> triggering motion".
>
> Threshold: Pixels is of course more accurate, but % is more obvious.
> Allow both. Think of how we could configure this via a user friendly web
> interface - a slider called "motion detection" that moves between "low"
> and "high" (ie a percentage).
>
>
>
>
> On Thu, Aug 11, 2016, at 09:34 PM, Joerg Weber wrote:
>> 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
>> 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: 2
Date: Fri, 12 Aug 2016 07:00:23 +0100
From: John Baker <[email protected]>
Subject: Re: [Motion-user] lightswitch
To: [email protected]
Message-ID:
<1470981623.1507435.693212369.3f484...@webmail.messagingengine.com>
Content-Type: text/plain
> This goes back to what was said earlier and how large we want to make motion.
> Currently it is lean and complex to setup, but that gives it an advantage in
> a reduced environment
Mike, i agree the motion binary should be kept simple, but an easy to
follow configuration does not have to mean a less lean binary, ie.
1. The value for lightswitch should be 'greater for more effect', not
'less for more'. That's not lots of extra coding, but probably 1 / at
some point.
2. Use a YAML parser to read a YAML formatted configuration file, which
I assume motion can link to, and hence eject all of the custom code to
read the config file and assemble structures (if that's how it works -
it works that way in python), which in turn makes config easier to read,
ie.
# Include another file with a set of shared options
include: globals.yml
detection:
# Comment ...
lightswitch: 20
threshold: ....
output:
snapshots:
directory: /tmp/camera/snapsots
format: yyyy-MM-dd.jpg
timelapse:
# Every X mlliseconds
frequency: 1000
directory: ...
format: ...
detection:
directory: ...
and so on.
Simply providing a structure to configuration will make it /so/ much
easier to read/follow, and should reduce hand cranked code too.
------------------------------
Message: 3
Date: Fri, 12 Aug 2016 08:12:37 +0100
From: Joseph Heenan <[email protected]>
Subject: Re: [Motion-user] The New Motion and the New RPI
To: Motion discussion list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Jack,
Personally I don?t see any downside to merging this (though I?ve not looked at
the in detail code yet); but obviously someone needs to actually do the
required work. It may be worth asking dozencrows if he/she would have any
interest in updating their code to work against the latest version of motion.
Thanks
Joseph
> On 12 Aug 2016, at 01:40, Jack Clift <[email protected]> wrote:
>
> Hello All,
>
> With the recent advent of new custody for the Motion initiative, and the new
> version of RPI, is there a possibility to integrate native support for the
> RPI camera? Presently getting to work involves installing 'mmal' 'fork'
> created / maintained by dozencrows?
>
> Regards
>
>
> ------------------------------------------------------------------------------
> 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: 4
Date: Fri, 12 Aug 2016 10:17:13 +0300
From: Dimitris Roussos <[email protected]>
Subject: [Motion-user] compilation error on Xenial (odroid C1)
To: [email protected]
Message-ID:
<CADC42EYVDJzqse49Y9dQu7iec_+VL8Z=ybe5q6t+ztdr2ep...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi
I'm trying to compile motion-mrdave bit I'm getting the following error :
*configure: error: Package requirements (libavutil libavformat libavcodec
libswscale) were not met:*
*No package 'libavformat' found*
*No package 'libavcodec' found*
*Consider adjusting the PKG_CONFIG_PATH environment variable if you*
*installed software in a non-standard prefix.*
*Alternatively, you may set the environment variables FFMPEG_CFLAGS*
*and FFMPEG_LIBS to avoid the need to call pkg-config.*
*See the pkg-config man page for more details.*
When searching the missing packages it seems that have
installed libavformat-ffmpeg56 and libavcodec-ffmpeg56 instead.
I'm pretty unexperienced in linux so I'd like you kind assistance for how
to do the compilation. Please keep in mind that I already have a working
version of motion but without RTSP support.
Thankyou
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
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 33
********************************************
