Page History

x32: (x32)
x64: (x64)

ChangePort

> = 0

Depends on the port specified for the Client.

4.7.3 and later

Allows changing the port number. For instance, if it is necessary to change port 20900 to 40900, then 20900="40900" string parameter is created.
The change of this parameter can affect the system.

x32: (x32)
x64: (x64)

CheckPingPeriod

> 0

 10

4.7.4 to 4.10.2

Sets Server-computer ping period.

Note. In Intellect since version 4.10.3 this parameter is set on the settings panel of the Security zone object.

x32: (x32)
x64: (x64)

CheckVersion

0, 1

0

4.7.4 and later

Sets the parameters of Server connection: the version is checked in connected version parameters. If versions do not agree, then there is a corresponding message and no connection.

x32: (x32)
x64: (x64)

Core IP Address

IP address

 -

4.7.3 and later 

Address of the computer to the core of which the slave.exe is to connect.

x32: (x32)
x64: (x64)

DBAttempts

>=1

 10

4.7.3 and later

Number of attempts to connect to database.

x32: (x32)/Debug
x64: (x64)/Debug

DebugLevel

0,1,2,3,4

0

4.7.3 and later

Sets the debug mode:
0 – disabled;

1 – information is shown in the process window;

2 – information is shown in the process window and logged;

3 – extended log is written – it contains module events;

4 – extended log is written – it contains module events and parameters.

x32: (x32)/Debug
x64: (x64)/Debug

DebugExtension

Any string

LOG

4.7.3 and later

Sets extensions of log files.

x32: (x32)/Debug
x64: (x64)/Debug

DebugFlushPeriod

> = 0

500

4.7.4 and later

Sets the update rate for log files (ms).

x32: (x32)/Debug
x64: (x64)/Debug

DebugOptions

Range in decimalsystem: 0-255. 

0x001 (i.e. 1)

4.7.3 and later

Hexadecimal logging in the debug mode. This parameter has a complex structure (bit mask) and it is modified using the Tweaki.exe utility.

x32: (x32)/Debug
x64: (x64)/Debug

DebugQueueMaxLines

0 – 2147483647

2000

4.7.4 and later

Specifies max. number of messages in a queue to log file. If there are more than 500 log lines in the queue, then they are to be groomed.

x32: (x32)/Debug
x64: (x64)/Debug

DebugSize

>=100

100

4.7.3 and later

Specifies the number of megabytes provided for log. Restricted by disk capacity.

x32: (x32)/Debug
x64: (x64)/Debug

DebugTime

 0-2147483647

48

4.7.3 and later

Specifies the number of hours for keeping log files.

x32: (x32)
x64: (x64)

defaultconnection

 0, 1

1

4.7.4 and later

Allows setting connections in the architecture only with the computer where the Computer object is created.

x32: (x32)
x64: (x64)

DisableProtocol

0, 1

0

4.7.3 and later

Allows disabling protocol.

x32: (x32)
x64: (x64)

DisableThreadStatQueue

0, 1

0

4.8.0 and later

 By default the key is not created.

Defines whether the queue statistics is called or not. If the registry key value=1, then the box can not be called.

To call the Queue statistics box, follow the steps:

• Intellect 4.9.2 and older – press F2
• Intellect 4.9.3 and later – press Alt+F2 key combination

x32: (x32)
x64: (x64)

InstallFolder

Intellect

4.7.3 and later

Specifies the installation folder.

x32: (x32)
x64: (x64)

Language

0x0419

-

4.7.3 and later

Specifies the language to use (0x0419 – English). 

x32: (x32)
x64: (x64)

LogIncommingMsg

0, 1

not created

up to  4.8.0

Defines whether logging of incoming events is enabled or not.

x32: (x32)
x64: (x64)

LogOutgoingMsg

0, 1

not created

up to  4.8.0

Defines whetheroutgoing reactions (for example, commands) will be logged or not.

x32: (x32)
x64: (x64)

