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: Psychedelic Pictures (Andr? H?nsel)
----------------------------------------------------------------------
Message: 1
Date: Tue, 11 May 2021 00:13:11 +0200
From: Andr? H?nsel <an...@webkr.de>
To: "'Motion discussion list'" <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Psychedelic Pictures
Message-ID: <109801d745e9$ad62d170$08287450$@webkr.de>
Content-Type: text/plain; charset="utf-8"
netcam_use_tcp
From: David Powell [mailto:da...@depowell.com]
Sent: Dienstag, 11. Mai 2021 00:03
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Psychedelic Pictures
I'm not sure... how can I tell? I just have netcam_url set to
rtsp://xxx.xxx.xxx.xxx:554/11
Is there another setting that I missed?
David
On 5/10/21 4:37 PM, Mike Wilson wrote:
Are you using tcp for RTSP? If not, I would give that a try.
On Mon, May 10, 2021 at 4:57 PM David Powell <da...@depowell.com
<mailto:da...@depowell.com> > wrote:
I have a strange issue with Motion using RTSP cameras. I have Motion version
4.1.1+git20181002-062a328 running on a Raspberry Pi controlling 3 MJPEG cameras
and 2 RTSP cameras. They all work fine at night with the IR lights and all,
but when the sun comes up, one RTSP camera (and to a lesser extent, the other
RTSP camera) will, over an hour or so, slowly start changing colors until it
looks like a black-light poster from the 70's. Here is an example (hopefully,
if images are allowed on this mailing list).
This is what it should look like:
This is the view after an hour:
If I restart that camera (Action->Restart), it immediately clears up but starts
to degrade again after a few minutes. The other RTSP camera does the same
thing, but to a lesser extent. None of the MJPEG cameras has ever behaved
thusly.
The motion log shows a couple of these per hour of operation for this camera:
[12:nc12:shed] [ERR] [NET] [May 10 15:24:07] netcam_rtsp_handler_reconnect:
Normal resolution: Reconnecting with camera....
I thought I might have just bought a couple of crappy cameras, but even when
the picture is messed up I can stream it with FFPLAY and it looks fine there.
I'm not even sure where to begin trying to fix this. I've checked the
resolution setting and it is correct. Has anyone else seen this behavior?
David
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net <mailto: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 <mailto: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...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 142037 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 210014 bytes
Desc: not available
------------------------------
------------------------------
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 12
********************************************
