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: zoneminder migration (Rainer Dorsch)
   2. Re: zoneminder migration (Rainer Dorsch)
   3. Re: zoneminder migration (Jake Stride)


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

Message: 1
Date: Mon, 07 Oct 2019 22:46:40 +0200
From: Rainer Dorsch <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] zoneminder migration
Message-ID: <5591891.V67EYXsC94@h370>
Content-Type: text/plain; charset="us-ascii"

Thanks, Jake.

My understanding is that the active camera.conf files are referenced in 
motion.conf.

If that is true what is in your motion.conf?

The default has entries like the onces below, but /dev/video0 does not make 
sense for me. Did you comment this line or don't they hurt? I assume at least 
daemon needs to be on (?).

############################################################                    
                                                                                
                                                                                
                                                     
# System control configuration parameters                                       
                                                                                
                                                                                
                                                     
############################################################                    
                                                                                
                                                                                
                                                     

# Start in daemon (background) mode and release terminal.                       
                                                                                
                                                                                
                                                     
daemon off

# Start in Setup-Mode, daemon disabled.                                         
                                                                                
                                                                                
                                                     
setup_mode off

# File to store the process ID.                                                 
                                                                                
                                                                                
                                                     
; pid_file value

# File to write logs messages into.  If not defined stderr and syslog is used.  
                                                                                
                                                                                
                                                     
; log_file value

# Level of log messages [1..9] (EMG, ALR, CRT, ERR, WRN, NTC, INF, DBG, ALL).   
                                                                                
                                                                                
                                                     
log_level 6

# Target directory for pictures, snapshots and movies                           
                                                                                
                                                                                
                                                     
; target_dir value

# Video device (e.g. /dev/video0) to be used for capturing.                     
                                                                                
                                                                                
                                                     
videodevice /dev/video0

# Parameters to control video device.  See motion_guide.html                    
                                                                                
                                                                                
                                                     
; vid_control_params value

# The full URL of the network camera stream.                                    
                                                                                
                                                                                
                                                     
; netcam_url value

# Name of mmal camera (e.g. vc.ril.camera for pi camera).                       
                                                                                
                                                                                
                                                     
; mmalcam_name value

# Camera control parameters (see raspivid/raspistill tool documentation)        
                                                                                
                                                                                
                                                     
; mmalcam_control_params value

############################################################                    
                                                                                
                                                                                
                                                     
# Image Processing configuration parameters                                     
                                                                                
                                                                                
                                                     
############################################################                    
                                                                                
                                                                                
                                                     

# Image width in pixels.                                                        
                                                                                
                                                                                
                                                     
width 640

# Image height in pixels.                                                       
                                                                                
                                                                                
                                                     
height 480

# Maximum number of frames to be captured per second.                           
                                                                                
                                                                                
                                                     
framerate 15

# Text to be overlayed in the lower left corner of images                       
                                                                                
                                                                                
                                                     
text_left CAMERA1

# Text to be overlayed in the lower right corner of images.                     
                                                                                
                                                                                
                                                     
text_right %Y-%m-%d\n%T-%q


Many thanks
Rainer

Am Montag, 7. Oktober 2019, 14:12:55 CEST schrieben Sie:
> Mine looks like this:
> 
> # User defined name for the camera.
> camera_name MyCam
> 
> # Numeric identifier for the camera.
> camera_id 103
> 
> # The full URL of the network camera stream.
> netcam_url rtsp://xxx.xxx.xxx.xxx:8554/unicast
> netcam_userpass user:password
> 
> On Mon, 7 Oct 2019 at 16:12, Rainer Dorsch via Motion-user <
> 
> [email protected]> wrote:
> > Hi Jake,
> > 
> > thanks for your quick reply. Do you have a network camera? If yes, would
> > you
> > mind to share your motion.conf and camera.conf files (as a example for a
> > working setup)? If you do, please do not forget to remove private data
> > like
> > passwords...
> > 
> > Many thanks
> > Rainer
> > 
> > Am Montag, 7. Oktober 2019, 00:28:25 CEST schrieben Sie:
> > > https://motion-project.github.io/motion_config.html is the best way to
> > > figure out what you need to do.
> > > 
> > > I started with with motioneye that's web front end built on top of
> > > motion
> > > to make configuration easy. Once I had that working and saw how powerful
> > 
> > it
> > 
> > > was I just decided to use motion on its own.
> > > 
> > > That might help you get started.
> > > 
> > > On Mon., 7 Oct. 2019, 05:58 Rainer Dorsch via Motion-user, <
> > > 
> > > [email protected]> wrote:
> > > > Hi,
> > > > 
> > > > I used zoneminder in the past, but since it is not part of Debian 10
> > > > (buster),
> > > > I want to test motion.
> > > > 
> > > > I have network cameras (HIKVISION Full HD 4MP IP DS-2CD2042WD-I), is
> > 
> > there
> > 
> > > > somewhere a quick start guide which helps to get quickly a working
> > > > configuration from which I can then start optimizing? Motion is a bad
> > 
> > name
> > 
> > > > for
> > > > a search engine :-/
> > > > 
> > > > Any advice is welcome.
> > > > 
> > > > Thanks
> > > > Rainer
> > > > 
> > > > --
> > > > Rainer Dorsch
> > > > http://bokomoko.de/
> > > > 
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Motion-user mailing list
> > > > [email protected]
> > > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > > https://motion-project.github.io/
> > > > 
> > > > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
> > 
> > --
> > Rainer Dorsch
> > http://bokomoko.de/
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Motion-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/motion-user
> > https://motion-project.github.io/
> > 
> > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user