LogStatistics

0, 1

not created

up to  4.8.0

Defines whether the statistics is logged or not.

x32: (x32)
x64: (x64)

OnlyLocalProtocol

0, 1

0

4.7.3 and later

Only local events are logged.

x32: (x32)
x64: (x64)

PeakWorkingSetSizeQuota

>=0

0

4.8.1 and later

Sets RAM limit (MB). When this limit is exceeded, the module that exceeded this limit will be restarted in the restart service.

x32: (x32)
x64: (x64)

PhotoCores

Name or IP address 

-

4.7.3 and later

The list of computers (cores) for mailing user photos.

x32: (x32)
x64: (x64)

PriorityClass

256,

128,

32768,

32,

16384,

64

 16384

4.7.3 and later

Defines the stream priority:

256 – realtime

128 – high

32768 – Above Normal

32 – normal

16384 – below Normal

64 – low

x32: (x32)
x64: (x64)

ShowCrashMessage

0, 1

0

4.7.5 and later

Create or not the module crash message. 

x32: (x32)
x64: (x64)

SyncTime

0, 1

0

Defines whether to synchronize time between computers or not.

x32: (x32)
x64: (x64)

Topmost

0, 1

1

4.7.4 and later

Sets the splash screen location:
1 – splash screen is topmost;
0 – screen is hidden behind other windows.

This key is applied for splash screen on the Server/Remote Administrator’s workplace for Intellect versions older than 4.10.0, for versions newer 4.10.1 – both on the Server/Remote Administrator’s workplace and on the Client.

x32: (x32)
x64: (x64)

Type_view_dept_log

0,1,2

0

4.7.4 and later

Specifies displaying the  name of department in the log:

0 – do not add:  Ivanov Ivan Ivanovich;  
1 – add to the beginning:
[Sales department] Ivanov Ivan Ivanovich;
2 – add to the end:
Ivanov Ivan Ivanovich [Sales department].

x32: (x32)
x64: (x64)

URAttempts

 0 – 10000

3

4.7.3 and later

Sets the number of attempts to enter the user password .

x32: (x32)
x64: (x64)

URDelay

 0 – 10000

60

4.7.3 and later

Sets the delay period (sec) for re-entering the system.

x32: (x32)
x64: (x64)

virtualgrabber

0, 1

0

4.7.6 and later

Defines whether it is possible to create  a virtual video capture card or no.

x32: (x32)
x64: (x64)

SyncNotEmpty

0, 1

0

4.8.5 and later

Defines the database synchronization algorithm:

1 – fast synchronization algorithm is in use;

0 –  standard synchronization algorithm is in use.

x32: (x32)\Debug
x64: (x64)\Debug

counter_period

>=0

0

4.9.0 and later

Defines the time period in seconds, in which information about availability of processor, memory and disk is recorded to the log-file. If the value of parameter is 0, this information is not included to the log-file.

x32: (x32)\ IntellectRunService
x64: (x64)\ IntellectRunService

RestartIntellectOnLogonDisable

0, 1

0

4.9.0 and later

1 – Intellect installed as a Service is not restarted under the current user even for users belonging to the IntellectUsers group.

0 – Intellect installed as a Service is restarted under the current user only if the user belongs to the IntellectUsers group.

x32: (x32)\ IntellectRunService
x64: (x64)\ IntellectRunService

CheckUserForRestartIntellectDisable

0, 1

-

4.9.0 and later

0 – Intellect installed as a Service is restarted (when entering the system) under the current user only if the user belongs to the IntellectUsers group.

1 – Intellect installed as a Service is restarted (when entering the system) under the current user even if the user doesn’t belong to the IntellectUsers group. The settings of permissions are to be taken into account when using this key. If the permissions are set incorrectly, then some Intellect features can operate incorrectly.

x32: (x32)
x64: (x64)

ShowHiddenObjects

0, 1

0

4.9.0 and later

