ZoneMinder Forums

A few weeks ago my server was running ZM 1.36.25 on Fedora 36. I've got 8 cores, 16GB RAM with 5 cameras and everything was great, pretty low CPU usage. Then I upgraded to Fedora 37 which also upgraded ZM, first to 1.36.32 and then I later went to 1.36.33. Since the upgrade, all 5 of my zmc ...

That works, thanks!

I have a video clip recorded last night that contains motion but it wasn't detected. I'm sure my zone settings aren't properly tuned for the type of motion I'm expecting in this zone. But I'm not sure how to fix it, short of trial and error (making changes and then waiting for motion to happen again ...

That worked, thanks!

I moved my ZM installation to a new server and did a dump/restore of the database but didn't bring over the old files. Really I just wanted to restore the configuration & source definitions. This worked fine, but now it's confused about the disk space usage. There was an earlier post in the forums ...

Thanks, that's pretty nice and I might try it. I started working on a different approach though, using zmbenchmark as a guide. I load two images (successive frames from a capture), manually configure a monitor, and call DetectMotion. It works surprisingly well and you can configure any of the zone ...

So I'm trying to tune my zone settings for better motion detection. I have some false-positive clips where motion was detected but shouldn't have been... and vice versa, where there was motion that ZM didn't flag. I know I need to adjust my zone settings but it's not always obvious which values to ...

1. What does "too sensitive" mean? Here are the settings I use for all zones (I think most of these are the defaults): Units: Pixels Min/Max Pixel Threshold: 60 / blank Filter Width/Height: 3 / 3 Min/Max Alarmed Area: 1000 / blank Min/Max Filtered Area: 3 / blank Min/Max Blob Area: 3 / blank Min/Max ...

Hi there, I just upgraded from 1.36.5 to 1.36.11 and updated the database. Good news: the "Error writing trailer Error number 67 occurred" messages are now gone (these were previously logged at the end of every capture). And the CPU usage per monitor is reduced by about 1/3, so that's good too! But ...

I already have LOG_LEVEL_FILE = Debug and LOG_FFMPEG turned on and the logs above are all that I have. Can you tell me which other options should be set?

Earlier today I wiped my database and reinstalled 1.36.8 from scratch. This is with just one camera, on a quad-core machine with 8GB doing almost nothing else. The camera is a Foscam bullet cam with these settings: Stream Type: FHD Mode Resolution: 720P Bit Rate: 1M Frame Rate: 5 Key Frame Interval ...

I just replaced that server last night and I started from scratch, clean install of F34, created a new database and didn't import anything. It's running 1.36.8 clean out of the box. I have the same issues on all three servers but the monitor crashes most frequently on this one. If you browse this ...

I'm a longtime ZM user, running three sites now. All with Foscam cameras (mostly wired), two on Fedora and one CentOS. I'm having a whole lot of video issues since upgrading to 1.36: Short segments due to monitors crashing frequently "Unable to free up older packets" error (even with analysis frames ...

Thanks, it should have a strong signal in that location but I'll get out there with the phone and double check.

I'm using 1.34.22 on CentOS 8, just one outdoor camera so far, a Foscam wifi bullet camera . The connection is wifi but the camera is powered (not battery). I've been having a lot of issues with the camera cutting out or freezing during recording, or sometimes just when opening the stream on the ...