Pre-Motion Recording when using AXIS Profiles as Triggering Event

General
1

This question doesn’t quite seem to fit in the MIP forum as I am not attempting to use the SDK itself to affect a change.

My client has a few Milestone systems and each one manages anywhere from 350 - 650 cameras each. Because of this, I cannot use the Milestone built-in motion detection as it will overwhelm the server resources, so I am using the built-in Axis Object Analytics instead. The Axis Object Analytics also allows me to specify what in the scene I am focusing on to detect motion (people, cars, bicycles, etc.).

So, here is the issue… I defined in each camera an Analytics event (Profile 1) for the AXIS Optimizer plug-in to monitor as a triggering event (Rising/Falling). I have also declared the two related events in the Events tab of each camera:(CameraApplicationPlatform/ObjectAnalytics/Device 1Scenario 1(Object Analytics 1) Rising (CameraApplicationPlatform/ObjectAnalytics/Device 1Scenario 1(Object Analytics 1) Falling

I also created a custom Rule:

“Perform an action on CameraApplicationPlatform/ObjectAnalytics/Device1Scenario1 (Object Analytics: Scenario 1) Rising
from All Cameras - Record Motion
start recording immediately on the device on which event occurred

Perform stop action on CameraApplicationPlatform/ObjectAnalytics/Device1Scenario1 (Object Analytics: Scenario 1) Falling
from All Cameras - Record Motion
stop recording 15 seconds after”

The rule works in that it triggers and records the action, but I need it to record both 15 seconds before and 15 after the action. I am getting the 15 seconds after, but the rule will not allow me to change the “start recording immediately” to 15 seconds so that I get the pre-event recording. I do have the Record tab settings enabled, complete with the 15 seconds pre-buffer setting specified. My client is a city and their policy states that their CCTC system must record starting 15 seconds before the triggering event.

Am I doing something wrong? Is there another way I need to do this?

2

Ok, the issue is resolved. Being unfamiliar with the pre-buffering option in the rule, I did not realized that in order to specify “pre-” recording, I had to enter a negative number. I must say though, I think this would have been far less confusing had the prompt read Select time before” instead of just “Select time”. I would have to say that the majority of video recording and access control systems don’t allow the use of negative numbers as an input value and that’s the mindset that led to my mistake.

1 Like