-- 
Rainer Dorsch
http://bokomoko.de/





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

Message: 2
Date: Mon, 07 Oct 2019 23:25:41 +0200
From: Rainer Dorsch <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] zoneminder migration
Message-ID: <1801940.PTOex7Dxxi@h370>
Content-Type: text/plain; charset="us-ascii"

I have a basic working (=cameras detecting events) system setup now. I entered 
the optimization phase :-)

Two quick questions:

I find parameters like threshold in motion.conf. From my zoneminder experience, 
these parameters have been heavily camera dependent (or better scene dependent 
recorded by a camera location and view). Is it possible to make these 
parameters camera specific? Can I simply add them in camera.conf?

Can I collect test scenes and replay them to the parameter optimization phase?

Thanks
Rainer

Am Montag, 7. Oktober 2019, 22:46:40 CEST schrieb Rainer Dorsch via Motion-
user:
> Thanks, Jake.
> 
> My understanding is that the active camera.conf files are referenced in
> motion.conf.
> 
> If that is true what is in your motion.conf?
> 
> The default has entries like the onces below, but /dev/video0 does not make
> sense for me. Did you comment this line or don't they hurt? I assume at
> least daemon needs to be on (?).
> 
> ############################################################
> # System control configuration parameters
> ############################################################
> 
> # Start in daemon (background) mode and release terminal.
> daemon off
> 
> # Start in Setup-Mode, daemon disabled.
> setup_mode off
> 
> # File to store the process ID.
> ; pid_file value
> 
> # File to write logs messages into.  If not defined stderr and syslog is
> used. ; log_file value
> 
> # Level of log messages [1..9] (EMG, ALR, CRT, ERR, WRN, NTC, INF, DBG,
> ALL). log_level 6
> 
> # Target directory for pictures, snapshots and movies
> ; target_dir value
> 
> # Video device (e.g. /dev/video0) to be used for capturing.
> videodevice /dev/video0
> 
> # Parameters to control video device.  See motion_guide.html
> ; vid_control_params value
> 
> # The full URL of the network camera stream.
> ; netcam_url value
> 
> # Name of mmal camera (e.g. vc.ril.camera for pi camera).
> ; mmalcam_name value
> 
> # Camera control parameters (see raspivid/raspistill tool documentation)
> ; mmalcam_control_params value
> 
> ############################################################
> # Image Processing configuration parameters
> ############################################################
> 
> # Image width in pixels.
> width 640
> 
> # Image height in pixels.
> height 480
> 
> # Maximum number of frames to be captured per second.
> framerate 15
> 
> # Text to be overlayed in the lower left corner of images
> text_left CAMERA1
> 
> # Text to be overlayed in the lower right corner of images.
> text_right %Y-%m-%d\n%T-%q
> 
> 
> Many thanks
> Rainer
> 
> Am Montag, 7. Oktober 2019, 14:12:55 CEST schrieben Sie:
> > Mine looks like this:
> > 
> > # User defined name for the camera.
> > camera_name MyCam
> > 
> > # Numeric identifier for the camera.
> > camera_id 103
> > 
> > # The full URL of the network camera stream.
> > netcam_url rtsp://xxx.xxx.xxx.xxx:8554/unicast
> > netcam_userpass user:password
> > 
> > On Mon, 7 Oct 2019 at 16:12, Rainer Dorsch via Motion-user <
> > 
> > [email protected]> wrote:
> > > Hi Jake,
> > > 
> > > thanks for your quick reply. Do you have a network camera? If yes, would
> > > you
> > > mind to share your motion.conf and camera.conf files (as a example for a
> > > working setup)? If you do, please do not forget to remove private data
> > > like
> > > passwords...
> > > 
> > > Many thanks
> > > Rainer
> > > 
> > > Am Montag, 7. Oktober 2019, 00:28:25 CEST schrieben Sie:
> > > > https://motion-project.github.io/motion_config.html is the best way to
> > > > figure out what you need to do.
> > > > 
> > > > I started with with motioneye that's web front end built on top of
> > > > motion
> > > > to make configuration easy. Once I had that working and saw how
> > > > powerful
> > > 
> > > it
> > > 
> > > > was I just decided to use motion on its own.
> > > > 
> > > > That might help you get started.
> > > > 
> > > > On Mon., 7 Oct. 2019, 05:58 Rainer Dorsch via Motion-user, <
> > > > 
> > > > [email protected]> wrote:
> > > > > Hi,
> > > > > 
> > > > > I used zoneminder in the past, but since it is not part of Debian 10
> > > > > (buster),
> > > > > I want to test motion.
> > > > > 
> > > > > I have network cameras (HIKVISION Full HD 4MP IP DS-2CD2042WD-I), is
> > > 
> > > there
> > > 
> > > > > somewhere a quick start guide which helps to get quickly a working
> > > > > configuration from which I can then start optimizing? Motion is a
> > > > > bad
> > > 
> > > name
> > > 
> > > > > for
> > > > > a search engine :-/
> > > > > 
> > > > > Any advice is welcome.
> > > > > 
> > > > > Thanks
> > > > > Rainer
> > > > > 
> > > > > --
> > > > > Rainer Dorsch
> > > > > http://bokomoko.de/
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > Motion-user mailing list
> > > > > [email protected]
> > > > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > > > https://motion-project.github.io/
> > > > > 
> > > > > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
> > > 
> > > --
> > > Rainer Dorsch
> > > http://bokomoko.de/
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Motion-user mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > https://motion-project.github.io/
> > > 
> > > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user


