Capture freezes after about 8 seconds

Forum for questions and support relating to the 1.34.x releases only.
Post Reply
Posts: 1
Joined: Mon Jul 20, 2020 1:31 pm

Capture freezes after about 8 seconds

Post by matludlam » Mon Jul 20, 2020 2:18 pm

Hi, I have recently set up ZM with one camera. I am using Modect.

The capture starts ok, but after a random number of seconds (about 8 ) the picture freezes from the camera (including the camera time stamp) but the ZM time stamp keeps going. The audio keeps being recorded.

After about 5 more seconds ZM decides that nothing is happening, and stops recording (which makes sense).

I am using a source type of FFMPEG as a source type and everything else seems ok.

When I look into the logs for this time slot i get:

Code: Select all

ERR Unable to send raw frame 2 : Broken pipe	zm_eventstream.cpp	816
ERR Unable to send raw frame 21: Broken pipe	zm_eventstream.cpp	816
ERR Unable to send stream frame: Broken pipe	zm_eventstream.cpp	833
... lots more "Unable to send stream frame" ... then
WAR Got no frame. returning nothing		zm_ffmpeg_input.cpp	234
... lots more of the above
There are a total of 35 errors and warning related to the one record event.

I am guessing that this is a buffer / configuration thing, so a pointer would be appreciated.

If I go into live view within ZM then it just works, there is no freeze.

Other info:
Camera is a SV-B07W VR-1080PS-HX, I used this page to get it running:
I am using 24 bit colour with 1920x1080 pixels
Store of JPEGs is disabled, Video write is h.264 passthrough
Image buffer size is 100, warmup is 25, per event is 10, post event is 10, Stream replay image buffer is 5 and alarm count is 1

Help really appreciated.

Posts: 220
Joined: Mon May 11, 2020 4:32 pm

Re: Capture freezes after about 8 seconds

Post by burger » Thu Jul 23, 2020 4:17 pm

Could be a few things. Start by lowering FPS, and resolution. You didn't mention what CPU / motherboard you are using. ARM will have trouble with 1920x1080, esp. higher FPS.

Some cameras have poor compatibility. That is always a possibility.

w/RPI it's common to see capture start, then fail after resources run out. Either CPU / memory. In this case, you'd lower FPS & resolution.

You can test w/ffmpeg and VLC from any computer on the network. That is a good way to quickly verify stream compatibility and also that the parameters are correct.

Does it work with record, and not modect? Do you have aggressive zones setup? You can try libVLC, also.
fastest way to test streams:
ffmpeg -i rtsp://<ipaddress>:554/path output.mp4
from terminal, and run through paths on ispydb or in zm hcl

If you are new to security software, read this:

Post Reply

Who is online

Users browsing this forum: Dimontr and 1 guest