ZoneMinder Forums

ZM isn't deleting my 24/7 recordings; they're all sitting there in the filesystem which is why I need that crontab triggered script to stop it filling up. I store the 24/7 high-res mp4's in a different storage area (#2) on a mounted filesystem and tell zmaudit to only deal with storage area #1 which ...

I've not really noticed before but yes... mine does the same thing - shows a max of 146 recordings for the injected captures. At a guess it'll be something to do with the 'unofficial' way zmrecord is injecting SQL records; but that's just a guess. However, I don't run zmaudit on my Big RAID of 24/7 ...

I don't have any cameras with audio capability... which will make replicating your issue tricksy :( However, this does sound like an ffmpeg related problem. The output files should not be 0 bytes. The MySQL error about CaptureFPS also points towards ffmpeg as the status output from ffmpeg is what's ...

I said I'd upload my final script and I have in a thread on the User Contribution section of the forum.

See here viewtopic.php?f=9&t=29137

I've been using Asker's most excellent motion detection stuff for ZM (https://github.com/pliablepixels/zmeventnotification) to 'declutter' ZM with dramatic effects. Of course, Asker's zmeventnotification extension's prime purpose is to filter events for actual objects of interest before sending you ...

That's a much cleaner solution than my Python hackery. It seems to be working well.

I've created a pull request for the small changes to objectconfig.ini and zm_event_end.sh. Please excuse me if the whole fork/push/pullrequest thing isn't right - not something I've really used before.

Never having written a line of Python code in my life :shock: but this seems to work. Lives just before the line "# end of matched file" # record number of objects removed by almostmatches if g.config['write_image_to_zm'] == 'yes' and args['monitorid'] and pre_pastdetections > 0 and post ...

What do you mean when object detection matches a previous detection? I have "match_past_detections=yes" in my objectconfig.ini. I've only seen this for single events with motion detection called once. I do see quite a lot of "27/02/20 14:36:21.272223 zmeventnotification[10335].DBG [main:827 ...

Good News(TM). After exhaustive testing of some 17 hours :) that seems to have resolved the issue. Thank you. There is one related, minor, problem for events where the object detection matched a previous detection. In this situation, zmeventnotification quite rightly does not update the Notes with ...

Installed and monitoring. Will report back.

FWIW, please do leave the Storage Path as $5 - a belt'n'braces check never goes amiss and it's only an fstat(2) call for bash; probable more efficient than a string compare with "*detected:*"

In short.... dunno about 34885. My zm_event_end.sh deleted it as there was no "detected:" string. I've changed my zm_event_end.sh so it'll save a copy of the event data before asking ZM to delete it and I am seeing quite a few (four since I made the change 15 mins ago) deleted events that have an ...

For the moment let's not conflate two unrelated issues into one. Sorry - getting over enthusiastic :) It's sooooo close to being brilliant! The changes I made were specifically to make sure the detection text was not overwritten for long running events where ZM added motion notes after the ...

Ahh... yes - just found other events that zmeventnotification didn't 'see' before I upgraded to 5.9. MariaDB [zm]> select Id,MonitorId,StartTime,EndTime,Notes from Events where Notes NOT like "%detected:%" and StorageId < 2 ...

Sadly, version 5.9 seems to be missing events. I have an event 34541 on Monitor 5 at 10:01:23 to 10:01:31 that, obviously, shows up in the zma logs but there's no sign of it in the zmeventnotification log :( "grep 34541 zm/zmeventnotification.log" produces nothing. Events 34550 and 34552 were ...

Oh dear - that isn't nice

For my purposes, would it be possible for zmeventnotification to pass the original detection string to zm_event_end.sh ? (as arg 5 so as not to break existing uses).