Page History

UseRealTimeStamps

Comma-separated camera identifiers

-

1.0.0 and later

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\VMDA
x64:(x64)\Video\VMDA

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

1.0.0 and later

Sets sensitivity of unattended objects detection tool for specified cameras

x32:(x32)\Video\VMDA
x64:(x64)\Video\VMDA

VMDA.unattendedObjectLongMemory

Comma-separated camera identifiers, for example unattendedObjectLongMemory ="1.1,1.2,1,3,1.4,5,6"

-

1.0.0 and later

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

x32:(x32)\Video\VMDA
x64:(x64)\Video\VMDA

VMDA.unattendedObjectTimeBeforeCheck

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

EXAMPLE unattendedObjectTimeBeforeCheck = "1, 2, 3, 4, 54.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)

1.0.0 and later

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

x32:(x32)\Video\VMDA
x64:(x64)\Video\VMDA

determineNoise

0, 1

1

1.0.0 and later

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

x32:(x32)\Video\VMDA
x64:(x64)\Video\VMDA

VMDA.determineColorIdentity

0, 1

1

1.0.0 and later

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

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

x32:(x32)\Video\VMDA
x64:(x64)\Video\VMDA

determineHumanCar

Comma-separated camera identifiers.

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

-

1.0.0 and later

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\VMDA
x64:(x64)\Video\VMDA

determineGivenTaken

Comma-separated camera identifiers.

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

1.0.0 and later

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\VMDA
x64:(x64)\Video\VMDA

VMDAFPS

>=-1

30

1.0.0 and later

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 VMDA detection

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 VMDA detection

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

1.0.0 and later

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

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

1.0.0 and later

The key sets the duration of the frame display in milliseconds in the area where montion is detected or on the detected abandoned object. By default, the key is not created. If a new object with the frame appears, the current frame will not disappear

Number in 4-byte RGB format:

Most significant 4th byte = 0

3rd byte — R (0..255)

2nd byte — G (0..255)

1st byte — B (0..255)

1.0.0 and later

The key sets the color of the frame (bounding box) on the detected abandoned object. By default, no key is created.

For this key to work, it is necessary to set the VMDAEXT key to 1