0 – hidden objects corresponding to IntegratedAudioSource and IntegratedVideoSource objects, as well as to Integrated device child objects are not shown in the object tree in Intellect.

1 – hidden objects are shown in the object tree in Intellect.

Intellect is to be restarted when the key value is changed.

x32: (x32)\ IntellectRunService\
x64: (x64)\ IntellectRunService\

InheritServiceEnvironment

0, 1

-

4.9.0 and later

The key is essential for proper operation of Intellect in MS failover cluster.

x32: (x32)
x64: (x64)

SortCamsById

0, 1

-

4.8.8 and later

The key is responsible for sorting the list of cameras on the settings panelof the Monitor object.

1 – cameras are sorted by ID;

0 – cameras are sorted by names.

x32: (x32)
x64: (x64)

EventProcessingThreads

>=0

0

4.9.0

Key reserves the specified number of streams for events processing.

x32: (x32)\Debug
x64: (x64)\Debug

DumpYUV

0, 1

-

4.9.0.959  and later

Key activates the mode of video dump corresponding to compressor.  It is required for diagnostics of StreamLabs (motionWavelet7.1) compressor/decompressor problems.

File (or files) with decompressed data will be created by key in the Modules directory. Names of files correspond to the template:
WxH_hv_chunk_№.yuv

W – width;
H – height;
h – horizontal subsampling;
v – vertical subsampling;
№ – number of file. If resolution or subsampling are changed the new file openes.

For example, file with resolution 640x480 in YUV420 color area will have the 640x480_22_chunk_0.yuv name.

x32: (x32)
x64: (x64)

x32: (x32)
x64: (x64)

0 – receiving of the SETUP reaction from the ATM object is disabled on the computer where this key is specified.

1 – receiving of the SETUP reaction from the ATM object is enabled on the computer where this key is specified. 

1 – F10 and F11 hot keys are in use to control screen displaying (see Main control panel section).

0 – F10 and F11 hot keys are not in use to control screen displaying.

Note.When the key is changed Intellect restart is required. 

 To disable F10 and F11 hot keys on the Administrator Remote Workplace, the key is to be created in the  \HKEY_CURRENT_USER\Software\ITV\Intellect registry section.

To disable F10 and F11 hot keys on the Administrator Remote Workplace when operating under the Admin account, he key is to be created in the same registry section as on Server (x32)/(x64).

0 –  F8 hot key is in use to call the Execute menu on the main control panel.  

1 – F8 hot key is not in use.

Note. To disable F8 hot key on the Administrator Remote Workplace, the key is to be created in the  \HKEY_CURRENT_USER\Software\ITV\Intellect registry section.

To disable F8 hot key on the Administrator Remote Workplace when operating under the Admin account, he key is to be created in the same registry section as on Server (x32)/(x64).

x32: (x32)
x64: (x64)

When the key value = 1, video or archive period is exported from the Monitor interface using the admin password.

By default the key is not created, the value is 10.

The key specifies maximum waiting time (in milliseconds) before sending data over the network.

The higher the value of this parameter, the more productive the system is (due to decreasing resources when sending a large amount of small messages).

The key sets the delay between disabling Guardant and unloading Intellect.

The delay is essential for the FORCED_OFF event generation of the SLAVE object and in case this event is used in scripts or programs, these scripts and programs are executed.

The key is for specifying the way of sorting objects in the tree:

0 – sorting by name;

1 – sorting by ID.

Note 1. If sorting by name is chosen, and there are numbers in the object name, then the objects will be sorted in alphabetical order. For example, an object with the name "115" will be above the object with the name "15", because in the name "115" the second number is 1, and in the name "15" the second number is 5.

Note 2. This key also affects the sorting of objects in the tree when adding the objects to a layer in the Map Editor utility.

The key enables displaying the main control panel of Intellect on the screen.

0 – the main control panel is displayed when pointing to the upper right corner of the screen.

Sets time period (in days) of storing the change protocol in the database.

