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: Watchdog timeout (tosiara)
2. Re: movie passthrough FPS (Mike Wilson)
3. Re: Watchdog timeout (Kevin)
----------------------------------------------------------------------
Message: 1
Date: Fri, 8 May 2020 08:28:15 +0300
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Watchdog timeout
Message-ID:
<cachtdwrdd8ajjlszwnk4q+oovo_j6ve2zjjeffu4tm9qu+d...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
You did not mention that motion crashes. Can you explain the gdb log you
attached?
And try to run "ffplay -f video4linux2 /dev/video0" on your motion box -
does it play?
On Fri, May 8, 2020 at 1:15 AM Kevin <kmg...@bigpond.com> wrote:
> Sadly, no change.
>
>
>
> # rpi-eeprom-update
>
> BCM2711 detected
>
> BOOTLOADER: up-to-date
>
> CURRENT: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
>
> LATEST: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
>
> FW DIR: /lib/firmware/raspberrypi/bootloader/critical
>
> VL805: up-to-date
>
> CURRENT: 000137ad
>
> LATEST: 000137ad
>
>
>
> See attachments for other "stuff".
>
>
>
> On 2020 M05 7, Thu 15:26:30 AEST tosiara thou dist spake thusly:
>
> > Could you try to update to mmotion 4.3.1 as well as latest Rpi firmware?
>
> > There were similar issues with USB and Rpi in the past and usually
> firmware
>
> > update helped
>
>
>
>
> _______________________________________________
> 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: 2
Date: Fri, 8 May 2020 02:33:17 -0400
From: Mike Wilson <knobby2...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] movie passthrough FPS
Message-ID:
<CAAVeUCq4LZVuuSOB3=srbvn5mpvztndbai161xwpmemrpmw...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Pass through is exactly what it says. It takes the raw feed from your
camera and writes it to disk. If you want to change the frame rate you
either need to change the camera stream or not use pass through.
On Thu, May 7, 2020 at 6:14 PM csspcmotion <mot...@curtissystemssoftware.com>
wrote:
> Can any body answer how to do following I posted over month ago?
>
>
> On 4/1/20 11:09 AM, csspcmotion wrote:
>
> I am using the netcam_highres option with movie_passthrough on.
>
> My cameras are set to 10 FPS and during some weathers conditions would
> like to slow the collection to much slower collection perhaps 4 FPS ...
> although attempting this with a lower framerate does not reflect this new
> framerate on the movie_passthrough created movies and motion ends up
> syncing to match the higher fps (10) which is not what I want during such
> weather or related (crazy motion) which can change in a matter of minutes.
>
> Is there a way to change that collection rate without restarting the given
> motion's affected camera(s) which has situation of lost frames and other
> related context data during a restart, while at the same time not requiring
> to change the FPS within the camera itself?
>
> I have looked at the code but don?t yet recognize a good spot to make such
> needed movie_passthrough/ffmpeg alterations. It may also be acceptable to
> just toss any frames beyond the lower framerate ? at least disk space can
> be minimized.
>
>
>
>
>
> _______________________________________________
> 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: Fri, 08 May 2020 16:42:40 +1000
From: Kevin <kmg...@bigpond.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Watchdog timeout
Message-ID: <6a3b7621-3719-40e4-9967-9b2b2b3ca...@bigpond.com>
Content-Type: text/plain; charset="utf-8"
1) gdb: Motion crashed so I hoped that gdb would provide a useful backstack
trace, obviously it hasn't.
2) ffmpeg: the command you gave me does not work:
error: XDG_RUNTIME_DIR not set in the environment.
Could not initialize SDL -
(Did you set the DISPLAY variable?)
All my Pi' are headless. However, if it means anything, after Motion has
finished a recording, I use ffmpeg to create a timelapse version. The command I
use is;
ffmpeg -y -i $file -filter:v setpts=0.3*PTS -an $output_dir/${output_name}" ?
BTW: If it will help, I'm willing to try and compile the source and use gdb to
track the error - but I'd need your help to know where to place break points.
I'm pretty busy right now so this would not be until some time next week. It
could also take a while for me to compile the source as all my experience is
with Fedora and dnf/yum.
-------- Original Message --------
From: tosiara <tosi...@gmail.com>
Sent: Fri May 08 15:28:15 GMT+10:00 2020
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Watchdog timeout
You did not mention that motion crashes. Can you explain the gdb log you
attached?
And try to run "ffplay -f video4linux2 /dev/video0" on your motion box -
does it play?
On Fri, May 8, 2020 at 1:15 AM Kevin <kmg...@bigpond.com> wrote:
> Sadly, no change.
>
>
>
> # rpi-eeprom-update
>
> BCM2711 detected
>
> BOOTLOADER: up-to-date
>
> CURRENT: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
>
> LATEST: Thu 16 Apr 17:11:26 UTC 2020 (1587057086)
>
> FW DIR: /lib/firmware/raspberrypi/bootloader/critical
>
> VL805: up-to-date
>
> CURRENT: 000137ad
>
> LATEST: 000137ad
>
>
>
> See attachments for other "stuff".
>
>
>
> On 2020 M05 7, Thu 15:26:30 AEST tosiara thou dist spake thusly:
>
> > Could you try to update to mmotion 4.3.1 as well as latest Rpi firmware?
>
> > There were similar issues with USB and Rpi in the past and usually
> firmware
>
> > update helped
>
>
>
>
> _______________________________________________
> 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
------------------------------------------------------------------------
------------------------------------------------------------------------
_______________________________________________
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...
------------------------------
------------------------------
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 167, Issue 6
*******************************************
