Go to documentation repository
Page History
...
Video analytics | |||||
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32: (X32)\Video\Detectors\VmdaVMDA x64: (x64)\Video\Detectors\VmdaVMDA | VMDA.inactiveIntervalInactiveInterval | >0 | - | 4.9.0 | Key specifies time period in minutes, during which absence of detected objects by tracker is permitted. If the key is created, after the specified time and if there is no activity of VMDA detection, the message about inactivity will be generated. On default, this message is not generated. |
x32: (x32)\Video x64: (x64)\Video | VMDAEXT | 0, 1 | 0 | 4.9.8 | On default the key is not created that corresponds to value 0. The key is for separating VMDA tracker processes to the single process. It's recommended to do to increase stability and reliability of the Intellect basic functional. Used CPU resources and memory are increasing while separating trackers to the single process. 0 – process of VMDA trackers is starting in the video.run process. 1 – process of VMDA trackers is starting in the single detector_ext.run process. Note. It's required to install the Intellect Detector Pack ( version>=2.1.0) for correct key operation. |
x32: (x32)\Video x64: (x64)\Video | VMDAEXT.RAM | >0 | 300 | 4.9.8 | The key is in use with the VMDAEXT key and sets the memory space in megabytes which can use the detectror_ext.run process. The process will be restarted if allocated memory is exceeded. |
x32:(X32)\Video\VmdaVMDA x64: (x64)\Video\VmdaVMDA | VMDA.useSpeedLimitTypeLessThan | VMDA detector IDs separated by comma or semicolon | - | 4.10.4 and later | The VMDA detection tool IDs separated by comma orsemicolon that should be triggered when the object speed is less than the speed configured for the VMDA detection tool. Note 1. If no ID is specified for this parameter, or there is no parameter at all, the detection tool is triggered when an object crosses the line in the selected direction with a speed that is approximately the same as the speed configured for the VMDA detection tool. Note 2. The same VMDA detector id can only be specified for either the VMDA.useSpeedLimitTypeLessThan or the VMDA.useSpeedLimitTypeMoreThan (see below) parameters. The simultaneous operation of both these parameters for the same VMDA detector is not allowed. |
x32:(X32)\Video\VmdaVMDA x64: (x64)\Video\VmdaVMDA | VMDA.useSpeedLimitTypeMoreThan | VMDA detector IDs separated by comma or semicolon | - | 4.10.4 and later | The VMDA detection tool IDs separated by comma orsemicolon that should be triggered when the object speed is greater than the speed configured for the VMDA detection tool. Note 1. If no ID is specified for this parameter, or there is no parameter at all, the detection tool is triggered when an object crosses the line in the selected direction with a speed that is approximately the same as the speed configured for the VMDA detection tool. Note 2. The same VMDA detector id can only be specified for either the VMDA.useSpeedLimitTypeLessThan (see above) or the VMDA.useSpeedLimitTypeMoreThan parameters. The simultaneous operation of both these parameters for the same VMDA detector is not allowed. |
х32: (X32)\Video\VMDA x64: (x64)\Video\VMDA | VMDA.ignoreAnaliticStream | 0, 1 | 0 | 4.9.8 and later | The key sets the camera stream used by the detection modules included in the Detector Pack subsystem. 0 - the Video Analytics stream is used. 1 - the Default stream is used. Note. If the camera is not used in the multi-thread mode, the first stream (the only one) will be used regardless of the key value. |
...