Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

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
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: I guess I simply don't understand... (Dougie Nisbet)
   2. Re: I guess I simply don't understand... (tosiara)
   3. Re: I guess I simply don't understand... <SOLVED> (John B)


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

Message: 1
Date: Thu, 12 Mar 2020 09:57:20 +0000
From: Dougie Nisbet <dou...@katsura.uk>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] I guess I simply don't understand...
Message-ID: <018a97ed-c31d-0fc1-40ac-a9f734821...@katsura.uk>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

I had an old Axis 2100 for a while and had problems. I think the 
netcam_url entry can be a problem and finding out what to put there is a 
headache. My archiveed post is here:
https://sourceforge.net/p/motion/mailman/message/36629531/
and may have some useful pointers.


On 12/03/2020 03:05, JB wrote:
> # The full URL of the network camera stream.
> netcam_urlhttp://192.168.X.X


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

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

Message: 2
Date: Thu, 12 Mar 2020 12:23:39 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] I guess I simply don't understand...
Message-ID:
        <cachtdwtj4wn9ojtn4nmrs_vnqh+jdk-2rmtyakbehr9ma_k...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Before setting up motion, first make sure you can play your Axis camera
using ffplay:

ffplay rtsp://192.168.X.X/whatever/is/correct/for/axis

On Thu, Mar 12, 2020 at 12:14 PM Dougie Nisbet <dou...@katsura.uk> wrote:

> I had an old Axis 2100 for a while and had problems. I think the
> netcam_url entry can be a problem and finding out what to put there is a
> headache. My archiveed post is here:
> https://sourceforge.net/p/motion/mailman/message/36629531/
> and may have some useful pointers.
>
>
> On 12/03/2020 03:05, JB wrote:
>
> # The full URL of the network camera stream.
> netcam_url http://192.168.X.X
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> 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...

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

Message: 3
Date: Thu, 12 Mar 2020 06:05:15 -0500
From: John B <yona...@riseup.net>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] I guess I simply don't understand...
        <SOLVED>
Message-ID: <20200312060515.76c55482@ACAB.TOSIAR>
Content-Type: text/plain; charset=US-ASCII

On Wed, 11 Mar 2020 22:05:48 -0500
JB <yona...@riseup.net> wrote:

