ZoneMinder Forums

I think that the missing update is actually in /usr/share/zoneminder/db/zm_update-1.37.23.sql.

If you visit https://launchpad.net/~iconnor/+archive ... tate=built you should be able to get a copy of the .deb for any build you like.

I'm not sure that this project would be all that useful to ZoneMinder since it is written in Node.js.

I don't know if this will be helpful, but I have had some success using the zmonvif-events project. I've used it successfully with my Hikvision doorbell camera to detect motion with the passive IR sensor. The project needed a couple of changes to work properly with ZoneMinder authentication. It ...

Mine's working again too. Thanks Isaac!

Since I updated to zoneminder_1.35.26~20210417125040-bionic, motion detection has not worked at all. I see no error messages in the log. Everything else works normally. I updated to zoneminder_1.35.26~20210417163214-bionic and I see the same thing. I did a fresh install on my test machine with the ...

I've definitely been able to downgrade from 1.35.18 to 1.35.16 without a problem. The only problem I have had in the past is finding the packages. If your system keeps old packages around then they should be in /var/cache/apt/archives. If you are running motion detection then each zmc should be ...

I was able to get my cameras working thanks to some help from the folks on the Slack channel. Apparently, zmc is queuing all frames in between keyframes. My misbehaving cameras were set to use H.264+ encoding which @iconnor says has a very high keyframe interval. Once I turned off H.264+ memory ...

That thread is specifically for new features in 1.35.*. I don't think that it is the appropriate place for this discussion. I'm hoping that this thread will get some attention.

If I can get some kind of handle on what is going on, I will make an issue post on the ZoneMinder github.

I answered before I had done much testing. I see it now. Some zmc processes are using enormous amounts of memory, even in Monitor mode.

Some monitors use a reasonable amount and some use a stupid amount. I cannot figure out what causes the difference.

Have you read this post about the updates from @iconnor?

It looks like shared memory is no longer used to communicate between zmc and zma. This means that most of what you have allocated for ImageBufferCount is just wasted. It is recommended that you set it to 2.

That's got it!

I still have to use 1.35.5~20200616165015-bionic because of the rotation problem I reported in github.

With 1.35.5~20200722224526-bionic, I'm now seeing alarm frames generated with proper images, but they don't show motion outlines. They show a red-outlined frame, but blobs are not outlined.

I'm still seeing this problem with 1.35.5~20200721160555-bionic.

I just upgraded to 1.35.5~20200714143209-bionic and some things are broken. I can get video from most of my cameras, but my camera that is rotated 90 degrees shows mostly misplaced scan lines with an occasional flash of the non-rotated image. The montage on the web interface and on ZmNinja is broken ...