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. Working fine? (Yannick Hagmann)
   2. Re: Working fine? (Colin Law)
   3. DCS-930L - is it possible to connect to this cam via      motion ?
      (Mariusz Ciszewski)
   4. Re: DCS-930L - is it possible to connect to this cam via
      motion ? (?ydr?nas Urbonas)
   5. (no subject) (Yannick Hagmann)
   6. Re: (no subject) (Joerg WEBER)


----------------------------------------------------------------------

Message: 1
Date: Thu, 3 Sep 2015 22:55:43 +0200
From: Yannick Hagmann <[email protected]>
Subject: [Motion-user] Working fine?
To: [email protected]
Message-ID:
        <CAOva+JQ_wsFGoc0WO54vhvLeSvcBChRSZf=akvlh8mhrhj1...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Is it working fine? And can I prevent motion to detect "motion" on startup?
Is there a webinterface for the settings?

[0] [NTC] [ALL] conf_load: Processing thread 0 - config file
/usr/local/etc/motion/motion.conf
[0] [NTC] [ALL] motion_startup: Motion Unofficial-Git-a5b5f13 Started
[0] [NTC] [ALL] motion_startup: Logging to syslog
[0] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
[0] [NTC] [ENC] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD 3670272
LIBAVFORMAT_BUILD 3670272
[0] [NTC] [ALL] main: Thread 1 is from /usr/local/etc/motion/motion.conf
[0] [NTC] [ALL] main: Thread 1 is device: rtsp://
admin:[email protected]:554/h264 input -1
[0] [NTC] [ALL] main: Stream port 8081
[0] [NTC] [ALL] main: Waiting for threads to finish, pid: 4256
[1] [NTC] [ALL] motion_init: Thread 1 started , motion detection Enabled
[1] [ALR] [NET] netcam_start: Network Camera thread starting... for url
(rtsp://admin:[email protected]:554/h264)
[0] [NTC] [STR] httpd_run: motion-httpd testing : IPV4 addr: 127.0.0.1
port: 8080
[0] [NTC] [STR] httpd_run: motion-httpd Bound : IPV4 addr: 127.0.0.1 port:
8080
[0] [NTC] [STR] httpd_run: motion-httpd/Unofficial-Git-a5b5f13 running,
accepting connections
[0] [NTC] [STR] httpd_run: motion-httpd: waiting for data on 127.0.0.1 port
TCP 8080
[1] [NTC] [NET] netcam_rtsp_open_context: Using tcp transport
[1] [NTC] [NET] netcam_connect_rtsp: Camera connected
[1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1 items
[1] [ALR] [NET] netcam_handler_loop: Camera handler thread [2] started
[1] [NTC] [STR] http_bindsock: motion-stream testing : IPV4 addr: 127.0.0.1
port: 8081
[1] [NTC] [STR] http_bindsock: motion-stream Bound : IPV4 addr: 127.0.0.1
port: 8081
[1] [NTC] [ALL] motion_init: Started motion-stream server in port 8081 auth
Disabled
[1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 2 items
[1] [NTC] [EVT] event_new_video FPS 5
[1] [NTC] [ENC] ffmpeg_open Selected Output FPS 5
[1] [NTC] [EVT] event_newfile: File of type 8 saved to:
/home/nuc/Bilder/Raben/01-20150903224333.avi
[1] [NTC] [ALL] motion_detected: Motion detected - starting event 1

Cheers,
Y.
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Thu, 3 Sep 2015 22:04:02 +0100
From: Colin Law <[email protected]>
Subject: Re: [Motion-user] Working fine?
To: Motion discussion list <[email protected]>
Message-ID:
        <CAL=0gLsd==mXY+esDtOBrRaDa0+NcsJ-VMZ74=v3=dijz36...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On 3 September 2015 at 21:55, Yannick Hagmann <[email protected]> wrote:
> Is it working fine? And can I prevent motion to detect "motion" on startup?

What do you see in the first avi file?

Colin

> Is there a webinterface for the settings?
>
> [0] [NTC] [ALL] conf_load: Processing thread 0 - config file
> /usr/local/etc/motion/motion.conf
> [0] [NTC] [ALL] motion_startup: Motion Unofficial-Git-a5b5f13 Started
> [0] [NTC] [ALL] motion_startup: Logging to syslog
> [0] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
> [0] [NTC] [ENC] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD 3670272
> LIBAVFORMAT_BUILD 3670272
> [0] [NTC] [ALL] main: Thread 1 is from /usr/local/etc/motion/motion.conf
> [0] [NTC] [ALL] main: Thread 1 is device:
> rtsp://admin:[email protected]:554/h264 input -1
> [0] [NTC] [ALL] main: Stream port 8081
> [0] [NTC] [ALL] main: Waiting for threads to finish, pid: 4256
> [1] [NTC] [ALL] motion_init: Thread 1 started , motion detection Enabled
> [1] [ALR] [NET] netcam_start: Network Camera thread starting... for url
> (rtsp://admin:[email protected]:554/h264)
> [0] [NTC] [STR] httpd_run: motion-httpd testing : IPV4 addr: 127.0.0.1 port:
> 8080
> [0] [NTC] [STR] httpd_run: motion-httpd Bound : IPV4 addr: 127.0.0.1 port:
> 8080
> [0] [NTC] [STR] httpd_run: motion-httpd/Unofficial-Git-a5b5f13 running,
> accepting connections
> [0] [NTC] [STR] httpd_run: motion-httpd: waiting for data on 127.0.0.1 port
> TCP 8080
> [1] [NTC] [NET] netcam_rtsp_open_context: Using tcp transport
> [1] [NTC] [NET] netcam_connect_rtsp: Camera connected
> [1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1 items
> [1] [ALR] [NET] netcam_handler_loop: Camera handler thread [2] started
> [1] [NTC] [STR] http_bindsock: motion-stream testing : IPV4 addr: 127.0.0.1
> port: 8081
> [1] [NTC] [STR] http_bindsock: motion-stream Bound : IPV4 addr: 127.0.0.1
> port: 8081
> [1] [NTC] [ALL] motion_init: Started motion-stream server in port 8081 auth
> Disabled
> [1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 2 items
> [1] [NTC] [EVT] event_new_video FPS 5
> [1] [NTC] [ENC] ffmpeg_open Selected Output FPS 5
> [1] [NTC] [EVT] event_newfile: File of type 8 saved to:
> /home/nuc/Bilder/Raben/01-20150903224333.avi
> [1] [NTC] [ALL] motion_detected: Motion detected - starting event 1
>
> Cheers,
> Y.
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> 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: Fri, 4 Sep 2015 22:02:40 +0200
From: Mariusz Ciszewski <[email protected]>
Subject: [Motion-user] DCS-930L - is it possible to connect to this
        cam via motion ?
To: Motion discussion list <[email protected]>
Message-ID:
        <caopaqylbsqkwxfo7wxx4nnyajjbtpol+q-6-suar7rgs5nx...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

DCS-930L - is it possible to connect to this cam via motion ?

http://www.dlink.com/uk/en/home-solutions/view/network-cameras/dcs-930l-wireless-n-network-camera
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 4
Date: Sat, 5 Sep 2015 07:11:04 +0300
From: ?ydr?nas Urbonas <[email protected]>
Subject: Re: [Motion-user] DCS-930L - is it possible to connect to
        this cam via motion ?
To: Motion discussion list <[email protected]>
Message-ID:
        <cachtdwri-aqgg1_azfwmj9jrm9by_xmzwra1a7nxfyjyybc...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Yes it is

On Fri, Sep 4, 2015 at 11:02 PM, Mariusz Ciszewski <
[email protected]> wrote:

> DCS-930L - is it possible to connect to this cam via motion ?
>
>
> http://www.dlink.com/uk/en/home-solutions/view/network-cameras/dcs-930l-wireless-n-network-camera
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>
>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 5
Date: Sat, 5 Sep 2015 11:36:49 +0200
From: Yannick Hagmann <[email protected]>
Subject: [Motion-user] (no subject)
To: [email protected]
Message-ID:
        <caova+jrmxhkeh4w34on4to0sa-updqaugfevpjfvnovljop...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi

"Detect motion in predefined areas (1 - 9)" and "Take care: This option
does NOT restrict detection to these areas!" do contradict themselves.

So how can I restrict motion detection to area 5?

# Detect motion in predefined areas (1 - 9). Areas are numbered like that:
1 2 3
# A script (on_area_detected) is started immediately when motion is
4 5 6
# detected in one of the given areas, but only once during an event.
7 8 9
# One or more areas can be specified with this option. Take care: This
option
# does NOT restrict detection to these areas! (Default: not defined)
area_detect 5

-- 
Cheers
Yannick
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 6
Date: Sat, 5 Sep 2015 12:50:26 +0200
From: "Joerg WEBER" <[email protected]>
Subject: Re: [Motion-user] (no subject)
To: "Motion discussion list" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain;charset=iso-8859-1

Hello Yannick,

let me explain a bit more in detail:

The only way to restrict motion detection in a specific area of the
captured image is the application of a mask. This can either be a fixed
mask or a dynamic one - like 'smart_mask' feature.

The area_detect feature is an extension of the various 'on_xxx' actions,
which can start external actions upon certain conditions. Here you can
define areas of the captured image. As soon as there is motion in one of
these areas, a script will be executed.

Let's take an example:
Your camera captures the area around your front door. If a person just
walks by, a movie is recorded and nothing else happens. If that person
really approaches your front door, you can sound the door bell, before
that person even pushes the button.
If you want to prevent motion from recording the person who just passes
by, you have to apply a fixed mask in that place, so that no movie will be
recorded, until someone really approaches your door.

Does that make sense?


Brgds Joerg.


-- 


Yannick Hagmann wrote:
Hi

"Detect motion in predefined areas (1 - 9)" and "Take care: This option
does NOT restrict detection to these areas!" do contradict themselves.

So how can I restrict motion detection to area 5?

# Detect motion in predefined areas (1 - 9). Areas are numbered like that:
1 2 3
# A script (on_area_detected) is started immediately when motion is
4 5 6
# detected in one of the given areas, but only once during an event.
7 8 9
# One or more areas can be specified with this option. Take care: This
option
# does NOT restrict detection to these areas! (Default: not defined)
area_detect 5






------------------------------

------------------------------------------------------------------------------


------------------------------

_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user


End of Motion-user Digest, Vol 112, Issue 2
*******************************************

Reply via email to