The storing period is counted from the last recording or starting from the current time depending on the value of the ClearProtocolFromCurrentTime key (see above).

The key enables the compression of transmitted messages:

0 – compression is disabled.

1 – messages from the cores are sent compressed (zip with maximum compression). Compression allows reducing the network load.

The key is used with the ACS/FAS integration modules that are the part of ACFA Intellect. It enables displaying the access card number for all events associated with the cards in the Event Viewer.
0 – the access card number is not displayed in the Event Viewer.
1 – when an event comes from the ACS device, the param1 parameter is interpreted as an access card number and is displayed in the Event Viewer in the Card column. This column is automatically added to the Event Viewer window when the first such event is received.

Note. In the released version 4.10.3 to show and hide the Card column use the Hide Card checkbox – see Event viewer parameters.

It enables recording of incoming messages to log files for started modules. The file name looks like <module name>.exe.cd.log.

These files are stored in the same folder as the executed module file, for instance, for intellect.exe the intellect.exe.cd.log file is stored in the Intellect installation directory and for VMSScript.exe the VMSScript.exe.cd.log file is stored in the Modules folder.

When the size of the log file exceeds 4 GB, it is archived to the backup file with .bak extension – <module name>.exe.cd.log.bak. This is necessary to avoid module overload.

Note. The log file is rewritten when Intellect is restarted.

0 – recording of incoming messages is disabled.

1 – recording of incoming messages is enabled.

x32 and x64:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

The key sets a period in milliseconds to update video on Video Surveillance Monitors of the Clients after Failover Service has transferred configuration.

If the key value is less than 500, the monitors are updated regardless of the number of cameras.

If the key value is more than 500 and the number of cameras on the monitor is more than 64, the update does not occur while the System Settings dialog box is open.

max_disp_menu_items

The key sets time period in milliseconds to wait for the Client to stop before aborting the Video.run process.

The key should be created on the Clients.

The key enables the display of users responsible for the region (if assigned) in events from objects related to the regions:

• In the Event Log – in the Add.info field.
• In the Operator protocol – in the event box next to the name of the region.
• On the Map – in the Output window on the Object Info tab

The key is created on the Server.

ShowPanelByKey

The key disables the display of the Main control panel by hovering the mouse cursor in the upper right corner of the screen. Having the key is set to 1, use the F12 hotkey to call the Main control panel.

Enables distribution integrity check when starting Intellect software package. The following files are checked:

• Intellect.exe
• Intellect64.exe
• Slave.exe
• Modules64/Slave.exe

If any of them is missing or changed, the message "The integrity of the distribution package is broken. Reinstall Intellect" is displayed in the launch window, and the Intellect start interrupts.

Sets the port through which Intellect receives events and reactions via HTTP request. See also Sending reactions and events to Intellect using HTTP request.

The key is discontinued starting from Intellect 4.11.1. The port is set on the Web server object settings panel – see Setting the parameters of connecting Clients to the Web-server.

The key enables synchronization with Active Directory when starting Intellect software.

0 – synchronization with AD when starting Intellect is disabled.

1 – synchronization with AD when starting Intellect software is enabled.

The key enables the joint operation of the Intellect software package and the Axxon Next software package.

0 – joint operation is disabled.

1 – joint operation is enabled.

The key specifies the number of the physical monitor on which the Main Control Panel should be displayed. The key can be used both for the Intellect Server/RAW configuration, and for the Client configuration.

Monitors are numbered left to right, top to bottom, regardless of system numbering.

Important! The numbering of monitors starts from 0. For example, set the key to 0 to display the Main Control Panel on the 1st physical monitor; set to 1 to display on the 2nd monitor, etc.

By default, the Main Control Panel is displayed on the Primary monitor selected in the system screen options.

The key disables hot keys for macros.

0 – hotkeys in macros are disabled.

1 – hotkeys in macros are enabled.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

Delay

> = 0

250

4.7.3 and later