>   Hi guys,
> 
>   For 5 hours now I've been trying to get motion to work with my Axis M1113 IP
>   cam.
> 
>   I have it connected to my router that I flash a few times a year with 
> DD-WRT.
> 
>   It took me long enough to get the setup *in* the cam itself to work right, 
> as
>   I kept changing the wrong things to be able to log into it as root and user,
>   and that was frustrating enough, but is finally done.
> 
>   No matter what I do to my motion.conf file, when I try to look at the
>   stream(?) of the camera *with motion*, the logs keep telling me things like:
> 
> Failed to read first camera header - giving up for now. Vid start:netcam 
> failed
> to open.
> 
>   If I simply put the IP of the cam into my browser, I get the Axis 'Live
> view', which shows a picture and the camera streaming to it, and of course I
> can also click on the 'setup' to do things in that.
> 
>   I've read, over and over and over ad nausea and just can't get the *motion*
>   thing to see the stream.
> 
>   For instance...the url I put into the browser to get to Axis's 'Live view'
>   stuff, is 192.168.X.X and I have it 'set up' in that so that I can go http 
> or
>   https.
> 
>   When I open Motion with 'http://localhost:8080/' it opens motion just fine,
>   and there's even a 'square' where a picture/video should be streaming, but 
> it
>   has the little broken picture icon in the upper left corner and nothing is
>   seen.
> 
>   I've honestly tried to understand the rtsp thing and the http stuff, but 
> it's
>   just knocking my ass for a loop and making me feel dumber than a Pet Rock.
> 
>   Here is my nice and short motion.conf, I just had no need really for all the
>   'extra' stuff it could have if I felt like it. I have the log file set at
>   level 4 so I could just stick to reading any errors, as having to try and
>   weed through 3KB of other stuff every time I changed something in the
>   motion.conf file just took me longer and longer and confused me even more...
> 
> # Rename this distribution example file to motion.conf
> #
> # This config file was generated by motion 4.2.2
> # Documentation:  /usr/share/doc/motion/motion_guide.html
> #
> # This file contains only the basic configuration options to get a
> # system working.  There are many more options available.  Please
> # consult the documentation for the complete list of all options.
> #
> 
> ############################################################
> # System control configuration parameters
> ############################################################
> 
> # Start in daemon (background) mode and release terminal.
> daemon on
> 
> # 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 /home/john/motion_logs/motion_logs
> 
> # Level of log messages [1..9] (EMG, ALR, CRT, ERR, WRN, NTC, INF, DBG, ALL).
> log_level 4
> 
> # Target directory for pictures, snapshots and movies
> target_dir /home/me/motion_cam
> 
> # 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 auto_brightness=2
> 
> # The full URL of the network camera stream.
> netcam_url http://192.168.X.X
> 
> netcam_userpass XX:XXXX
> 
> # 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 800
> 
> # Image height in pixels.
> height 600
> 
> # Maximum number of frames to be captured per second.
> framerate 25
> 
> # 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
> 
> ############################################################
> # Motion detection configuration parameters
> ############################################################
> 
> # Always save pictures and movies even if there was no motion.
> emulate_motion off
> 
> # Threshold for number of changed pixels that triggers motion.
> threshold 1500
> 
> # Noise threshold for the motion detection.
> ; noise_level 32
> 
> # Despeckle the image using (E/e)rode or (D/d)ilate or (l)abel.
> despeckle_filter EedDl
> 
> # Number of images that must contain motion to trigger an event.
> minimum_motion_frames 1
> 
> # Gap in seconds of no motion detected that triggers the end of an event.
> event_gap 60
> 
> # The number of pre-captured (buffered) pictures from before motion.
> pre_capture 3
> 
> # Number of frames to capture after motion is no longer detected.
> post_capture 2
> 
> ############################################################
> # Script execution configuration parameters
> ############################################################
> 
> # Command to be executed when an event starts.
> ; on_event_start value
> 
> # Command to be executed when an event ends.
> ; on_event_end value
> 
> # Command to be executed when a movie file is closed.
> ; on_movie_end value
> 
> ############################################################
> # Picture output configuration parameters
> ############################################################
> 
> # Output pictures when motion is detected
> picture_output off
> 
> # File name(without extension) for pictures relative to target directory
> picture_filename %Y-%m-%d---%T-%q
> 
> ############################################################
> # Movie output configuration parameters
> ############################################################
> 
> # Create movies of motion events.
> movie_output on
> 
> # Maximum length of movie in seconds.
> movie_max_time 60
> 
> # The encoding quality of the movie. (0=use bitrate. 1=worst quality, 
> 100=best)
> movie_quality 85
> 
> # Container/Codec to used for the movie. See motion_guide.html
> movie_codec mpeg4
> 
> # File name(without extension) for movies relative to target directory
> movie_filename %Y-%m-%d---%T-%q
> 
> ############################################################
> # Webcontrol configuration parameters
> ############################################################
> 
> # Port number used for the webcontrol.
> webcontrol_port 8080
> 
> # Restrict webcontrol connections to the localhost.
> webcontrol_localhost on
> 
> # Type of configuration options to allow via the webcontrol.
> webcontrol_parms 2
> 
> ############################################################
> # Live stream configuration parameters
> ############################################################
> 
> # The port number for the live stream.
> stream_port 8081
> 
> # Restrict stream connections to the localhost.
> stream_localhost on
> 
> ##############################################################
> # Camera config files - One for each camera.
> ##############################################################
> ; camera /etc/motion/camera1.conf
> ; camera /etc/motion/camera2.conf
> ; camera /etc/motion/camera3.conf
> ; camera /etc/motion/camera4.conf
> 
> ##############################################################
> # Directory to read '.conf' files for cameras.
> ##############################################################
> ; camera_dir /etc/motion/conf.d
> 
> 
>   If anyone hasn't slapped their forehead and muttered about another idiot
> could please try to help me out, I'd be grateful as can be.
> 
>   I'm 100% disabled and literally just had to move and now I'm in a pretty bad
>   area and *must* have a camera watching my motorcycle (believe it or not it's
>   easier on my back pain than sitting in a car or p/u truck) as it's the only
>   transportation I own.
> 
>   I have an el cheap-o logitech C610 I think it is, and tried it, but the
>   pictures/videos were awful and really wouldn't be of much help if I had to
>   show them to the cops, and also skipped frames here and there as all it 
> could
>   run was 10fps. I spent what little I had left after the move, leaving myself
>   with nothing left for the month for gas money, my pain meds or food (luckily
> I had a little more than a months worth of food still at the old place that I
>   brought with me!)...and the cam only cost $30 with S&H. :(
> 
>   Anyway, if you need more information to work with, let me know precisely 
> what
>   you need and how to go about getting it if at all possible.
> 
>   Thanks, everyone, for any help with this.
> 
>   Take care, stay warm and dry!
> 
>       JB
> 
> 

  Okay folks, a fellow Motion user found the solution for me! Here is what I got
  in an e-mail (not sure why it didn't make it to the list here as it has my
  e-mail address *and* the address to the list. Huh)...

"The crux of the problem is this snippet in the config: netcam_url
http://192.168.X.X
Motion needs the direct stream for the image; you are giving motion the
address of the whole interface (with login button, axis logo etc).
The right url could be mentioned in the admin interface, or at the very
least could be extracted from your browser on a page where you see the
picture.
Unfortunately I don't have an axis handy for testing, but going by the
manual (https://www.axis.com/files/manuals/um_m1113e_46770_en_1206.pdf) you
should try netcam_url rtsp://192.168.X.X/axis-media/media.amp

Hope this helps,"

  The reason I never tried this, is because I apparently got seriously confused
  by the *axis* guide, not the Motion guide. Let me explain...

  In the Axis guide, I kept seeing things about 'AXIS Media Control (AMC)
AXIS Media Control (AMC) in Internet Explorer in Windows is the recommended
method of accessing live video from the Axis product.'

  This made me think that if I saw what Joris said to try "axis-media/media.amp"
  in the URL it was for Windows and I wouldn't be able to see or use it since
  I'm using Linux.

  Now that that is 'fixed' though, I'm not too sure this camera is any better
  than the cheap-o logitech USB webcam I have. When I brought up the stream in
  Motion in my browser, it was slower than molasses in January. I can't remember
  if it was similar with the webcam. Yet, when I bring up the Axis app 'Live
  View', and open a little window to see how it's streaming, it's doing quite
  well and almost real-time fast (as in keeping up pretty good when I wave my
  hand in front of the camera).

  Is this 'normal' or did I simply get the wrong cam or too old of a cam and the
  webcam is actually better?

  Both cables for the cam are cat 6a and no longer than 10 feet. My system is an
  AMD FX-8350 and my graphics is a GeForce GTX 960 so I don't think I should be
  having any problems with video speed I'm guessing.

  Anyway, I'll give it a try first at just monitoring my room for a while and
  then look at some of the videos it captured to see how they turned out.

  Thanks very, very much to everyone who jumped in to try and help and
  especially to Joris who got it figured out. This really is a good list with
  good people and I'm glad I've been with it for this past decade or so (has it
  really been that long that Motion has been around? Neat!!).

  Everyone take care, stay warm and dry,

        JB




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



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

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


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

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

Reply via email to