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: New problem with artifacts (David Powell)


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

Message: 1
Date: Mon, 28 Jan 2019 16:32:14 -0500
From: David Powell <da...@depowell.com>
To: Motion discussion list <Motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] New problem with artifacts
Message-ID: <5cafd4c8-a3f5-7311-d3a2-706f42e24...@depowell.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Thanks MrDave, I think you fixed it.

I wasn't able to try /ffplay/ on the Pi, as it is headless and doesn't 
have a desktop installed anyway.? I spent a while trying to run /ffmpeg/ 
to record a stream but couldn't get the command to work with an RTSP 
URL. So I gave up on that.

Not sure about the two instances thing - I have a cron job that checks 
several programs (including Motion) at 5-minute intervals and starts 
them if they are not running. I double checked it and the logic is 
working. It won't try to start Motion unless it is not running.

What fixed the problem is lowering the reference frame frequency from 50 
to 30, and the frame rate from 25 to 15.? So I guess it still gets an 
I-frame every two seconds but only 15 frames from one to the next (I 
know better than to have the frame rate mismatched, but something must 
have slipped there. I think it was me). ? It's been running for 20 
minutes and still has a clear picture.? It wouldn't go that long before.

David

On 1/28/19 12:37 AM, MrDave wrote:
>
> This looks like a classic decoding issue of not enough information 
> getting to the decoder in Motion.? Couple of things to try:
>
> 1.? Ensure that the test via ffplay is being executed on the pi rather 
> than a different computer.? This ensures that it isn't a network 
> connectivity problem.? e.g? Is the pi using wifi and the other 
> computer using hardwire.
>
> 2.? Try increasing the "I" frame rate from the camera.? There are 
> three types of frames that can be sent from the camera.? The "I" frame 
> is the "full" one upon which all the others depend? in order to decode 
> images.? This will increase the bandwidth over the wire between the 
> camera and Motion.? Make sure to also correlate this with the frame 
> rate that the camera is sending images.? The reason that these issues 
> occur just with the RTSP rather than MJPG is because in the MJPG case, 
> all the images sent from the camera are effectively "I" frames.
>
> 3.? Try slowing the FPS on the camera to be the same as in Motion.
>
> 4.? Try using a lower resolution on the camera and validating that the 
> resolution in Motion exactly matches it.? This would be testing to see 
> if the PI is overloaded.
>
> 5.? Try the highres/passthrough options with a substream from the 
> camera.? This is again trying to determine if the PI is overloaded 
> decoding the 1280 image.
>
> 6.? If the ffplay suggestion in 1 is not an option due to being 
> headless, then try ffmpeg to encode a movie and view the resulting movie.
>
> 7.? It appears that there are two instances of Motion running. Note 
> the middle of the log, it shows Motion starting and not being? able to 
> start MHD (which is usually caused by the port already being in use 
> from another instance).? That section is not preceded by log messages 
> of Motion shutting down.? Two instances trying to decode a 1280 H264 
> image would definitely overload a PI.
>
>
-------------- 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 151, Issue 47
********************************************

Reply via email to