Page History

x32: (X32)\Video
x64: (x64)\Video

UseRealTimeStamps

Comma-separated camera identifiers

-

4.9.5 to 4.9.7

Identifiers are separated by commas for cameras for which current timestamps are to be sent. Due to features of the unattended object detection tool (that is a third-party module) it sends synthetic timestamps by default.

x32: (X32)\Video
x64: (x64)\Video

VMDA.unattendedObjectSensitivity

Comma-separated sensitivity values in the ‘camera id.sensitivity’ format.

Sensitivity range –[1...25]

EXAMPLE: unattendedObjectSensitivity="1.15,99.20,4.7"

7 for all cameras

4.9.5 to 4.9.7

Sets sensitivity of unattended objects detection tool for specified cameras.

x32: (X32)\Video
x64: (x64)\Video

VMDA.unattendedObjectLongMemory

Comma-separated camera identifiers in the ‘camera id.1’ format.

EXAMPLE unattendedObjectLongMemory ="1.1,1000.1,2.1,999.1,3.1,5.1,4.1,6.1,7.1,8.1"

'camera_id.0' means that long memory detection tool is disabled for the camera with the corresponding identifier.

-

4.9.5 to 4.9.7

Sets identifiers of cameras to which the unattended object detection tool with long memory is to be used.

x32: (X32)\Video
x64: (x64)\Video

VMDA.unattendedObjectTimeBeforeCheck

Values of periods are comma-separated and are in the ‘camera id.period’ format.

EXAMPLE unattendedObjectTimeBeforeCheck = "4.20,1.10,3.40"

By default it is the same as the waiting for loss period set while configuring the Tracker object (see Creating and configuring the Tracker object).

4.9.5 to 4.9.7

Time in seconds before checking object in case of using the unattended object detection tool with long memory.

x32: (X32)\Video
x64: (x64)\Video

determineNoise

0, 1

1

4.9.5 to 4.9.7

Use (1) or not (0) the algorithms for detecting pseudo-moving objects

x32: (X32)\Video
x64: (x64)\Video

VMDA.determineColorIdentity

0, 1

1

4.9.5 to 4.9.7

Use (1) or not (0) the algorithms for detecting objects matching by their color characteristics.

The key enables more percise colour determination for smart detection and archive search (see Configuring smart video detection tools and Search by colour).

x32: (X32)\Video
x64: (x64)\Video

determineHumanCar

Comma-separated camera identifiers.

EXAMPLE determineHumanCar ="1,1000,2,999,3,5,4,6,7,8"

-

4.9.5 to 4.9.7

Sets the list of camera identifiers for which the algorithm of determining whether it is a car or a human is to be ENABLED.

For proper operation of the tracker determineGivenTaken and determineHumanCar keys MUST be used at the same time. There is no point in using only one key.

x32: (X32)\Video
x64: (x64)\Video

determineGivenTaken

Comma-separated camera identifiers.

EXAMPLE determineGivenTaken ="1,1000,2,999,3,5,4,6,7,8"

4.9.5 to 4.9.7

Sets the list of camera identifiers for which the algorithm of determining whether the object is given or taken is to be enabled in the unattended object detection tool.

For proper operation of the tracker determineGivenTaken and determineHumanCar keys MUST be used at the same time. There is no point in using only one key.

x32: (X32)\Video
x64: (x64)\Video

VMDAFPS

>=-1

30

4.9.5 to 4.9.7

Sets fps to be sent to the tracker.  
-1 – ALL FRAMES
0 – send a frame to the tracker if the tracker is available (processed the previous frame).
>0 – maximum fps sent to the tracker.

The key specifies usage of previous frame processing before its sending to video analytics repository:

0 – not to use.

1 – to use.

If the key is enabled, it's in use for all cameras.

Important! The useFilterFrame parameter is to have ‘1’ value for key operation (see below).

The key specifies post processing usage of frames received from video analytics repository. Procedure is configured only for operation with frames from left-off items detection, so it can operate incorrectly with frames from tracker. If the key is enabled, it is in use for all cameras.

Important! The useFilterFrame parameter is to have ‘1’ value for key operation (see below).

The key is responsible for enabling frame pre-process before its analysis. If it is disabled, useLeftImprover and useLeftImproverGeometry keys won’t work (see above).

1 – enabled;

0 – disabled.

Set VMDAEXT to 1 in order to use this key.

Enables the function of determining the given/taken objects on the side of the Tracker library. Information about given/taken objects is recorded to the VMDA metadata storage. After that, it is possible to perform forensic search by them in the archive. See also CAM_VMDA_DETECTOR.

Set VMDAEXT to 1 in order to use this key.

Enables the function of determining the object type on the side of the Tracker library. This type is stored to the VMDA metadata storage. After that, it is possible to perform forensic search by it in the archive. See also CAM_VMDA_DETECTOR.

The VMDA detector identifier and the operation mode separated by the dot "." The pairs of values are separated by a comma "," or a semicolon ";"

Starting with 4.10.5

DP 2.6

Set VMDAEXT to 1 and specify required value for VMDA.determineGivenTaken in order to use this key.

Sets the operation mode of VMDA detectors, which detect the abandoned objects.

The following modes are available:

0 - trigger on abandoned objects (default)

1 - trigger on disappeared objects

2 - trigger on abandoned and disappeared objects

Key value format: VMDA_identifier dot "." operation_mode. For example: 1.0

To list several pairs of detectors and their operating modes, use a comma "," or a semicolon ";". For example: 1.0;2.2;3.1