ZoneMinder Forums

Ok. this shouldn't be that hard to solve, and we have the code to phpbb.

So first step is research others having the problem, and if no solution found, we can at least prevent reusing old posts. And filtering urls out of location.

Honestly I wouldn't go more than 4 years old, unless you really have no budget. At some point the electricity cost negates the initial savings.

The technology is out there, but has not been integrated into zoneminder. To do so requires ai facial recognition, and video re-encoding, which means you will need a pretty good gpu. What is your budget? This feature will not be cheap from any of the incumbent VMS providers. It may be affordable to ...

I seem to recall there was some issue with the jpeg stream that zm didn't like.

viewtopic.php?p=128536&hilit=esp#p128536

You can look at the code.

https://github.com/ZoneMinder/zoneminde ... .cpp#L1260

Just pushed a fix for it. The issue was that it is trying to set permissions for monitors that have been deleted.

Just pushed a possible fix. Packages building.

Just pushed a fix to not list deleted monitors.

You mention errors logged, but havn't shared what those errors are.

Another thought here is that logrotate runs at midnight every night and will cause the monitor to start/restart capture. Shouldn't result in green, but maybe that's it. You can trigger it anytime using sudo zmdc.pl logrot

In 1.37 I have been debugging long standing issues that only occur on some cameras. What I have determined is that the clock on the camera jumps back (or forward) in time. This is basically because the internal clock is really bad, and ntp is making a correction every hour. Some cameras are set to u...

New packages are building. 1.37.54 should have the necessary db updates to fix this.

It should be. The packet queue should maintain a buffer of that size + keyframe. SOmetimes it can't and there will be a log entry about it.

The onvif setup is taking over 20 seconds. So zmwatch is killing the camera before it can even try to capture.
We will need to move the code around so that onvif doesn't delay capture.

In the meantime, increase your Options->System->WATCH_MAX_DELAY

Todays build should fix it.