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. [SPAM] Fw: new message (Winter-Rabatt)
2. Re: Motion Paused to boot (tosiara)
3. Segmentation fault following re-compile w/ FFmpeg
(Alexander Sprunt)
----------------------------------------------------------------------
Message: 1
Date: Sun, 1 May 2016 12:25:30 +0300
From: Winter-Rabatt <chinati...@gmx.ch>
Subject: [Motion-user] [SPAM] Fw: new message
To: "Motion discussion list" <motion-user@lists.sourceforge.net>,
"Users" <users-boun...@lists.claws-mail.org>
Message-ID: <0000a5320470$3df87e78$d693e9b5$@gmx.ch>
Content-Type: text/plain; charset="us-ascii"
Hello!
You have a new message, please read <http://ianvrees.info/peace.php?uvwr>
Winter-Rabatt
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 2
Date: Fri, 6 May 2016 21:02:44 +0300
From: tosiara <tosi...@gmail.com>
Subject: Re: [Motion-user] Motion Paused to boot
To: Motion discussion list <motion-user@lists.sourceforge.net>
Message-ID:
<cachtdwrzbrpqcwjpvh_4qkeojstaja0vecovhg2w0zokffa...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
imho, this is pretty nice feature. Would be nice to have both conf option
and command line switch to start motion with pasused motion detection
Can you please file a feature request at https://github.com/Mr-Dave/motion?
On Mon, Apr 18, 2016 at 10:14 PM, rUzzine <ruzzin...@gmail.com> wrote:
> Hi,
> it's possible start motion daemon paused?
> I can with api stop detection (paused), it's possible do it at daemon
> start?
> Another question..it's possible enable a privacy mask when necessary or
> i must stop motion?
> Bye.
> ruzzine
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> 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: 3
Date: Sat, 7 May 2016 11:39:29 -0700
From: Alexander Sprunt <aspr...@gmail.com>
Subject: [Motion-user] Segmentation fault following re-compile w/
FFmpeg
To: motion-user@lists.sourceforge.net
Message-ID:
<capabqeu8v6+djxdpbm+1_7vwo951fhz9g5iyvug0ivrttv2...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello,
I'm getting a segmentation fault after re-compiling motion (Mr. Dave's fork
at 9b4c16c, revise version number to 3.4.1) to use FFmpeg.
Some particulars:
- I'm running on a Raspberry Pi Model B, PCB revision 2.0 with Raspbian
Jessie.
- I downloaded the FFmpeg source and compiled it overnight. Many
warnings, but no errors. It runs when passed --version, but I've not done
anything with it standalone beyond that.
- I had previously compiled motion with libav (and it worked, though
some things were missing, which is why I wanted to try FFmpeg).
- In preparation for the re-compile with FFmpeg, I saved my old binary
and ran make clean.
- Configure --with-ffmpeg=$HOME/ffmpeg seemed to indicate it found what
it needed, since I think it output "FFmpeg yes," or something similar.
- I've pasted in the log below. Even at level 9, there's not much there
prior to the crash.
- The second line in the log makes me wonder if libav has snuck in: [0]
[NTC] [ENC] [May 07 11:12:17] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD 3745636
LIBAVFORMAT_BUILD 3744868
- I did not get the "YUV420P" warning with the version compiled with
libav.
I did not remove the various libav packages before the re-compile is that
necessary?
Thanks,
Alex
[0] [NTC] [ALL] [May 07 11:12:17] motion_startup: Using log type (ALL) log
level (ALL)
[0] [NTC] [ENC] [May 07 11:12:17] ffmpeg_init: ffmpeg LIBAVCODEC_BUILD
3745636 LIBAVFORMAT_BUILD 3744868
[0] [NTC] [ALL] [May 07 11:12:17] main: Thread 1 is from
/mnt/nas/ipcam/config/front_camera.conf
[0] [NTC] [ALL] [May 07 11:12:17] main: Thread 1 is device: rtsp://
192.168.10.108:88/videoMain input -1
[0] [NTC] [ALL] [May 07 11:12:17] main: Stream port 8081
[0] [NTC] [ALL] [May 07 11:12:17] main: Waiting for threads to finish, pid:
22328
[1] [NTC] [ALL] [May 07 11:12:17] motion_init: Thread 1 started , motion
detection Enabled
[1] [ALR] [NET] [May 07 11:12:17] netcam_start: Network Camera thread
starting... for url (rtsp://192.168.10.108:88/videoMain)
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Entry netcam_url_parse
data rtsp://192.168.10.108:88/videoMain
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Parse case 0 data
rtsp://192.168.10.108:88/videoMain
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Parse case 1 data rtsp
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Parse case 6 data
192.168.10.108
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Parse case 7 data :88
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Parse case 8 data 88
[1] [DBG] [NET] [May 07 11:12:17] netcam_url_parse: Parse case 9 data
/videoMain
[1] [INF] [NET] [May 07 11:12:17] netcam_start: Netcam_http parameter 'off'
converts to flags: HTTP/1.0: 1 HTTP/1.1: 0 Keep-Alive OFF.
[1] [INF] [NET] [May 07 11:12:17] netcam_start: now calling
netcam_setup_rtsp()
[1] [NTC] [NET] [May 07 11:12:17] netcam_rtsp_open_context: Using tcp
transport
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: Using network
protocols without global network initialization. Please use
avformat_network_init(), this will become mandatory later.
- flag 24
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: Using network
protocols without global network initialization. Please use
avformat_network_init(), this will become mandatory later.
- flag 24
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: SDP:
v=0
o=- 1461127270810773 1 IN IP4 192.168.233.233
s=IP Camera Video
i=videoMain
t=0 0
a=tool:LIVE555 Streaming Media v2014.02.10
a=type:broadcast
a=control:*
a=range:npt=0-
a=x-qt-text-nam:IP Camera Video
a=x-qt-text-inf:videoMain
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:96
a=rtpmap:96 H264/90000
a=fmtp:96
packetization-mode=1;profile-level-id=42001E;sprop-parameter-sets=Z0IAHpWoKA9k,aM48gA==
a=control:track1
m=audio 0 RTP/AVP 0
c=IN IP4 0.0.0.0
b=AS:64
a=control:track2
- flag 40
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: video codec set to:
h264
- flag 48
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: RTP Packetization
Mode: 1
- flag 48
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: RTP Profile IDC: 42
Profile IOP: 0 Level: 1e
- flag 48
[1] [INF] [ENC] [May 07 11:12:17] ffmpeg_avcodec_log: Extradata set to
0xb3b07ae0 (size: 21)!
- flag 48
[1] [INF] [ENC] [May 07 11:12:18] ffmpeg_avcodec_log: hello state=0
- flag 48
[1] [INF] [ENC] [May 07 11:12:18] ffmpeg_avcodec_log: Missing reference
picture
- flag 16
[1] [INF] [ENC] [May 07 11:12:18] ffmpeg_avcodec_log: decode_slice_header
error
- flag 16
[1] [INF] [ENC] [May 07 11:12:18] ffmpeg_avcodec_log: concealing 1200 DC,
1200 AC, 1200 MV errors
- flag 32
[1] [INF] [ENC] [May 07 11:12:21] ffmpeg_avcodec_log: Non-increasing DTS in
stream 1: packet 47 with DTS 22322, packet 48 with DTS 22055
- flag 24
[1] [INF] [ENC] [May 07 11:12:22] ffmpeg_avcodec_log: All info found
- flag 48
[1] [INF] [ENC] [May 07 11:12:22] ffmpeg_avcodec_log: Estimating duration
from bitrate, this may be inaccurate
- flag 24
[1] [INF] [ENC] [May 07 11:12:22] ffmpeg_avcodec_log: detected 1 logical
cores
- flag 48
[1] [INF] [ENC] [May 07 11:12:22] ffmpeg_avcodec_log: Missing reference
picture
- flag 16
[1] [INF] [ENC] [May 07 11:12:22] ffmpeg_avcodec_log: decode_slice_header
error
- flag 16
[1] [INF] [ENC] [May 07 11:12:22] ffmpeg_avcodec_log: concealing 1200 DC,
1200 AC, 1200 MV errors
- flag 32
[1] [DBG] [NET] [May 07 11:12:22] netcam_buffsize_rtsp: expanding buffer
from [0/0] to [0/921600] bytes.
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc:
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc:
****************************************************************
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc: The network
camera is sending pictures in a different
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc: format than
YUV420P. The image sent is being
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc: trancoded to
YUV420P. If possible change netcam
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc: picture format to
YUV420P to possibly lower CPU usage.
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc:
****************************************************************
[1] [NTC] [NET] [May 07 11:12:22] netcam_rtsp_resize_ntc:
[1] [DBG] [NET] [May 07 11:12:22] netcam_buffsize_rtsp: expanding buffer
from [0/0] to [0/921600] bytes.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
------------------------------
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 120, Issue 1
*******************************************