Defines the delay (ms) when sending commands to the camera. This key is essential for grooming the stream of commands to the device as some devices can be blocked because of too many commands and cannot process the information.

This parameter is not supported by IP cameras.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

JoysticThreshold

> = 0

5

4.7.6 HOTFIX and later

This parameter sets the joystick trigger threshold: the less the number is, the more sensitive joystick is.

0 value is not recommended to be used, as commands can be sent randomly.  When the value is too big, the joystick becomes rotation-insensitive.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

PriorityDelay

> =  0

30000

4.7.3 and later

Defines the priority delay (ms).

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

UseBoschOSRD40

0, 1

-

4.8.4 and later

Enables presets saving for Bosch-Autodome control protocol.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

PnPJoystick

0, 1

0

4.8.3 and later 

The key defines whether to restart Intellect after connecting a joystick:

0 – Intellect is to be restarted after connecting the joystick.
1 – Intellect is not to be restarted after connecting the joystick.

x32: (X32)\TELEMETRY
x64: (x64)\TELEMETRY

Zenable

0, 1

1

4.7.7 and later 

The key is in use with joysticks (e.g., Logitech Attack 3) where the telemetry control operates incorrectly because of shifted Z axis. Z axis is disabled when the parameter value is 0.  Z axis is enabled when the parameter value is 1.

The key is used in order to set the zoom step when panasonic-850 telemetry protocol is in use:

1 – zooming with 50% step of max. possible

0 – zooming with 20% step of max. possible

The key is responsible for coordinate move in the Z-direction.

The key is responsible for coordinate move in the Y-direction.

The key is responsible for coordinate move in the X-direction.

The key specifies way of  command transmission to telemetry:

1 – telemetry server is connected to video servers and sends commands to devices.

0 – telemetry server sends commands to the Intellect core which send them to devices.

See also description of the MonitorToTelemetryDirectCommand key below.

The key specifies way of transmission telemetry commands while control from the Monitor:

1 – telemetry server is connected to video servers and sends commands to devices while telemetry control from the Monitor.

0 – telemetry server sends commands to the Intellect core which send them to devices while telemetry control from the Monitor.

The key is in use with the TelemetryDirectCommand key to provide smoother telemetry control. Recommended values of these keys:

TelemetryDirectCommand = 1 (default value)

MonitorToTelemetryDirectCommand = 1 (attention: default value is 0)

The key is to enable the function of sending events to Intellect core when controlling PTZ. This function is essential for PTZ control audit.

1 – when sending any reaction of TELEMETRY object the corresponding event is generated.

The key enables presets created on the camera in Intellect. The function is only available when camera is connected via ONVIF protocol and only if video server settings are selected when adding a Video capture device using the Camera discovery tool and the Use device settings checkbox is set unchecked on the settings panel of the Video Capture Device object.

0 – presets created on the camera are not used in Intellect.

1 – presets created on the camera are in use in Intellect. The features are listed below:

1. The preset ID on the camera is to be the same as the preset ID in Intellect or differ by 1 depending on the camera features (see item 2).
2. As preset numeration starts differently on various cameras (with 0 or 1), then preset numbers can differ by 1 in Intellect. If the numeration on the camera starts with 0, then numeration in Intellect is the same. If the numeration on the camera starts with 1, then numeration in Intellect is greater by 1 (for instance, the first preset on the camera corresponds to the second in Intellect and the first in Intellect is not active).

The key enables the old mechanism for connecting and controlling joysticks using Windows tools.

1 – the joystick is controlled by Driver Pack driver.

0 – the joystick is controlled by Windows built-in driver.

By default, joysticks should be connected the Camera discovery tool as a Control Device.See also Configuring the joystick for telemetry control.

DO NOT set the key to 0 if the Control Device object is created for the joystick.

DO NOT set the key to 1 if the Control Panel object is created for the joystick.

x32: (x32)\ EventViewer
x64: (x64)\EventViewer

