Go to documentation repository
...
Core | |||||
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32: (x32) | ChangePort | > = 0 | Depends on the port specified for the Client | 1.0.0 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. |
x32: (x32) | CheckPingPeriod | > 0 | 10 | 1.0.0 and later | Sets the period of checking the computer's connection to the server. Note. Starting with the Axxon PSIM 1.0.0 version, you can set this parameter in the Ping (s) field for servers on the settings panel of the Security Zone object and it is automatically saved in the CheckPingPeriod parameter. For the Remote client, you can set it in the CheckPingPeriod parameter manually |
x32: (x32) | CheckVersion | 0, 1 | 0 | 1.0.0 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) | Core IP Address | IP address | - | 1.0.0 and later | Address of the computer to the core of which the psim_host.exe is to connect |
x32: (x32) | DBAttempts | >=1..∞ | 10 | 1.0.0 and later | Number of attempts to connect to database |
x32: (x32)/Debug | DebugLevel | 0,1,2,3,4 | 4 | 1.0.0 and later | Sets the debug mode: 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 | DebugExtension | Any string | LOG | 1.0.0 and later | Sets extensions of log files |
x32: (x32)/Debug | DebugFlushPeriod | > = 0 | 500 | 1.0.0 and later | Sets the update rate for log files (ms) |
x32: (x32)/Debug | DebugOptions | Range in decimalsystem: 0-255. | 0x001 (i.e. 1) | 1.0.0 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 | DebugQueueMaxLines | 0 – 2147483647 | 50000 | 1.0.0 and later | Specifies max. number of messages in the queue to the log file. If there are more than 500 log lines in the queue, then they must be decimated |
x32: (x32)/Debug | DebugSize | >=100 | 100 | 1.0.0 and later | Specifies the number of megabytes provided for log. Restricted by disk capacity |
x32: (x32)/Debug | DebugTime | 0-2147483647 | 48 | 1.0.0 and later | Specifies the number of hours for keeping log files |
x32: (x32)/Debug x64: (x64)/Debug | DebugZipDays | >0 | 2 | 1.0.0 and later | Specifies the number of days for keeping log files in the gz format |
x32: (x32)/Debug x64: (x64)/Debug | LogTracker | 0, 1 | - | 1.0.0 and later | By default, the key isn't created. Only for 64-bit systems. The key is used to write logs to a new vmda_lib.log file in the Modules64 folder during smart search in the archive. 0—a new log file isn't created 1—a new log file is created |
x32: (x32)/Debug x64: (x64)/Debug | AutoTestSupportEnabled | 0, 1 | 0 | 1.0.0 and later | The key supports automatic tests for the User permissions object and the AD connection window. By default, the key isn't created and its value is 0 |
x32: (x32) x64: (x64) | debug_log | 0, 1 | - | 1.0.0 and later | By default, the key is not created. The key defines whether all events and reactions all fully logged into the log file. Note. It is not recommended to use this key on a permanent basis, because with full logging, the size of the log file will constantly increase |
x32: (x32) x64: (x64) | debug_protocol | 0, 1 | 0 | 1.0.0 and later | The key creates the DEBUG_PROTOCOL table in the database. All events and reactions are recorded in the table. Note. When restarting Axxon PSIM, the table will be created anew |
x32: (x32) | defaultconnection | 0, 1 | 1 | 1.0.0 and later | Allows setting connections in the architecture only with the computer where the Computer object is created |
x32: (x32) | DisableProtocol | 0, 1 | 0 | 1.0.0 and later | Allows disabling protocol |
x32: (x32) | DisableThreadStatQueue | 0, 1 | 0 | 1.0.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, press Alt+F2 key combination |
x32: (x32) | InstallFolder | Axxon PSIM | 1.0.0 and later | Specifies the installation folder | |
x32: (x32) | Language | 0x0419 | - | 1.0.0 and later | Specifies the language to use (0x0419 – English) |
x32: (x32) | OnlyLocalProtocol | 0, 1 | 0 | 1.0.0 and later | Only local events are logged |
x32: (x32) x64: (x64) | ProtocolWriteAllEvents | 0, 1 | 0 | 1.0.0 and later | Defines whether the events are recorded into the Events protocol |
x32: (x32) | PeakWorkingSetSizeQuota | >=0 | 0 | 1.0.0 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) | PhotoCores | Name or IP address | - | 1.0.0 and later | The list of computers (cores) for mailing user photos |
x32: (x32) | PriorityClass | 256, 128, 32768, 32, 16384, 64 | 32 | 1.0.0 and later | The key determines the stream priority: 256—realtime 128—high 32768—Above Normal 32—normal 16384—below Normal 64—low |
x32: (x32) | ShowCrashMessage | 0, 1 | 0 | 1.0.0 and later | Create or not the module crash message |
x32: (x32) | SyncTime | 0, 1 | 0 | 1.0.0 and later | Defines whether to synchronize time between computers or not |
x32: (x32) | Topmost | 0, 1 | 1 | 1.0.0 and later | Sets the splash screen location: This key is applied for splash screen both on the Server/Remote Administrator’s workstation and on the Client |
x32: (x32) | Type_view_dept_log | 0,1,2 | 0 | 1.0.0 and later | Specifies displaying the name of department in the log: 0 – do not add: Ivanov Ivan Ivanovich; |
x32: (x32) | URAttempts | 0 – 10000 | 3 | 1.0.0 and later | Sets the number of attempts to enter the user password |
x32: (x32) | URDelay | 0 – 10000 | 60 | 1.0.0 and later | Sets the delay period (sec) for re-entering the system |
x32: (x32) | virtualgrabber | 0, 1 | 0 | 1.0.0 and later | Defines whether it is possible to create a virtual video capture card or no |
x32: (x32) | SyncNotEmpty | 0, 1 | 0 | 1.0.0 and later | Defines the database synchronization algorithm: 1 – fast synchronization algorithm is in use; 0 – standard synchronization algorithm is in use |
x32: (x32)\Debug | counter_period | >=0 | 60 | 1.0.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 the parameter is 0, this information is not included to the log file |
x32: (x32)\ AxxonPSIMRunService | Restart AxxonPSIMOnLogonDisable | 0, 1 | 0 | 1.0.0 and later | 1 – Axxon PSIM installed as a Service is not restarted under the current user even for users belonging to the AxxonPSIMUsers group. 0 – Axxon PSIM installed as a Service is restarted under the current user only if the user belongs to the AxxonPSIMUsers group |
x32: (x32)\ AxxonPSIMRunService | CheckUserForRestartAxxonPSIMDisable | 0, 1 | - | 1.0.0 and later | 0 – Axxon PSIM installed as a Service is restarted (when entering the system) under the current user only if the user belongs to the AxxonPSIMUsers group 1 – Axxon PSIM installed as a Service is restarted (when entering the system) under the current user even if the user doesn’t belong to the AxxonPSIMUsers group. The settings of permissions are to be taken into account when using this key. If the permissions are set incorrectly, then some Axxon PSIM features can operate incorrectly |
x32: (x32) | ShowHiddenObjects | 0, 1 | 0 | 1.0.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 Axxon PSIM 1 – hidden objects are shown in the object tree in Axxon PSIM Axxon PSIM is to be restarted when the key value is changed |
x32: (x32)\ AxxonPSIMRunService\ | InheritServiceEnvironment | 0, 1 | - | 1.0.0 and later | The key is essential for proper operation of Axxon PSIM in MS failover cluster |
x32: (x32) | SortCamsById | 0, 1 | - | 1.0.0 and later | The key determines the order in which the list of cameras is sorted in the Monitor object settings panel and in the Monitor object function menu. 1—cameras are sorted by ID; 0—cameras are sorted by name |
x32: (x32) | EventProcessingThreads | >=0 | 0 | 1.0.0 and later | Key reserves the specified number of streams for events processing |
4-8 | Equal to CPU cores number | 1.0.0 and later | |||
x32: (x32)\Debug | DumpYUV | 0, 1 | - | 1.0.0 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: W – width; For example, file with resolution 640x480 in YUV420 color area will have the 640x480_22_chunk_0.yuv name |
x32: (x32) | settings_height | >0, depends on screen resolution | 438 | 1.0.0 and later | Sets the height of the object settings panel (in pixels) |
x32: (x32) | settings_width | >0, depends on screen resolution | 600 | 1.0.0 and later | Sets the width of the object settings panel (in pixels) |
x32: (x32) x64: (x64) | ATMSendSetup | 0, 1 | 1 | 1.0.0 and later | 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 |
x32: (x32) x64: (x64) | RegisterF10andF11 | 0, 1 | 1 | 1.0.0 and later | 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 Axxon PSIM restart is required. To disable F10 and F11 hot keys on the Remote Administrator's workstation, the key is to be created in the \HKEY_CURRENT_USER\Software\AxxonSoft\PSIM registry section. To disable F10 and F11 hot keys on the Remote Administrator's workstation 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) | DisableF8 | 0, 1 | 0 | 1.0.0 and later | 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 Remote Administrator's workstation, the key is to be created in the \HKEY_CURRENT_USER\Software\AxxonSoft\PSIM registry section. To disable F8 hot key on the Remote Administrator's workstation when operating under the Admin account, he key is to be created in the same registry section as on Server (x32)/(x64) |
x32: (x32) | check_digital | 0, 1 | 0 | 1.0.0 and later | When the key value = 1, video or archive period is exported from the Monitor interface using the admin password |
x32: (x32) x64: (x64) | CONNECT_ATTEMPTS | >=1 | 1 | 1.0.0 and later | The key sets the number of attempts to connect the Client to Server. The key is specified on the side of the Client |
x32: (x32) x64: (x64) | FLUSH_TIMER_TIMEOUT | >0 | 10 | 1.0.0 and later | 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 due to decreasing resources when sending a large amount of small messages. However, time of response to events can also increase. The key is created by default |
x32: (x32) x64: (x64) | UnloadDelay | 0 to 60000 ms | 5000 | 1.0.0 and later | The key sets the delay between disabling Guardant and unloading Axxon PSIM. The delay is essential for the FORCED_OFF event generation of the PSIM_HOST object and in case this event is used in scripts or programs, these scripts and programs are executed. If UnloadDelay = 0, unloading is performed without any delays, i.e. script/program in which the specified event is used, cannot execute |
x32: (x32) x64: (x64) | SortSubItems | 0, 1 | 0 | 1.0.0 and later | 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 |
x32: (x32) x64: (x64) | ShowSmallBarAlways | 0, 1 | 0 | 1.0.0 and later | The key enables displaying the main control panel of Axxon PSIM on the screen. 0 – the main control panel is displayed when pointing to the upper right corner of the screen 1 – the main control panel is always displayed in the upper right corner of the screen |
x32: (x32) x64: (x64) | UpdateProtocolPeriod | > 0 | - | 1.0.0 and later | 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). Recordings storing period of which has expired are deleted at midnight every 24 hours in case the license is activated |
x32: (x32) x64: (x64) | permissible_memory_limit | >0 | 2000 | 1.0.0 and later | The key sets the occupied memory threshold, reaching which the core starts receiving messages with a delay. The key must be used when module shuts down because of excessive memory consumption |
x32: (x32) x64: (x64) | MsgCompressOn | 0, 1 | 0 | 1.0.0 and later | 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 Note. If the key value = 1, the Web-Server doesn't work, because the Web-Server doesn't recieve compressed messages |
x32: (x32) x64: (x64) | user_card_info_on | 0, 1 | 0 | 1.0.0 and later | The key is used with the ACS/FAS integration modules that are the part of ACFA PSIM. It enables displaying the access card number for all events associated with the cards in the Event Viewer. |
x32: (x32) x64: (x64) | CriticalErrGui | 0, 1 | 0 | 1.0.0 and later | It enables displaying messages about database connection errors regardless the debugging mode (see the description of the Debug key and Enabling and configuring the debug mode of Axxon PSIM section). 0 – messages about database connection errors are displayed only at Debug 4 debugging levels 1 – messages about database connection errors are displayed regardless the selected debugging level |
x32: (x32) x64: (x64) | clean_object_lists | 0, 1 | 0 | 1.0.0 and later | The key determines if cameras are removed from the list in the Video surveillance monitor when the Camera object is removed. 1—when the object is removed, the camera is removed from the list in the Video surveillance monitor 2—when the object is removed, the camera isn't removed from the list in the Video surveillance monitor. When you recreate the Camera object with the same identifier, it is automatically added to the list of cameras in the Video surveillance monitor |
x32: (x32) x64: (x64) | AxxonPSIMCloseTimeout | >0 | 60000 | 1.0.0 and later | It sets Axxon PSIM close timeout in milliseconds. If psim.exe process does not close during this timeout, then it is terminated forcefully. If there is no key, then timeout is 60 seconds |
x32: (x32) x64: (x64) | SaveIncommingMsg | 0, 1 | 0 | 1.0.0 and later | 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 psim.exe the psim.exe.cd.log file is stored in the Axxon PSIM 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 Axxon PSIM is restarted. 0 – recording of incoming messages is disabled 1 – recording of incoming messages is enabled |
x32: (x32) x64: (x64) | BackupFolder | Address of a local or network folder | - | 1.0.0 and later | Specifies the address of the folder to save a backup copy of the database created by a macro or using the idb.exe utility. For example, C:\Documents and Settings\AVP\Desktop\Backup If the database copy is to be stored on the network disk, then the UNC path to the network folder (with the recording access) is to be specified on the disk in the \\ServerName\ShareName format. Take into account the fact that all network resources that require additional authentication are to be enabled using the same username as for running the SQL Server service. See also Creating the database backup copy |
x32 and x64: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon | Shell | Any text value | explorer.exe | 1.0.0 and later | If the key value contains the "explorer" string (for example, the default value, "testexplorertest" or "123explorertest125" values), the Save button is displayed in the About program... window. Otherwise, the Save button is hidden |
x32: (x32)\ AxxonPSIMRunService x64: (x64)\ AxxonPSIMRunService | PsimUserGroup | Any text value | 1.0.0 and later | If Axxon PSIM is installed as a Service, and you need to use a user group other than PsimUsers, then specify the required user group name in this key | |
x32: (x32) x64: (x64) | monitor_refresh_delay | 10 -30000 | 3000 | 1.0.0 and later | 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 |
x32: (x32) x64: (x64) | DisableUpdateProtocol | 0, 1 | 0 | 1.0.0 and later | The key disables the filling of the UPDATE_PROTOCOL table storing information about changes of Axxon PSIM object settings (except the User objects). 0 – the UPDATE_PROTOCOL table is filled 1 – the UPDATE_PROTOCOL table is not filled |
x32: (x32) x64: (x64) | max_disp_menu_items | >0 | 50 | 1.0.0 and later | If the number of screens assigned to a computer is larger than that specified in the key, scrolling the list of screens with the mouse wheel becomes available (if the size of the list is larger than the size of a computer monitor). The key is set on each Server and Client where this function is required |
x32: (x32) x64: (x64) | URM_ProcessWait | >0 | 10000 | 1.0.0 and later | 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 |
x32: (x32) x64: (x64) | show_responsible | 0, 1 | 0 | 1.0.0 and later | The key enables the display of users responsible for the region (if assigned) in events from objects related to the regions:
The key is created on the Server |
x32: (x32) x64: (x64) | NotifyExpireLic | 0, 1 | 0 | 1.0.0 and later | The key enables the event showing the days left to the license expiration (see SLAVE Computer) |
x32: (x32) x64: (x64) | sync_timeout | >0 | 600 | 1.0.0 and later | The key sets the time period in seconds allocated for synchronizing the database when starting Axxon PSIM software. The key must be created on the Server, where synchronization with another server occurs. See also Configuring database synchronization |
x32: (x32) x64: (x64) | ShowPanelByKey | 0, 1 | 0 | 1.0.0 and later | 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 |
x32: (x32) x64: (x64) | IntegrityCheck | 0, 1 | 0 | 1.0.0 and later | Enables distribution integrity check when starting Axxon PSIM software package. The following files are checked:
If any of them is missing or changed, the message "The integrity of the distribution package is broken. Reinstall Axxon PSIM" is displayed in the launch window, and the Axxon PSIM start interrupts |
x32: (x32)\Display x64: (x64)\Display | DISPLAY_MAX_NUM | 1-1000 | 500 | 1.0.0 and later | The key sets the maximum number of Display objects that can be assigned to one computer |
x32: (x32)\ x64: (x64)\ | ADSyncOnStart | 0, 1 | 0 | 1.0.0 and later | The key enables synchronization with Active Directory when starting Axxon PSIM software. 0 – synchronization with AD when starting Axxon PSIM is disabled 1 – synchronization with AD when starting Axxon PSIM software is enabled |
x32: (x32)\ x64: (x64)\ | cur_monitor | >0 | not set | 1.0.0 and later | 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 Axxon PSIM 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 |
x32: (x32)\Macro x64: (x64)\Macro | UseHotKeys | 0, 1 | 1 | 1.0.0 and later | The key disables hot keys for macros. 0 – hotkeys in macros are disabled 1 – hotkeys in macros are enabled |
x32: (x32) x64: (x64) | SocketReadSize | >0 | 32768 | 1.0.0 and later | The key sets the size of the buffer to receive the TCP transport layer in bytes. Examples of values: 262144 (0.25 MB), 1048576 (1 MB), 10485760 (10 MB). Used together with the SocketWriteSize parameter |
x32: (x32) x64: (x64) | SocketWriteSize | >0 | 32768 | 1.0.0 and later | The key sets the buffer size to send the socket of the TCP transport layer in bytes. Examples of values: 262144 (0.25 MB), 1048576 (1 MB), 10485760 (10 MB). Used together with the SocketReadSize parameter |
x32: (x32)\InstallPropertyInfo x64: (x64)\InstallPropertyInfo | INSTALL_AS_SERVICE | 0, 1 | 0 | 1.0.0 and later | Enables Axxon PSIM installation as a Service. 0—standard Axxon PSIM installation 1—Axxon PSIM will be installed as a Service |
x32: (x32) x64: (x64) | core_module_name | psimCore_server64.exe, psim64.exe | Core_server64psim.exe | 1.0.0 and later | Sets the executable started file of the program module if Axxon PSIM is installed as a Service. psim.exe—the psim.exe program module is started when the PSIM Core Server service is started psim64.exe—the psim64.exe program module is started when the PSIM Core Server service is startedservice, that is, the AxxonSoft PSIM Core Server service starts the Core_server64.exe file of the program module |
x32: (x32) x64: (x64) | GlobalParamChange | 0, 1 | 1 | 1.0.0 and later | Enables the display of the Change parameter item in the context menu in the objects tree (see The Change parameter function). 1—the Change parameter function is displayed in the menu 0—the Change parameter function isn't displayed in the menu |
x32: (x32) x64: (x64) | LogUsersArray | 0, 1 | 1 | 1.0.0 and later | Disables logging of domain user account data to the psim.log file. 1—account data logging is enabled 0—account data logging is disabled |
x32: (x32) x64: (x64) | inc_server_send_full_event | 0, 1 | not set | 1.0.0 and later | Enables additional data logging for Incident server events: INC_SERVER||EVENT will contain the full parameters of the source event (see INC_SERVER Incident server). 1—data logging with full parameters of events 0—normal logging of event data By default, the key is not created. Note that if you enable full parameter logging, it will increase the size of the event database (by default, Incident server events are stored in the Axxon PSIM database in the PROTOCOL_INC_SERVER table) |
x32: (x32) x64: (x64) | UseWindowsEventLog | 0, 1 | not set | 1.0.0 and later | The key determines the mode of event logging to the Windows system log. 1—event logging is enabled 0—event logging is disabled By default, the key isn’t created |
x32: (x32) x64: (x64) | ScriptSlavesDefaultNotSelected | 0, 1 | 1 | 1.0.0 and later | The key determines the availability mode of the new script for all computers in the distributed configuration: 1—a new script is unavailable for all computers in the distributed configuration 0—a new script is available for all computers in the distributed configuration |
x32: (x32) x64: (x64) | OldScript | 0, 1 | NA | Determines the availability mode of Scripts and Programs objects 1—support both Scripts and Programs objects 0—support Scripts objects only; Programs objects aren't available in the System settings window | |
x32: (x32)\IpWizard x64: (x64)\IpWizard | AdditionalSearchTime | >=0 | 10000 | 1.0.0 and later | The key sets the additional wait time in milliseconds for a response from a device in the Ip Wizard window |
...
Abandoned objects detection tool of the Tracker object | |||||
---|---|---|---|---|---|
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | 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 | 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 | VMDA.unattendedObjectLongMemory | Comma-separated camera identifiers in the ‘camera id.1’ format.EXAMPLE , for 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,5" | - | 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 | 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) | 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 | 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 | 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 | 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 | 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 | VMDAFPS | >=-1 | 30 | 1.0.0 and later | Sets FPS to be sent to the tracker. |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | useLeftImprover | 0,1 | - | 1.0.0 and later | 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) |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | longShif | >=0 | - | 1.0.0 and later | Parameter of moving average accumulation is reasonable only when value 1 is assigned to the useLeftImprover parameter. It is not recommended to change value of parameter |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | longShiftUpdateThreshold | >=0 | - | 1.0.0 and later | Threshold of difference from a background below of which the long moving average is updated. It has a point if value 1 is assigned to the useLeftImprover parameter. It is not recommended to change the parameter value |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | useLeftImproverGeometry | 0, 1 | - | 1.0.0 and later | 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) |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | timeShift | >=0 | - | 1.0.0 and later | Time period in seconds after receiving a frame from video analytics repository, during which item in the frame will be analyzed for "invalidity". Operates only when the useLeftImproverGeometry key is enabled. The more this time period the longer item is analyzed and analysis is more authentic, but the more unlikely the item will be removed from the frame by the time of analysis completion |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | timeLife | >=0 | - | 1.0.0 and later | Time period during which left-off item frame will be sent after its recognition by analyzer of post processing video analytics repository. It is in use only when the useLeftImproverGeometry key is enabled |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | maxDeltaInside | 0-255 | - | 1.0.0 and later | Value of maximal difference of average color in the left-off item frame at the moment of frame receiving from video analytics repository and at the moment after time specified by the timeShift key. The less value, the more strict condition and the less number of items (left-off items) satisfying this condition |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | minDeltaOutside | 0-255 | - | 1.0.0 and later | Minimal difference of average color in the left-off item frame received from video analytics repository from average color around the frame, at which the frame will be further analyzed and won't be considered as invalid trigger. It is in use only when the useLeftImproverGeometry key is enabled. The higher value, the more strict condition and the less number of items (left-off items) satisfying this condition |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | useFilterFrame | 0, 1 | 0 | 1.0.0 and later | 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 |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | VMDA.determineNoise | 0,1 | 1 | 1.0.0 and later | Enables the noise determination function on the video and when smart video detection tools operate |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | VMDA.determineGivenTaken | IDs of cameras, comma-separated | - | 1.0.0 and later | 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 |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | VMDA.determineHumanCar | IDs of cameras, comma-separated | - | 1.0.0 and later | 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 |
x32: (x32)\Video\VMDA x64: (x64)\Video\VMDA | VMDA.filterGivenOrTaken | The VMDA detector identifier and the operation mode separated by the dot "." The pairs of values are separated by a comma "," or a semicolon ";" | 2 for all VMDA detectors | 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 |
x32: (x32)\Video x64: (x64)\Video | live_time | 0 – 2 147 483 648 | - | 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 |
x32: (x32)\Video x64: (x64)\Video | vmda_color | 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 |
...