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: Pi & Logitech C920 (Mr Dave)
2. Re: Feature wish list (Mike Wilson)
----------------------------------------------------------------------
Message: 1
Date: Thu, 24 Sep 2015 17:41:19 -0600
From: Mr Dave <[email protected]>
Subject: Re: [Motion-user] Pi & Logitech C920
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Ok. That is fair. I was indicating it was good because it compiled and
started and that it appeared that only the parameters needed slight
modifications. Seeing now that it still doesn't work for you I'd
agree..it is still bad.
The problem still appears to be the configuration parameters. The
configuration options changed significantly between the 3.12 version and
the versions in apt/trunk and the git version you just compiled. So
when you copied over your previously working version of the
motion.config, it has the old configuration parameter names and we need
to be using the new ones. (This was a change before I arrived). And
not only did the names change but also the parameters to specify. The
option of "input 8" used to mean webcam but in the latest versions, the
appropriate specification is now "input -1". Technically, you could go
through the old configuration file and change them one by one to the new
options and selections but with the extent of the changes, I'd recommend
starting with the motion-dist.conf, renaming it to motion.conf and
making the changes from that starting point.
Dave
On 9/24/2015 1:52 PM, Dave Howorth wrote:
> I'm not having a good day, I'm afraid. I see what you say about it using
> defaults, but in that case the pre-built version works and captures
> video so I'm not sure how it's good that the new version doesn't?
>
> Poking about I see that it wants the config file
> in /usr/local/etc/motion/ so I copied the previously
> working /etc/motion/motion.conf there. Then I edited it so it doesn't
> try to start as a daemon and changed permissions so it was readable, but
> when I then start motion from the command line it says:
>
> $ motion
> [0] [NTC] [ALL] conf_load: Processing thread 0 - config
> file /usr/local/etc/motion/motion.conf
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "despeckle"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "gap"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "max_mpeg_time"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "output_all"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "output_normal"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "output_motion"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "ppm"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_cap_new"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_cap_motion"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_timelapse"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option
> "ffmpeg_timelapse_mode"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "ffmpeg_bps"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option
> "ffmpeg_variable_bitrate"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option
> "ffmpeg_video_codec"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option
> "ffmpeg_deinterlace"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "locate"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "jpeg_filename"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "movie_filename"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option
> "timelapse_filename"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "webcam_port"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "webcam_quality"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "webcam_motion"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "webcam_maxrate"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "webcam_localhost"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "webcam_limit"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "control_localhost"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option
> "control_html_output"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "sql_log_image"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "sql_log_snapshot"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "sql_log_mpeg"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "sql_log_timelapse"
> [0] [ALR] [ALL] conf_cmdparse: Unknown config option "sql_query"
> [0] [NTC] [ALL] motion_startup: Using default log level (NTC) (6)
> [0] [NTC] [ALL] motion_startup: Motion Unofficial-Git-UNKNOWN Started
> [0] [NTC] [ALL] motion_startup: Logging to syslog
> [0] [NTC] [ALL] motion_startup: Using default log type (ALL)
> [0] [NTC] [ALL] motion_startup: Using log type (ALL) log level (NTC)
> [0] [NTC] [ALL] main: Thread 1 is from /usr/local/etc/motion/motion.conf
> [0] [NTC] [ALL] main: Thread 1 is device: /dev/video0 input 8
> [0] [NTC] [ALL] main: Stream port 0
> [0] [NTC] [ALL] main: Waiting for threads to finish, pid: 7984
> [1] [NTC] [ALL] motion_init: Thread 1 started , motion detection Enabled
> [1] [NTC] [VID] vid_v4lx_start: Using videodevice /dev/video0 and input
> 8
> [1] [NTC] [VID] v4l2_get_capability:
> ------------------------
> cap.driver: "uvcvideo"
> cap.card: "HD Pro Webcam C920"
> cap.bus_info: "usb-bcm2708_usb-1.2"
> cap.capabilities=0x04000001
> ------------------------
> [1] [NTC] [VID] v4l2_get_capability: - VIDEO_CAPTURE
> [1] [NTC] [VID] v4l2_get_capability: - STREAMING
> [1] [ERR] [VID] v4l2_select_input: Unable to query input 8.
> VIDIOC_ENUMINPUT, if you use a WEBCAM change input value in conf by -1:
> Invalid argument
> [1] [NTC] [VID] vid_v4lx_start: Using V4L1
> [1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 1
> items
> [1] [ERR] [ALL] motion_init: Error capturing first image
> [1] [NTC] [ALL] image_ring_resize: Resizing pre_capture buffer to 3
> items
> [1] [ERR] [ALL] motion_loop: Video device fatal error - Closing video
> device
> [1] [NTC] [VID] vid_close: Closing video device /dev/video0
> [1] [WRN] [ALL] motion_loop: Retrying until successful connection with
> camera
> [1] [NTC] [VID] vid_v4lx_start: Using videodevice /dev/video0 and input
> 8
>
> The last stanza then repeats every few seconds until I terminate the
> program. I don't understand what I've done to make it not recognize the
> configuration options.
>
> Cheers, Dave
>
>
>
> On Wed, 2015-09-23 at 19:11 -0600, Mr Dave wrote:
>> OK. That is good. It looks like it is up, found your camera, started
>> working, detected motion. Then quit cleanly. The issue now appears
>> that it is within the parameters. From the log posted, it appears that
>> it is still using the defaults (see the resolution reported when it is
>> looking at the PIX format). So you may want to check that you changed
>> the right file. (Look where it installed via the messages from the make
>> install step). Also check all the other parameters like target_dir and
>> possibly try it in non-daemon mode first for testing /debugging
>>
>> Dave
>>
>>
>>
>>
>> On 9/23/2015 1:52 PM, Dave Howorth wrote:
>>> I tried autoreconf -f and it built without error. I edited the init
>>> script to use /etc/local/bin/motion for DAEMON and changed motion.conf
>>> to be 1280x720 and restarted the service.
>>>
>>> Sadly, it detected motion and exited but did not create any image or
>>> video files:
>>>
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] motion_startup:
>>> Using default log level (NTC) (6)
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] motion_startup:
>>> Motion Unofficial-Git-UNKNOWN Started
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] motion_startup:
>>> Logging to syslog
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] motion_startup:
>>> Using default log type (ALL)
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] motion_startup:
>>> Using log type (ALL) log level (NTC)
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] main: Thread 1 is
>>> device: /dev/video0 input -1
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] main: Stream port 0
>>> Sep 23 20:36:02 raspberrypi motion: [0] [NTC] [ALL] main: Waiting for
>>> threads to finish, pid: 7205
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [ALL] motion_init: Thread
>>> 1 started , motion detection Enabled
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] vid_v4lx_start:
>>> Using videodevice /dev/video0 and input -1
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_get_capability:
>>> #012------------------------#012cap.driver: "uvcvideo"#012cap.card: "HD
>>> Pro Webcam C920"#012cap.bus_info:
>>> "usb-bcm2708_usb-1.2"#012cap.capabilities=0x04000001#012------------------------
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_get_capability:
>>> - VIDEO_CAPTURE
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_get_capability:
>>> - STREAMING
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_select_input:
>>> name = "Camera 1", type 0x00000002, status 00000000
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_select_input: -
>>> CAMERA
>>> Sep 23 20:36:02 raspberrypi motion: [1] [WRN] [VID] v4l2_select_input:
>>> Device doesn't support VIDIOC_G_STD
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> Config palette index 17 (YU12) doesn't work.
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> Supported palettes:
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> (0) YUYV (YUV 4:2:2 (YUYV))
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> 0 - YUV 4:2:2 (YUYV) (compressed : 0) (0x56595559)
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> (1) H264 (H.264)
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> 1 - H.264 (compressed : 1) (0x34363248)
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> (2) MJPG (MJPEG)
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format:
>>> 2 - MJPEG (compressed : 1) (0x47504a4d)
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_set_pix_format
>>> Selected palette YUYV
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID]
>>> v4l2_do_set_pix_format: Testing palette YUYV (352x288)
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID]
>>> v4l2_do_set_pix_format: Using palette YUYV (352x288) bytesperlines 704
>>> sizeimage 202752 colorspace 00000008
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> found control 0x00980900, "Brightness", range 0,255
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> #011"Brightness", default -8193, current 128
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> found control 0x00980901, "Contrast", range 0,255
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> #011"Contrast", default 57343, current 128
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> found control 0x00980902, "Saturation", range 0,255
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> #011"Saturation", default 57343, current 128
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> found control 0x00980918, "Power Line Frequency", range 0,2
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> #011"Power Line Frequency", default 2, current 2
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> found control 0x00980913, "Gain", range 0,255
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] v4l2_scan_controls:
>>> #011"Gain", default 57343, current 0
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [VID] vid_v4lx_start:
>>> Using V4L2
>>> Sep 23 20:36:02 raspberrypi motion: [1] [NTC] [ALL] image_ring_resize:
>>> Resizing pre_capture buffer to 1 items
>>> Sep 23 20:37:29 raspberrypi motion: [1] [NTC] [EVT] event_new_video FPS
>>> 14
>>> Sep 23 20:37:29 raspberrypi motion: [1] [NTC] [ALL] motion_detected:
>>> Motion detected - starting event 1
>>> Sep 23 20:37:29 raspberrypi motion: [1] [NTC] [ALL] motion_loop: Thread
>>> exiting
>>> Sep 23 20:37:29 raspberrypi motion: [1] [NTC] [VID] vid_close: Closing
>>> video device /dev/video0
>>> Sep 23 20:37:29 raspberrypi motion: [0] [NTC] [ALL] main: Threads
>>> finished
>>> Sep 23 20:37:30 raspberrypi motion: [0] [NTC] [ALL] main: Motion
>>> terminating
>>>
>>>
>>> Also $ lsb_release -a
>>> No LSB modules are available.
>>> Distributor ID: Debian
>>> Description: Debian GNU/Linux 7.0 (wheezy)
>>> Release: 7.0
>>> Codename: wheezy
>>>
>>>
>>> Cheers, Dave
>>>
>>> On Tue, 2015-09-22 at 20:12 -0600, Mr Dave wrote:
>>>> I have just checked this on my PI and it appears to function correctly.
>>>>
>>>> Can you tell us the image that you are using so we can test it?
>>>>
>>>> Also, you may want to check the motion_guide.html and INSTALL files
>>>> distributed with the source code. I have updated them to have current
>>>> building/installing instructions as well as all the new and different
>>>> options. It may be as simple as using the
>>>>
>>>> autoreconf -f
>>>>
>>>> option instead of the sequence that you've indicated.
>>>>
>>>> MrDave
>>>>
>>>> On 9/22/2015 5:54 PM, Mr Dave wrote:
>>>>> Yes, that is definitely broken. Sorry about that. I'm pretty sure
>>>>> that this change is only on the unstable branch which is in testing.
>>>>> Can you switch to the master branch and test it again? The following
>>>>> switches your sources over to master which doesn't have the offending
>>>>> code but does have the changes I think you are looking for.
>>>>>
>>>>> git checkout master
>>>>> autoreconf
>>>>> ./configure
>>>>> make
>>>>> make install
>>>>>
>>>>>
>>>>> MrDave
>>>>>
>>>>>
>>>>> On 9/22/2015 4:14 PM, Dave Howorth wrote:
>>>>>> Thanks for that. I've just downloaded it and am trying to compile it but
>>>>>> I ran into something I don't understand. It's the first time I tried to
>>>>>> compile something on the pi. I ran:
>>>>>>
>>>>>> $ autoheader
>>>>>> $ autoconf configure.ac > configure
>>>>>> $ sudo apt-get install libjpeg-dev
>>>>>>
>>>>>> but when I
>>>>>> $ ./configure
>>>>>> it says
>>>>>>
>>>>>> checking for gcc... gcc
>>>>>> checking whether the C compiler works... yes
>>>>>> checking for C compiler default output file name... a.out
>>>>>> checking for suffix of executables...
>>>>>> checking whether we are cross compiling... no
>>>>>> checking for suffix of object files... o
>>>>>> checking whether we are using the GNU C compiler... yes
>>>>>> checking whether gcc accepts -g... yes
>>>>>> checking for gcc option to accept ISO C89... none needed
>>>>>> checking how to run the C preprocessor... gcc -E
>>>>>> checking for grep that handles long lines and -e... /bin/grep
>>>>>> checking for egrep... /bin/grep -E
>>>>>> checking for ANSI C header files... yes
>>>>>> checking for sys/types.h... yes
>>>>>> checking for sys/stat.h... yes
>>>>>> checking for stdlib.h... yes
>>>>>> checking for string.h... yes
>>>>>> checking for memory.h... yes
>>>>>> checking for strings.h... yes
>>>>>> checking for inttypes.h... yes
>>>>>> checking for stdint.h... yes
>>>>>> checking for unistd.h... yes
>>>>>> checking minix/config.h usability... no
>>>>>> checking minix/config.h presence... no
>>>>>> checking for minix/config.h... no
>>>>>> checking whether it is safe to define __EXTENSIONS__... yes
>>>>>> checking for gcc... (cached) gcc
>>>>>> checking whether we are using the GNU C compiler... (cached) yes
>>>>>> checking whether gcc accepts -g... (cached) yes
>>>>>> checking for gcc option to accept ISO C89... (cached) none needed
>>>>>> checking for Darwin... no
>>>>>> checking for *BSD... no
>>>>>> checking for gcc... (cached) gcc
>>>>>> checking whether we are using the GNU C compiler... (cached) yes
>>>>>> checking whether gcc accepts -g... (cached) yes
>>>>>> checking for gcc option to accept ISO C89... (cached) none needed
>>>>>> checking threads... yes
>>>>>> checking for sdl... no
>>>>>> checking for libjpeg-turbo... skipping
>>>>>> checking for libjpeg-mmx... skipping
>>>>>> checking for jpeg_set_defaults in -ljpeg... yes
>>>>>> ./configure: line 5287: syntax error near unexpected token `FFMPEG,'
>>>>>> ./configure: line 5287: ` PKG_CHECK_MODULES(FFMPEG, libavutil
>>>>>> libavformat libavcodec libswscale, HAVE_FFMPEG=yes)'
>>>>>>
>>>>>> A syntax error makes me think something is broken somewhere but I'm not
>>>>>> sure whether I've caused the problem?
>>>>>>
>>>>>> Cheers, Dave
>>>>>>
>>>>>>
>>>>>> On Fri, 2015-09-18 at 09:15 +0300, ?ydr?nas Urbonas wrote:
>>>>>>> Hey, try compiling latest Mr-Dave fork, it contains a fix for
>>>>>>> C910/C920 cameras
>>>>>>> https://github.com/Mr-Dave/motion/commits/unstable
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Sep 17, 2015 at 9:03 PM, Dave Howorth <[email protected]>
>>>>>>> wrote:
>>>>>>> Hello,
>>>>>>> I'm trying to set up motion with a Logitech HD Pro
>>>>>>> Webcam C920
>>>>>>> connected
>>>>>>> to a Raspberry PI. It sort of works but not properly so I'd
>>>>>>> appreciate
>>>>>>> some pointers.
>>>>>>> The Pi has raspberrypi 3.2.27+ #250 PREEMPT
>>>>>>> motion is Version 3.2.12
>>>>>>> I'm sshed to the pi; there's no display on it. I
>>>>>>> have motion
>>>>>>> set up as a
>>>>>>> service started on boot.
>>>>>>> I have two issues that I'd like to resolve:
>>>>>>> (1) motion happily captures video when
>>>>>>> there is motion and
>>>>>>> records an
>>>>>>> avi file and a bunch of jpegs. But it only does this if I
>>>>>>> leave the
>>>>>>> width and height at their default. If I set 1280 x 720 or
>>>>>>> 1920
>>>>>>> x
>>>>>>> 1080 resolution, nothing gets captured.
>>>>>>> I have tried running cheese and that is able to show
>>>>>>> high-resolution
>>>>>>> video, so I know its not a hardware problem. There's a lot of
>>>>>>> stuff
>>>>>>> in /var/log/messages but I don't understand it:
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [0] Motion
>>>>>>> thread 1
>>>>>>> restart
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] cap.driver:
>>>>>>> "uvcvideo"
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] cap.card: "HD Pro
>>>>>>> Webcam C920"
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] cap.bus_info:
>>>>>>> "usb-bcm2708_usb-1.2"
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1]
>>>>>>> cap.capabilities=0x04000001
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] - VIDEO_CAPTURE
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] - STREAMING
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] Config palette index
>>>>>>> 8
>>>>>>> (YU12)
>>>>>>> doesn't work.
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] Supported palettes:
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] 0: YUYV (YUV 4:2:2
>>>>>>> (YUYV))
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] 1: H264 (H.264)
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] 2: MJPG (MJPEG)
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] Selected palette YUYV
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] Test palette YUYV
>>>>>>> (1280x720)
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] Using palette YUYV
>>>>>>> (1280x720)
>>>>>>> bytesperlines 2560 sizeimage 1843200 colorspace 00000008
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] found control
>>>>>>> 0x00980900,
>>>>>>> "Brightness", range 0,255
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] #011"Brightness",
>>>>>>> default -8193,
>>>>>>> current 128
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] found control
>>>>>>> 0x00980901,
>>>>>>> "Contrast", range 0,255
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] #011"Contrast",
>>>>>>> default 57343,
>>>>>>> current 128
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] found control
>>>>>>> 0x00980902,
>>>>>>> "Saturation", range 0,255
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] #011"Saturation",
>>>>>>> default 57343,
>>>>>>> current 128
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] found control
>>>>>>> 0x00980913,
>>>>>>> "Gain", range 0,255
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] #011"Gain", default
>>>>>>> 57343,
>>>>>>> current 0
>>>>>>> Sep 17 18:56:41 raspberrypi motion: [1] Resizing pre_capture
>>>>>>> buffer to 1
>>>>>>> items
>>>>>>> Sep 17 18:57:03 raspberrypi motion: [1] Resizing pre_capture
>>>>>>> buffer to 3
>>>>>>> items
>>>>>>> (2) motion exits if I try to access the
>>>>>>> web stream at
>>>>>>> http://pi:8081/.
>>>>>>> I'm not too concerned about this issue because it's not
>>>>>>> something I
>>>>>>> intend to use once it all works.
>>>>>>> Cheers, Dave
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> Motion-user mailing list
>>>>>> [email protected]
>>>>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>>>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>> ------------------------------------------------------------------------------
>>>> 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
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>
>> ------------------------------------------------------------------------------
>> 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
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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, 25 Sep 2015 02:00:17 +0000
From: Mike Wilson <[email protected]>
Subject: Re: [Motion-user] Feature wish list
To: Motion discussion list <[email protected]>
Message-ID:
<caaveucp1g5wayitlryec3pqnmbwhxi6pbn-w4vt1p2pjyvt...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
For #3 I always just use the on_event scripts to curl or something to
notify other processes.
On Thu, Sep 24, 2015 at 6:50 PM Jim Dodgen <[email protected]> wrote:
> Improvements I would like to see in motion
>
> 1. A way to only have motion detection during certain times.
>
> 2. area_detect improvements lets say 6x6 instead of 3x3. also I'm not
> convinced that it is currently working.
>
> 3. some kind of IPC to notify other processes of movement.
>
> any ideas?
>
>
> *Jim Dodgen*
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> 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...
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 112, Issue 24
********************************************
