The feature Record on motion allows a quick and simple configuration of an alarm recording due to motion. When motion is detected, video is recorded. When motion stops, video recording stops. (this is unlike an alarm scenario where video is recorded for a set duration whether there is motion or not.)
Record on motion does not replace a complete alarm scenario (see Alarms). We recommend converting your motion alarms to Record on Motion.
You must have either server-side or camera-side motion detection enabled first prior to enabling record on motion in this screen.
Also, the Idle timer or Dead time value in the server-side/camera-side motion detection screens is ignored with Record on Motion.
Record on Motion differs from the early versions of Ocularis 5 in that if enabled, video will be recorded when there is motion only. When motion stops, recording stops. In Ocularis 5.1, the only option for motion recording was where video was recorded for a set duration whether motion continued or not. While this form of motion detection recording is still available in v5.2 and later, Record on Motion is much more efficient and makes better use of storage space. It also eliminates the need for alarm scenarios which frees up resources on the core. Video recorded using Record on Motion will be categorized as alarm recording. With Record on Motion, you can set pre and post buffers on a camera-by-camera basis. Multi-camera configuration is also supported and you can enable Record on Motion when adding cameras using the Device Finder.
Record on Motion may be used with either camera side or server side motion detection. It also supports the use of motion detection regions inside an image.
In order to enable Record on Motion, either camera side or server side motion detection must be enabled first. The following examples will be discussed:
3. Choose Record On Motion under 'Image Storage'.
4. Enable Record on Motion by selecting Yes from the drop-down list.
5. Pre and post buffer is defaulted to 3 seconds for each. Modify these values if desired.
Notice that the system recognizes that Camera side or Server side motion detection is enabled. You must first enable it prior to saving this screen.
6. Click Save to save these settings.
That's it! You are done!. Alarm scenarios need not be configured. The video that is recorded due to motion will be coded in red on the Kinetic Timeline in Ocularis Client.
Multi-camera configuration is supported with Record on Motion. Remember that either camera side or server side motion detection must be enabled first. This example is going to use server side motion detection.
1. In Ocularis Recorder Manager, select the checkbox next to each you wish to configure.
2. Click the Edit tool.
Notice that the configuration tab is labeled 'Multiple IP cam...' to indicate that multiple cameras will be configured.
Choose Record On Motion under 'Image Storage'.
Click the checkbox next to Enable Record on Motion.
Select Yes from the drop-down list.
If you want to apply the same Pre and post buffer settings to the cameras, click the corresponding checkboxes to enable the field entry and set the desired change. Otherwise, the defaults of 3 seconds each will be applied.
Click Save to save these settings on all cameras.
When using the Device Finder Tool to add cameras, you may also enable server side motion detection and Record on Motion. recording.
Now these cameras will have server side motion detection activated and Record on Motion enabled. You should still review and if necessary modify the Sensitivity and Threshold settings for each camera in the Server Side Motion Detection screen.
If you have what was considered 'Basic' motion detection recording configured on your v5.1 system (i.e. where the Record on Motion drop-down was set to 'Yes' but no alarm scenarios were created. Video was recorded for 30 seconds regardless of whether there was continued motion and with no pre or post buffer) and you upgrade to v5.2 or later (including upgrading the recorder), the system will convert these camera configurations and enable Record on Motion. No further action is required. Keep in mind that the default values for pre- and post- buffers of 3 seconds will be used. If you want, you may modify these settings. The settings in the server side or camera side motion detection screens remain unchanged.
If you have motion detection already configured in v5.1 using alarm scenarios and you upgrade to v5.2 or later (including upgrading the recorder), your alarm scenarios and motion detection recording will still continue to work as before. No action is required.
However, we recommend that you enable some or all of your cameras for Record on Motion to take advantage of its efficiencies. Remember that you can enable Record on Motion with multi-config for a group of cameras to make it easier. Also, if you do decide to enable Record on Motion, you will need to delete or deactivate the corresponding alarm scenarios. If you do not deactivate alarm scenarios that do motion detection recording, they will continue to function as before and will result in excess video. Deactivating alarm scenarios is supported with group edit to modify multiple scenarios in bulk. Reducing the number of alarm scenarios will also free up resources on the core.