Go to documentation repository
...
Video archive files | |||||
---|---|---|---|---|---|
Registry section | String parameter | Available values | Default | Product version | Parameter in effect |
x32:(x32)\Video\FileSystem x64:(x64)\Video\FileSystem | FileReader.MMF | 0, 1 | 0 | 1.0.0 and later | 0 – during the playback, the video archive fragments are read into RAM by one frame 1 – during the playback, the video archive fragments are read into the RAM all at once |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.NotifyCoreFrameSkipped | 0, 1 | 1 | 1.0.0 and later | The key enables FRAME_SKIPPED event (see CAM Camera). 0 – the FRAME_SKIPPED event is not generated, core load is reduced 1 – the FRAME_SKIPPED is generated, there is a risk of buffer overflow |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.RecordingStateChangeDelay | >30 | 30 | 1.0.0 and later | The key sets in seconds the delay period between the state changes of frames skipping. Accordingly, the FRAME_SKIPPED\FRAME_SKIPPED_STOP events won’t be generated more often than the period specified in the key. See CAM Camera |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.MaxSkippedFramesByPeriod | >0 | 50 | 1.0.0 and later | The key sets the minimum number of skipped frames for the period (the period is set in the FileSystem.RecordingStateChangeDelay key), during which the FRAME_SKIPPED event will be generated. See CAM Camera |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.NotifyCoreFileSystemError | 0, 1 | 1 | 1.0.0 and later | The key enables the generation of camera events FILE_REC_ERROR and FILE_REC_OK (see CAM Camera). 0 – FILE_REC_ERROR and FILE_REC_OK events are not generated, the load on the core is reduced 1 – FILE_REC_ERROR and FILE_REC_OK events are generated, there is a risk of buffer overflow |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.MinMaxHoursFromNow | 0, 1 | 1 | 1.0.0 and later | The key enables the feature of counting down the storage period for the Keep no less than parameter from the last archive record timestamp (see also Configuring camera archive depth). 0 – the archive storage time is counted from the last archive record time stamp 1 – the archive storage time is counted from the current time |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.SaveUncompressed | 0, 1 | 0 | 1.0.0 and later | The key enables or disables compression of the video recorded on the disk. 0 – compressed video is recorded to the disk according to the settings of each camera 1 – uncompressed video is recorded from all cameras to disk, ignoring the compression settings specified for all cameras Note. This key is required for debugging. It is not recommended to change the value of this key |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.DeleteMinutes | >=10 | 60 | 1.0.0 and later | The key sets in minutes the time segments of the recorded archive that will be deleted when it is necessary to free up space. The smaller the value, the smaller segment will be deleted in one deletion iteration, but there will be more such iterations. This will speed up the deletion process and will not overflow the buffer |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.FlushFileBuffers | 0, 1 | 0 | 1.0.0 and later | The key specifies the method of clearing the internal data buffer of the OS file system record: 1—forced resetting of the internal buffers of the OS file system record (actual prohibition of record caching) 0—automatic (at the discretion of the system) resetting of the internal buffers of the OS file system record |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.MemFile | -1, 0, 1 | -1 | 1.0.0 and later | The key specifies the way the archive is recorded to the disk or network storage: 0—each frame is recorded to the disk at once. This value is not recommended to use for network storages 1—at first video is fully recorded to RAM (default video size is 1500 frames, it's specified by the Frame count parameter on the Settings panel of the Video subsystem section of the Tweaki.exe utility, or by the MaxFrames key), temporary files are not created. When the recording ends, it is recorded to the disk by parts, the size of which is set by the FileSystem.WriteBufferSize parameter (4 MB by default). Memory consumption highly increases in this case -1—at first video is recorded to the temporary file in RAM. The minimum size of the temporary file is limited by the FileSystem.PreAllocateFileSize key value. The maximum size of the temporary file is limited by the FileSystem.WriteBufferMemoryLimit key value. When the size of the temporary file reaches maximum value, it is recorded to the disk. Memory consumption highly increases in this case. By default, when installing Axxon PSIM, the key is not created |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.WriteBufferMemoryLimit | >=0 | 4 | 1.0.0 and later | The key sets the maximum possible size of the memory buffer for the channel; when this value is exceeded, the data from the buffer will be recorded to the archive. The unit of measurement is megabytes |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.PreAllocateFileSize | 0-200 | 10 | 1.0.0 and later | The key is used when FileSystem.MemFile=-1 (described above). Sets the minimum size of a temporary file in RAM in megabytes, i.e., a file of the specified size will be created immediately before writing to it |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.FastIndex | 0, 1 | 1 | 1.0.0 and later | The key enables fast index download. It is used by 64-bit modules only as memory consumption increases when reading and saving. Regardless of the key value, the fastIndex.index file is created in the VIDEO folder. This file helps to download indexes much faster. 0 – when Axxon PSIM is started, all indexes are downloaded, so no time is wasted for data loading 1 – when Axxon PSIM is started, the specified file is downloaded and the data on detailed index for each hour will be loaded if required |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.WriteBufferSize | >0 | 4 | 1.0.0 and later | The key specifies the size of the video data chunks in megabytes that are recorded to the disk simultaneously. If the size of the frame is less than the specified value, it is "glued" to the next frame. The key is used when the FileSystem.MemFile key value is 1 or -1 Note. See also WritingQueueSize |
x32: (x32)\Video x64: (x64)\Video | WritingQueueSize | >0 | 1001500 | 1.0.0 and later | The key sets number of frames storing in RAM until start of data record to buffer. The key can be used with any codec |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem | FileSystem.ReadRaw | 0, 1 | 0 | 1.0.0 and later | The key enables a more optimal read of video archive individual frames from the disk. It is created on the Server. 0 – optimization of video archive reading is disabled 1 – optimization of video archive reading is enabled |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem
| FileSystem.QueueRecorders | 0, 1 | 1 | 1.0.0 and later | The key specifies the number of channels of simultaneous recording to disk: 0—the maximum possible number of recording channels are used 1—one recording channel is used Attention! We don't recommend you change the value of the parameter yourself! Use the assistance of technical support specialists! |
x32: (x32)\Video\FileSystem x64: (x64)\Video\FileSystem
| FileSystem.RecorderTimeout | >=0 | NA | 1.0.0 and later | By default, the key isn't created. It specifies, in milliseconds, the time interval of delay before attempting to access the file subsystem. Attention! We don't recommend you change the value of the parameter yourself! Use the assistance of technical support specialists! |
...
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 |
...