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: Changing resolution when motion detected (Laurent MAHE)
2. Re: Motion Version 4.01 process end (Colin Law)
3. Re: Motion Version 4.01 process end (Riccardo Stronati)
----------------------------------------------------------------------
Message: 1
Date: Wed, 9 Nov 2016 16:38:48 +0000
From: Laurent MAHE <[email protected]>
Subject: Re: [Motion-user] Changing resolution when motion detected
To: Motion discussion list <[email protected]>
Message-ID:
<CADZhf+UVm2ge15=WoHYSV3RzWEKCsL=o3oexkV=duags35+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
I got all previous info from a post by Mr-Dave:
https://github.com/Motion-Project/motion/issues/123
Look for his post on Aug 12th.
When I run the command ffmpg stops after 30 sec
On 8 November 2016 at 18:04, Dave Fournier <[email protected]> wrote:
> Thanks for the reply. That is really useful. I have been investigating the
> command outside of motion to see how it works for me. First thing one
> finds
> with ffmpeg is that there are so many command line options it is difficult
> to find
> docs on them. I have not found
>
> -rtsp_transport tcp
>
> anywhere. The command works without it, but with perhaps more errors
> reported. Also the -t 30 writes a file for 30 seconds, but afterward
> ffmpeg keeps
> running. Is there an option to have it exit after writing the avi file.
>
> Thanks,
>
> Dave
>
> On Sun, Nov 6, 2016 at 3:35 PM, Laurent MAHE <[email protected]>
> wrote:
>
>> Hi Dave,
>>
>>
>> Set your movie length to 25 sec:
>> max_movie_time 25
>>
>> Set ffmpeg to record on motion detection:
>> on_event_start ffmpeg -rtsp_transport tcp -i "rtsp://xxx.xxx.xxx/11" -c
>> copy -t 30 "fullpath/moviename.avi"
>>
>> This way the movies overlap by 5 sec so you don't miss anything if motion
>> is longer than 25sec, BUT you tend to miss the first ~2 sec of motion
>> detection since there is no pre-capture
>> You also don't get any OSD from Motion, just raw video (I use my own cam
>> OSD for that)
>>
>> However if your camera has a mic, you get the sound too
>>
>> Laurent
>>
>> On 6 November 2016 at 22:17, Dave Fournier <[email protected]>
>> wrote:
>>
>>> I have some new cameras for which I was able to identify the URL's
>>> for both high and low resolution feeds. High res is
>>>
>>> rtsp://xxx.xxx.xxx/11
>>>
>>> low res is
>>>
>>> rtsp://xxx.xxx.xxx/12
>>>
>>> I wonder if there is a way to switch from low resolution to high
>>> resolution when motion is detected.
>>>
>>> Thanks,
>>>
>>> Dave
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Developer Access Program for Intel Xeon Phi Processors
>>> Access to Intel Xeon Phi processor-based developer platforms.
>>> With one year of Intel Parallel Studio XE.
>>> Training and support from Colfax.
>>> Order your platform today. http://sdm.link/xeonphi
>>> _______________________________________________
>>> Motion-user mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>>
>>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> 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: 2
Date: Wed, 9 Nov 2016 20:47:14 +0000
From: Colin Law <[email protected]>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <[email protected]>
Message-ID:
<CAL=0glum3b61gq61yz2fwd7ehv+nee5zh7yg6vz_k12a5tu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Ricardo, did you have a chance to try my suggestion?
Colin
On 6 November 2016 at 21:57, Colin Law <[email protected]> wrote:
> On 6 November 2016 at 20:02, Riccardo Stronati <[email protected]>
> wrote:
>
>>
>> this is the motion.service
>> [Unit]
>> Description=Motion daemon
>> After=local-fs.target network.target
>>
>> [Service]
>> PIDFile=/var/run/motion.pid
>> ExecStart=/usr/bin/motion
>> Type=simple
>> StandardError=null
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>>
> I am not an expert in systemd but I do not believe that PIDFile is
> appropriate for Type=simple. Normally PIDFile is used with type forking and
> indicates the pid value of the process that is to be considered the main
> process of the service, whereas type=simple means that the process started
> by execstart (ie motion) is the main process and will continue to run. I
> think it is possible that systemd is looking for the process in pidfile and
> killing motion when it does not appear. I suggest removing the PIDFile
> line and see what happens. After removing that line run
> sudo systemctl daemon-reload
> which tells systemd to re-read the service files then
> sudo systemctl start motion
> and see if it is any better.
>
> Colin
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Thu, 10 Nov 2016 09:42:02 +0100
From: Riccardo Stronati <[email protected]>
Subject: Re: [Motion-user] Motion Version 4.01 process end
To: Motion discussion list <[email protected]>
Message-ID:
<cabhf65e8o9sk4+fnbt6k8hdz26--gqbztvoyqyjojedmpvu...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm sorry, I didn't try I was off for work.
I'll try this evening, thanks you again.
Riccardo
2016-11-09 21:47 GMT+01:00 Colin Law <[email protected]>:
> Ricardo, did you have a chance to try my suggestion?
>
> Colin
>
> On 6 November 2016 at 21:57, Colin Law <[email protected]> wrote:
>
>> On 6 November 2016 at 20:02, Riccardo Stronati <[email protected]>
>> wrote:
>>
>>>
>>> this is the motion.service
>>> [Unit]
>>> Description=Motion daemon
>>> After=local-fs.target network.target
>>>
>>> [Service]
>>> PIDFile=/var/run/motion.pid
>>> ExecStart=/usr/bin/motion
>>> Type=simple
>>> StandardError=null
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>>
>> I am not an expert in systemd but I do not believe that PIDFile is
>> appropriate for Type=simple. Normally PIDFile is used with type forking and
>> indicates the pid value of the process that is to be considered the main
>> process of the service, whereas type=simple means that the process started
>> by execstart (ie motion) is the main process and will continue to run. I
>> think it is possible that systemd is looking for the process in pidfile and
>> killing motion when it does not appear. I suggest removing the PIDFile
>> line and see what happens. After removing that line run
>> sudo systemctl daemon-reload
>> which tells systemd to re-read the service files then
>> sudo systemctl start motion
>> and see if it is any better.
>>
>> Colin
>>
>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> 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...
------------------------------
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
------------------------------
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
End of Motion-user Digest, Vol 126, Issue 10
********************************************
