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: Gray glitching but only one of of two identical cameras
      (Barry Martin)


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

Message: 1
Date: Fri, 28 May 2021 08:40:38 -0500
From: Barry Martin <barry3mar...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] Gray glitching but only one of of two
        identical cameras
Message-ID: <afb9afca-654e-b78a-46e7-42b348378...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"


Hi Roger/All who are following this!


Just to keep up-to-date: At about 4 o?clock (1600) yesterday afternoon I 
reset my Pi4?s gpu_mem from 512MB to 256 MB. Seems counter-intuitive to 
decrease the graphic memory for video problems but maybe I was starving 
the CPU. Anyway, at the time of the update Camera1?s video feed (to the 
monitor) had been frozen for a couple of hours. Camera2?s video feed was 
chugging along happily. Both cameras were sending motion-triggered 
recordings to the NSA.


Did a reboot to update the memory configuration. Since then things seem 
to be working as they should ? have had previous fixes works for a while 
so not celebrating yet. Both cameras seem to be holding at 5 fps, though 
have seen a one to two second video freeze; might try cutting gpu_mem a 
little more. (The gpu_mem in the Pi4 works differently from earlier 
versions; if somebody reading this is using a Pi3 might make things worse.)



I semi-figured out logging to it?s own file: in motion.conf I have 
*log_file /mnt/NSA320/Unit_1/%m-%d/motion.log* ==> to the server in the 
basement, Unit #1?s partition (clever name, huh?!). The what I wanted it 
to do was to a daily file, hence the month and date variables but 
they?re not working; work elsewhere. Figuring the log_file field doesn?t 
input variable but rather a literal. Works in movie_filename, which is a 
?type: string? as is log_file, per 
https://motion-project.github.io/motion_config.html . OTOH might not be 
necessary to have separate/daily logs: relatively short. I had looked at 
syslog which was constantly updating and HUGE.


Suggestions? It also looks like motion.log with the default level of 6 
only logs at boot start, though I haven?t done a motion restart.


..I just took a closer look at motion.log: it /is/ updating! The file 
was created yesterday and here the ?Modified? column is showing 
?yesterday? as opposed to the time of the last entry a few minutes ago. 
Just assumed (yeah: I know!) when I saw ?yesterday? it hadn?t been altered.


Barry




-------------- 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 179, Issue 34
********************************************

Reply via email to