ZoneMinder Forums

Are you sure that ZM agrees that there is motion? Turn on saving alarm frame jpegs and see what it thinks. ZM's default zone settings were design when the images were 640x480 or less. I find that I have to make them drastically more sensitive. Start by choosing1% or less for all the min alarm pixel ...

A big shoutout to all of our contributors, but a special one to Mike Dussault who discovered that we weren't using our SSE or otherwise optimised blending routines. On a 4K 10fps camera stream this one fix reduces cpu use by 60% when doing motion detection.

1.36.7 cuts cpu for motion detection dramatically. Give it a whirl.

never.

I have now released 1.36.7.

Changes since 1.36.6 - Add an example fail2ban rule - Email sending: fix html emails when using ZM_NEW_MAIL_MODULES. Improve debugging reduce Info logging - fix bug in zms causing failed image loading in zmNinja and anywhere a low maxfps was specified - Updated italian translation - add missing cal...

They thing here is 4k.

decoding a 4K cam takes 50% cpu (on my system). Adding motion detection, etc. No way. Forget it. Drop it to 1080p. Even 1080p is ridiculous.

I have a discord server as well. Paid support access only. Discord is cool, really intuitive. For voice chat. But we are minimising the channels because we do not have the attention bandwidth. If other people want to create discord channels for discuss ZM, go right ahead. The ZM developers won't be ...

I introduced a bug unfortunately. I'll be releasing 1.36.7 today to fix it.

You might try adding a maxfps=30 to the url which might work around it for now.

Just run mysqltuner and do what it says.

Remember, the disk in question here is the system disk, where mysql stores it's work files and the actual zm db. Not where we store the video.

Wouldn't work on h265, as frames depend on both future and past frames.

You re-encode to a lower frame rate.

We COULD just not record frames, but as discussed, the result might not be pleasant. Might be interesting to try though. I would think we would want to keep all keyframes though.

I have included this in the ZM distro under misc/fail2ban.rules

Assuming most of your events aren't archived, an archived index won't help much. You might want to look at db tuning... At the end of the day, because we are sorting we will have to look at all 340k rows... I can't think of any reasonable way of making this filter performant. You should decide how m...

This ended up being a big one. Lots of fixes. I suspect there will be at least 1 more release in the 1.36 series, but not too many more. Going for a shorter release cycle so we can bring you the needed features. With cameras going > 1080p, it has become clear that we cannot continue decoding these h...

# Changes since 1.36.5 - Fix Archive FTP .zip filename not including monitor name. Fixes #3304 - Correct the size of the Longitude and Latitude fields. Fixes #3311 - Optimise API by optionally not loading the Frames from db table - Handle the case when the monitor doesn't exist more gracefully and n...

Apparently I didn't finish this release notification, so here it is.... # Changes since 1.36.5 - fix logout modal not appearing when too many sessions in sessions table - fix remote monitors not restarting when Function = None leaving them running. - fixes to onvif zooming #3295 - fix EndTime handli...