Overlay

0, 1

1

4.7.3 and later

Defines whether to use overlay.

x32: (x32)\ EventViewer
x64: (x64)\EventViewer

Topmost

0, 1

0

4.7.3 and later

Defines whether to display event log as topmost window: 

0 – standard window;

1 – topmost window.

x32: (x32)\ EventViewer
x64: (x64)\EventViewer

It sets the time period in minutes, after which, if there is no user activity, automatic scroll to the end of the event list when new events arrive is enabled in the Event Viewer window.

If 0 is specified, then automatic scroll is disabled.

Enables the generation of the EVENT_VIEWER||CREATE_REPORT event instead of opening the report when selecting the Show report menu item in the Event Viewer.

0 – when selecting the Show report menu item in the Event Viewer, a report opens.

1 – when selecting the Show report menu item in the Event Viewer, the EVENT_VIEWER||CREATE_REPORT event is generated, but the report does not open.

See also EVENT_VIEWER.

x32: (X32)\ Subscribe
x64: (x64)\Subscribe

<OBJECT_NAME>

(*) (№.*) (№.№)

-

4.7.3 and later

Describes rules for system starting. Unimplemented system objects are disabled.

You should create a string parameter with the name that is used by the system of the object that is to be disabled and specify its ID separated by a full stop.
Example: DEPARTMENT.1:
«0» – disable,
«1» – enable
The “.*” parameter can be used – in this case all objects with “DEPARTMENT” name are disabled. Take into account that parameter with the ID is of a higher priority than the “.*” parameter. So there is no need to describe all objects by listing their IDs if there are a lot of objects that are to be disabled. You can just set 0 value to the “.*” parameter and list the objects that are not to be disabled.
All values are to be written in capital letters.
This registry section is applied to all system objects.

x32: (X32)\ DB Import
x64: (x64)\ DB Import

ChunkSize

> 0 and >= photo size

32768

4.7.3 and later

Sets the buffer size (in bytes) when reading large files (photo) in the external DB.

x32: (X32)\ DB Import
x64: (x64)\ DB Import

CursorLocation

1, 2, 3

2

4.7.3 and later

Sets the cursor location (pointer to DB entries):
1 – do not create the cursor;
2 – create the cursor on the Server;
3 – create the cursor on the Client.

x32: (X32)\ DB Import
x64: (x64)\ DB Import

DwSleep

> = 0

1

4.7.3 and later

Sets the delay value (ms) when sending modified entries to the core in the external DB in order not to get 100% CPU load.

x32: (X32)\ DB Import
x64: (x64)\ DB Import

MoveFirst

0

0

4.7.3 and later

The key must not be modified.

x32: (X32)\ Keyb
x64: (x64)\ Keyb

Prefix

VK_NUMPAD0
VK_NUMPAD1
VK_NUMPAD2
VK_NUMPAD3
VK_NUMPAD4
VK_NUMPAD5
VK_NUMPAD6
VK_NUMPAD7
VK_NUMPAD8
VK_NUMPAD9
VK_MULTIPLY
VK_ADD
VK_SEPARATOR
VK_SUBTRACT
VK_DECIMAL
VK_DIVIDE
VK_F1
VK_F2
VK_F3
VK_F4
VK_F5
VK_F6
VK_F7
VK_F8
VK_F9
VK_F10
VK_F11
VK_F12
VK_F13
VK_F14
VK_F15
VK_F16
VK_F17
VK_F18
VK_F19
VK_F20
VK_F21
VK_F22
VK_F23
VK_F24

0x60

0x61

0x62

0x63

0x64

0x65

0x66

0x67

0x68

0x69

0x6A

0x6B

0x6C

0x6D

0x6E

0x6F

0x70

0x71

0x72

0x73

0x74

0x75

0x76

0x77

0x78

0x79

0x7A

0x7B

0x7C

0x7D

0x7E

0x7F

0x80

0x81

0x82

0x83

0x84

