Re: 1.26.4 Upgrade Failure
Posted: Mon Feb 10, 2014 2:21 am
That "smearing" is caused by missing RTP packets, specifically those missing from an I frame. Unfortunately, occasional dropped packets are a fact of life, and hen RTP is carried over the UDP transport layer, there is no retransmission of the missing data. FFMPEG does a good job of concealing lost packets when they occur during a P frame, but when part of an I frame is missing there's nothing the decoder can do.
Forcing the use of TCP as the transport layer with the "?tcp" suffix is great if your camera supports it (some do not). Otherwise, you're stuck with these smeared frames triggering lots of false motion detection alarms.
One possible workaround might be to do the motion detection on the camera itself if the camera supports it (and if the camera can be made to work with zmtrigger.pl).
The alternative is to spend a little more money and buy a camera which can do MJPEG streaming over TCP.
Forcing the use of TCP as the transport layer with the "?tcp" suffix is great if your camera supports it (some do not). Otherwise, you're stuck with these smeared frames triggering lots of false motion detection alarms.
One possible workaround might be to do the motion detection on the camera itself if the camera supports it (and if the camera can be made to work with zmtrigger.pl). The alternative is to spend a little more money and buy a camera which can do MJPEG streaming over TCP.