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: Corrupted Images (Ken Cox)
----------------------------------------------------------------------
Message: 1
Date: Sun, 22 Mar 2020 22:00:13 -0600
From: Ken Cox <kenc...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Corrupted Images
Message-ID:
<cap4ecbmg0iavyprxg+xo2scbqdgjzhwz3vr34dwscnrvk36...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
It seems like it's solved. I reduced the frame rate to 2 / sec in both the
camera and Motion. I have not seen a corrupt image since.
Thanks,
Ken
On Fri, Mar 20, 2020, 7:35 AM Colin Law <clan...@gmail.com> wrote:
> On Fri, 20 Mar 2020 at 12:53, Ken Cox <kenc...@gmail.com> wrote:
> >
> > Lots of good advice here. It will take me a bit to work through each
> piece. A couple of comments for now:
> >
> > ffplay returns an authentication error. Any ideas why that would be? I
> do have the cameras secured with username/password, but motion works when
> these are passed in the URL. ffplay does not.
> >
> > I'm not supper jazzed about lowering the resolution. Part of the reason
> I purchased these cameras was to get a clearer view of an intruder's face
> at a distance. If it comes down to that, I think my preference would be to
> keep things as they are and just deal with an occasional bad image.
> >
>
> Alternatively see if you can drop the frame rate significantly in the
> camera. It is not so beneficial doing it on the PC as it still has to
> decode every frame even if motion is not going to use it. That should
> not affect your ability to identify faces.
>
> Colin
>
> > Thanks!
> > Ken
> >
> >
> > On Fri, Mar 20, 2020 at 3:33 AM manu.kemppainen--- via Motion-user <
> motion-user@lists.sourceforge.net> wrote:
> >>
> >> Same happened with my camera. Either lower part of the picture was
> corrupted (typically green) whe RTSP I-frames were lost or similar to the
> example when RTSP I-frame was received but RTSP sub-frames were either
> missing or corrupted. Tosiara gave good test:ffplay to see if the frames
> are corrupted also there - I bet they are.
> >> It seems with my camera that camera is not capable for full resolution
> encoding with plenty of changes in the image i.e. despite of the network
> capability video is never going to work properly.
> >> What you can try:
> >> - Use camera jpeg output url if one exist (my camera supports this but
> image resolution is lower)
> >> - Configure camera RTSP output resolution lower
> >> - Decrease the camera RTSP framerate (I got best results with 4 fps)
> >> - Try to adjust camera bitrate (up or down)
> >> - Try VBR/CBR for camera RTSP
> >> - Check your framerate in motion.conf (currently rate is 100 which is
> optimal for USB cameras)
> >>
> >> Bottleneck can also be your network. What is the network
> speed/topology/load?
> >>
> >> With ffmpeg I can force ffmpeg to only process I-frames from RTSP (i.e.
> discard sub-frames).
> >> Can I somehow force motion to only use I-frames from RTSP stream?
> >>
> >> --
> >> Manu
> >>
> >>
> >> -------- Alkuper?inen viesti --------
> >> L?hett?j?: tosiara <tosi...@gmail.com>
> >> P?iv?m??r?: pe 20. maalisk. 2020 klo 10.57
> >> Vastaanottaja: Motion discussion list <
> motion-user@lists.sourceforge.net>
> >> Aihe: Re: [Motion-user] Corrupted Images
> >>
> >> And I can see there are decoding issues in your motion log:
> >>
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 411 packets
> >> [1:nc1] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [1:nc1] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 31 packets
> >> [1:nc1] [ERR] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: error while
> decoding MB 104 65, bytestream -5
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 20 packets
> >> [1:nc1] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [1:nc1] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 22 packets
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 14 packets
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 12 packets
> >> [2:nc2] [ERR] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: error while
> decoding MB 30 48, bytestream -5
> >> [1:nc1] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [1:nc1] [NTC] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: RTP: missed
> 87 packets
> >> [1:nc1] [ERR] [ENC] [Mar 17 14:52:22] ffmpeg_avcodec_log: error while
> decoding MB 109 66, bytestream -7
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:23] ffmpeg_avcodec_log: max delay
> reached. need to consume packet
> >> [2:nc2] [NTC] [ENC] [Mar 17 14:52:23] ffmpeg_avcodec_log: RTP: missed
> 246 packets
> >> [2:nc2] [ERR] [ENC] [Mar 17 14:52:23] ffmpeg_avcodec_log: left block
> unavailable for requested intra4x4 mode -1
> >> [2:nc2] [ERR] [ENC] [Mar 17 14:52:23] ffmpeg_avcodec_log: error while
> decoding MB 0 23, bytestream 7496
> >>
> >> It is either network issue or cpu resource
> >>
> >> On Fri, Mar 20, 2020 at 10:51 AM tosiara <tosi...@gmail.com> wrote:
> >>
> >> One thing to try is to view the same stream using ffplay. Do you see
> the same artifacts randomly? Does ffplay log decoding errors?
> >>
> >> On Fri, Mar 20, 2020 at 10:45 AM walexand <w.alexan...@gmx.de> wrote:
> >>
> >> IMHO this is not a corrupted image. It is a compression artifact because
> >> of the moving person in the room. Try a lower resolution. 2688x1520
> >> pixels is too much for a motion jpeg stream.
> >>
> >> Alex
> >>
> >> On 19.03.20 21:42, manu.kemppainen--- via Motion-user wrote:
> >> > Hi Ken,
> >> >
> >> > Your image seems to be 4mp (2688 x 1520) and it seems some frames
> have dropped
> >> > from the stream.
> >> > I have experienced similar problems with high resolution cameras.
> >> > I did not manage to get RTSP out of the camera even when I connected
> ethernet
> >> > cable directly between PC and Cam.
> >> > My solution was to use the jpeg url for my camera.
> >> >
> >> > What is your frame rate in the camera?
> >> > What is your bitrate in the camera?
> >> >
> >> > --
> >> > Manu
> >> >
> >> >
> >> > -------- Alkuper?inen viesti --------
> >> > L?hett?j?: Ken Cox <kenc...@gmail.com>
> >> > P?iv?m??r?: to 19. maalisk. 2020 klo 22.05
> >> > Vastaanottaja: Motion discussion list <
> motion-user@lists.sourceforge.net>
> >> > Aihe: Re: [Motion-user] Corrupted Images
> >> >
> >> > I tried to respond but apparently my message did not go through
> because the
> >> > log file is rather large. I put all of this in a google drive
> folder with a
> >> > shared link:
> >> >
> https://drive.google.com/open?id=1FJ6ZmxCe1VFjhL_IfNBcIjusjy11I40i
> >> > An example of one of my corrupt images, my three config files,
> and the full
> >> > log from one day are included
> >> >
> >> > I appreciate you helping me with this!
> >> >
> >> > Thanks,
> >> > Ken
> >> >
> >> >
> >> > On Wed, Mar 18, 2020 at 1:34 AM tosiara <tosi...@gmail.com
> >> > <mailto:tosi...@gmail.com>> wrote:
> >> >
> >> > Yes, please provide an example of an image
> >> > And also would be nice to see your full config and full log
> >> > It could be also an insufficient resource for decoding
> >> > If this is really a network issue, you could try to change
> camera
> >> > settings, like CBR over VBR or reduce I-framw interval
> >> >
> >> > On Tue, Mar 17, 2020 at 11:57 PM Ken Cox <kenc...@gmail.com
> >> > <mailto:kenc...@gmail.com>> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > I'm experiencing frequent image corruption. When it
> happens, it
> >> > looks like it's blending 2 images with the changed
> pixels some weird
> >> > ghostly looking mixture of the two images. Often I can
> tell there is
> >> > an outline of a person there, but the details are a
> corrupted mess.
> >> > I can provide an example if it helps. I did find in the
> >> > configuration help page that without netcam_use_tcp set
> to on
> >> > "rtsp/rtmp images are frequently corrupted and result in
> many false
> >> > positive values and images that appear to be smeared."
> Mine was
> >> > already set to on, so I tried off on a whim. It did not
> solve this
> >> > issue, but did indeed add some additional smearing
> regions in many
> >> > images that seem to be unrelated to the motion.
> >> >
> >> > Has anyone else seen this issue? Any ideas whats wrong
> or how to fix it?
> >> >
> >> > Thanks,
> >> > Ken
> >> > _______________________________________________
> >> > 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
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >>
> >> _______________________________________________
> >> 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
>
>
> _______________________________________________
> 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 165, Issue 23
********************************************