0x85

0x86

0x87

4.7.3 and later

The list is not full. Any soft key can be in use.

The key allows using the standard keyboard as the special one. In this case keypress on the standard keyboard will be considered as keypress on the special keyboard and processed according to the ini file.

x32: (x32)\Script\

x64: (x64)\Script\

x32: (x32)\Script\

x64: (x64)\Script\

TerminateProcessOnHang

0 – Intellect core does not terminate the VMSScript.exe process when it hangs.

1 – Intellect core terminates the VMSScript.exe process when it hangs.

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

UseRealTimeStamps

Comma-separated camera identifiers

-

4.9.

8 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

4.9.

8 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 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.

8 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 = "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.

8 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

4.9.

8 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

4.9.

8 and later

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

determineHumanCar

Comma-separated camera identifiers.

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

-

4.9.

8 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"

4.9.

8 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

4.9.

8 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.

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

Starting with 4.11.2

DP 2.8 and later

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

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

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)

Starting with 4.11.2

DP 2.8 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.

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

1 – utility is started in export mode in the AXXN codec if Export to AVI in initial format item is selected.

0 – export is possibly performed in original format.

Key sets priorities of the AviExport utility and is used by the Video.run module while its starting:

-2 – low priority (IDLE_PRIORITY_CLASS)

-1 – below average priority(BELOW_NORMAL_PRIORITY_CLASS)

 0 – average priority (NORMAL_PRIORITY_CLASS)

 1 – above average priority (ABOVE_NORMAL_PRIORITY_CLASS)

 2 – high priority (HIGH_PRIORITY_CLASS)

>0

Fractional values can be specified with comma as decimal separator  (for example, "0,5")

When the export period is being set, the key disables the automatic loading of indexes until the date/time control focus is removed.

0 – the indexes are loaded automatically.

1 – the indexes are not loaded until the focus is removed from the date/time controls.

Specifies the path to the folder for storing temporary files created during export.

To enable the use of this key, set the TempDirByDst key to 0 (see below). By default, temporary files are saved in the folder specified by the ExportDir registry key (in the AviExport section, see above)

Note. It is recommended to enable the UseTempDir key for export to removable media or network drives. In this case, set the directory on the computer hard disk in the key.

Enables the use of the UseTempDir key (see above).

0 – temporary export files are stored in the UseTempDir path.

1 – temporary export files are stored in the ExportDir path (specified in the AviExport section, see above).

Specifies a part of the name for the Axxon Player utility file exported together with the archive from the AviExport utility, if the corresponding setting is selected (see General settings of export).

If the key is specified, the player file will be named "<key_value>_player_portable.exe".

By default, if the key is not created, the player file is named Axxon_player_portable.exe.

The key allows hiding the Face disguise masking checkbox in the AviExport utility (see Masking faces export)

0 – checkbox Face disguise masking is displayed

1 – checkbox Face disguise masking is hidden

HIDE_WHOLE_SCREEN_WITHOUT_LIVE_VIDEO

DONT_HIDE

HIDE_WHOLE_SCREEN

The key allows to completely hide the screen before and after the selected segment with inverted masking when viewing a live or archive video in the Surveillance Monitor, as well as during export.

HIDE_WHOLE_SCREEN_WITHOUT_LIVE_VIDEO — the screen is completely hidden before and after the selected segment with inverted masking when viewing the archive in the Surveillance Monitor and when exporting. When watching live video in the Surveillance Monitor, the screen before and after is not hidden.

DONT_HIDE — the screen is not hidden.

HIDE_WHOLE_SCREEN — the screen is completely hidden when viewing a live video or archive in the Surveillance Monitor, as well as when exporting.

Specifies the maximum number of

simultaneously running export threads. Cannot exceed the number of processor cores.

Specifies the delay in sending messages about the export process in milliseconds if the percentage indication does not change for a long time.

Specifies the delay in milliseconds before checking for incoming frames ready to be written to a file.