-- 
Rainer Dorsch
http://bokomoko.de/





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

Message: 3
Date: Tue, 8 Oct 2019 05:51:36 +0800
From: Jake Stride <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] zoneminder migration
Message-ID:
        <CAOO87zOF09BTefZa4t0H26=pw+un3+iaxoc_jsvjjld0vwh...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

One of the things that made me move to motion from motioneye is that you
can put config options in motion.conf and then override then for individual
cameras so you can choose where to put options.(hence why my original
config is fairly light) - that's what works for me as I have two brands of
cameras.

I run tensorflow on my cameras so have done only minor tweaking as you
suggest but the paragraphs after the bullet points and before Video4Linix
should set you on the right direction
https://motion-project.github.io/motion_config.html with web control and
other areas.

On Tue., 8 Oct. 2019, 05:26 Rainer Dorsch via Motion-user, <
[email protected]> wrote:

> I have a basic working (=cameras detecting events) system setup now. I
> entered
> the optimization phase :-)
>
> Two quick questions:
>
> I find parameters like threshold in motion.conf. From my zoneminder
> experience,
> these parameters have been heavily camera dependent (or better scene
> dependent
> recorded by a camera location and view). Is it possible to make these
> parameters camera specific? Can I simply add them in camera.conf?
>
> Can I collect test scenes and replay them to the parameter optimization
> phase?
>
> Thanks
> Rainer
>
> Am Montag, 7. Oktober 2019, 22:46:40 CEST schrieb Rainer Dorsch via Motion-
> user:
> > Thanks, Jake.
> >
> > My understanding is that the active camera.conf files are referenced in
> > motion.conf.
> >
> > If that is true what is in your motion.conf?
> >
> > The default has entries like the onces below, but /dev/video0 does not
> make
> > sense for me. Did you comment this line or don't they hurt? I assume at
> > least daemon needs to be on (?).
> >
> > ############################################################
> > # System control configuration parameters
> > ############################################################
> >
> > # Start in daemon (background) mode and release terminal.
> > daemon off
> >
> > # Start in Setup-Mode, daemon disabled.
> > setup_mode off
> >
> > # File to store the process ID.
> > ; pid_file value
> >
> > # File to write logs messages into.  If not defined stderr and syslog is
> > used. ; log_file value
> >
> > # Level of log messages [1..9] (EMG, ALR, CRT, ERR, WRN, NTC, INF, DBG,
> > ALL). log_level 6
> >
> > # Target directory for pictures, snapshots and movies
> > ; target_dir value
> >
> > # Video device (e.g. /dev/video0) to be used for capturing.
> > videodevice /dev/video0
> >
> > # Parameters to control video device.  See motion_guide.html
> > ; vid_control_params value
> >
> > # The full URL of the network camera stream.
> > ; netcam_url value
> >
> > # Name of mmal camera (e.g. vc.ril.camera for pi camera).
> > ; mmalcam_name value
> >
> > # Camera control parameters (see raspivid/raspistill tool documentation)
> > ; mmalcam_control_params value
> >
> > ############################################################
> > # Image Processing configuration parameters
> > ############################################################
> >
> > # Image width in pixels.
> > width 640
> >
> > # Image height in pixels.
> > height 480
> >
> > # Maximum number of frames to be captured per second.
> > framerate 15
> >
> > # Text to be overlayed in the lower left corner of images
> > text_left CAMERA1
> >
> > # Text to be overlayed in the lower right corner of images.
> > text_right %Y-%m-%d\n%T-%q
> >
> >
> > Many thanks
> > Rainer
> >
> > Am Montag, 7. Oktober 2019, 14:12:55 CEST schrieben Sie:
> > > Mine looks like this:
> > >
> > > # User defined name for the camera.
> > > camera_name MyCam
> > >
> > > # Numeric identifier for the camera.
> > > camera_id 103
> > >
> > > # The full URL of the network camera stream.
> > > netcam_url rtsp://xxx.xxx.xxx.xxx:8554/unicast
> > > netcam_userpass user:password
> > >
> > > On Mon, 7 Oct 2019 at 16:12, Rainer Dorsch via Motion-user <
> > >
> > > [email protected]> wrote:
> > > > Hi Jake,
> > > >
> > > > thanks for your quick reply. Do you have a network camera? If yes,
> would
> > > > you
> > > > mind to share your motion.conf and camera.conf files (as a example
> for a
> > > > working setup)? If you do, please do not forget to remove private
> data
> > > > like
> > > > passwords...
> > > >
> > > > Many thanks
> > > > Rainer
> > > >
> > > > Am Montag, 7. Oktober 2019, 00:28:25 CEST schrieben Sie:
> > > > > https://motion-project.github.io/motion_config.html is the best
> way to
> > > > > figure out what you need to do.
> > > > >
> > > > > I started with with motioneye that's web front end built on top of
> > > > > motion
> > > > > to make configuration easy. Once I had that working and saw how
> > > > > powerful
> > > >
> > > > it
> > > >
> > > > > was I just decided to use motion on its own.
> > > > >
> > > > > That might help you get started.
> > > > >
> > > > > On Mon., 7 Oct. 2019, 05:58 Rainer Dorsch via Motion-user, <
> > > > >
> > > > > [email protected]> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I used zoneminder in the past, but since it is not part of
> Debian 10
> > > > > > (buster),
> > > > > > I want to test motion.
> > > > > >
> > > > > > I have network cameras (HIKVISION Full HD 4MP IP
> DS-2CD2042WD-I), is
> > > >
> > > > there
> > > >
> > > > > > somewhere a quick start guide which helps to get quickly a
> working
> > > > > > configuration from which I can then start optimizing? Motion is a
> > > > > > bad
> > > >
> > > > name
> > > >
> > > > > > for
> > > > > > a search engine :-/
> > > > > >
> > > > > > Any advice is welcome.
> > > > > >
> > > > > > Thanks
> > > > > > Rainer
> > > > > >
> > > > > > --
> > > > > > Rainer Dorsch
> > > > > > http://bokomoko.de/
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Motion-user mailing list
> > > > > > [email protected]
> > > > > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > > > > https://motion-project.github.io/
> > > > > >
> > > > > > Unsubscribe:
> https://lists.sourceforge.net/lists/options/motion-user
> > > >
> > > > --
> > > > Rainer Dorsch
> > > > http://bokomoko.de/
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Motion-user mailing list
> > > > [email protected]
> > > > https://lists.sourceforge.net/lists/listinfo/motion-user
> > > > https://motion-project.github.io/
> > > >
> > > > Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
>
> --
> Rainer Dorsch
> http://bokomoko.de/
>
>
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
-------------- next part --------------
An HTML attachment was scrubbed...

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



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

Subject: Digest Footer

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


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

End of Motion-user Digest, Vol 160, Issue 4
*******************************************

Reply via email to