ZoneMinder Forums

Hi,

I'm currently filming a stork's nest.
Recording is on 24/7. I'd like to use the camera's motion detection to have events with motion highlighted.
To my knowledge (as per documentation, https://zoneminder.readthedocs.io/en/la ... er.pl#perl) zmtrigger only triggers the *recording* of events.

I'm looking for a way to set alarm frames or a score for a corresponding event without a recording as that's already happening.

Ideally I'd want use the Montage Review and have the events be highlighted.

Any help by pointing me in the right direction would be much appreciated.

Sounds like you want mocord.
You might want to play with Options->Config->EVENT_CLOSE_MODE as well as Misc->Section length for the cam.

I'll check it out, thanks!

Just to make sure I understand your feedback:

In order to avoid having two recordings for the same event, the regular 24/7 recording as well as the motion triggered one, the settings are to be changed in such a way that the regular recording stops once the motion triggered one begins and vice versa once the motion triggered one ends.

Have a read - https://zoneminder.readthedocs.io/en/st ... nitor.html

Thank your for pointing that out. Mocord is indeed what I'm going for.
I'm essentially trying to offload the CPU work of detecting motion from the Server to the Camera itself.

While it is working (somehow) by using the Monitor in Mocord-mode without having zones for motion detection defined (Thanks @ dougmccrary for bringing that to mind) the CPU load is still comparatively high. I'm hoping to further scale it down by specifically sending a command to have the corresponding event highlighted. with out further straining the server's CPU.

I suppose that's managed using the database. I guess ZoneMinder/Event.pm https://zoneminder.readthedocs.io/en/la ... nt.pm#perl is what I'm going to look into then.

Where does the pearl module fall on the system architecture's map?
https://zoneminder.readthedocs.io/en/la ... m-overview

Update: Having the setup run for a few days, I looked at the uptime logs. It would appear that using Mocord and applying settings to create a new event everytime the external camera sends a trigger increases the cpu load by 30% compared to using the server's motion detection.

Updated Update:
I've used the server's motion detection with 2 zones per monitor and the workload is double of what it was when I used the external device's motion detection.

I'll switch back to using the external detection again as it is beneficial after all.

Topic can be closed.