Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.

Previous page Intellect Enterprise base version  Database tables reference guide for Intellect and vertical solutions Next page


Tables
Designations

The following designations are in the reference guide:

(x32) – HKEY_LOCAL_MACHINE\SOFTWARE\ITV\INTELLECT\ registry section for 32-bit operating systems

(x64) – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ITV\INTELLECT registry section for 64-bit operating systems

For the ATM-Intellect software:

(x32-ATM/Monitoring) – HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\VHostService registry section for 32-bit operating systems

(x64-ATM/Monitoring) – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\VHostService registry section for 64-bit operating systems

For the ATM Event Capture utility:

(x32-ATM Event Capture) – HKEY_LOCAL_MACHINE\SOFTWARE\ITV\EventATM registry section for 32-bit operating systems

(x64-ATM Event Capture) – HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ITV\EventATM registry section for 64-bit operating systems

General information on Windows OS registry and working with it is given in the Working with Windows OS registry section of the Administrator's Guide.


ACFA Intellect

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

Rovalant A6-A16 ISS 






x32: (x32)\Rovalant_A6_A16
x64: (x64)\Rovalant_A6_A16

access_point_count

-

10

4.7.6 and later

Internal module setting. You’d better not modify the key.

x32: (x32)\Rovalant_A6_A16
x64: (x64)\Rovalant_A6_A16

rele_count

-

20

4.7.6 and later

Internal module setting. You’d better not modify the key. 

Apollo (AAN 100, AAN 32, AIM-4, AIM-4SL)






x32: (x32)\Apollo
x64: (x64)\Apollo

DisableLogOffLineEvents

0, 1

0

4.7.4 and later

Disables event logging when the controller is in the offline mode.

x32: (x32)\Apollo
x64: (x64)\Apollo

EnableHardwareReset

0, 1

1

4.7.4 and later

Enables hardware reset before forwarding configuration.

x32: (x32)\Apollo
x64: (x64)\Apollo

nCardType

0, 1

0

4.7.4 and later

Defines the card type. When the value is 1, support for Weigand32 is enabled.

x32: (x32)\Apollo
x64: (x64)\Apollo

nPINType

0, 1, 2

1

4.7.4 and later

Defines whether PIN is in use:
0 – not is use;
1- PIN 4 figures;
2 - PIN 6 figures.

x32: (x32)\Apollo
x64: (x64)\Apollo

SetLinkParametersAfterReset

0, 1

1

4.7.4 and later

Sets link parameters after reset.

ABC (Access Net) 






x32: (x32)\ABC
x64: (x64)\ABC

UseDynamic

0, 1

0

4.7.4 and later

Defines whether the Dynamic checkbox is available in the controller settings. In this case configuration forwarding in a separate stream can cause module crash.

x32: (x32)\ABC
x64: (x64)\ABC

UseMultiThreaded

0, 1

0

4.7.4 and later

Sets the use of the multithreading mode.

Perco Card Reader






x32: (x32)\Perco CR
x64: (x64)\Perco CR

ReadTotalTimeoutConstant

> = 0

-

4.7.4 and later

Sets timeout of reader query. If connection is lost sometimes, then the value is to be increased.

PERCO-SYSTEM-12000L ACS 






x32: (x32)\Perco
x64: (x64)\Perco

AdditionNumberOfCard


0

4.7.4 and later

If the number of card is read with displacement (error of COM Server Perco), then the value of this parameter defines the displacement.

x32: (x32)\Perco
x64: (x64)\Perco

AutoconfigType

0, 1,2,3

0

4.7.5 and later

Sets auto configuration mode:
0 – feature is not available;
1 – controllers that do not exist are deleted;
2  - controllers that do not exist are deleted and new found controllers are stored at the end of the object tree;
3 – new found controllers are stored at the end of the object tree.

x32: (x32)\Perco
x64: (x64)\Perco

DisableOffLine

0, 1, 2

0

4.7.4 and later

0  - standard action;
1 - controller access  to all cards with  shift schedule is forbidden;
2 - controller access to all cards is forbidden.

x32: (x32)\Perco
x64: (x64)\Perco

RequestTime

> = 0

1000

4.7.4 and later

Sets the time period during which the log is read, at the end of this period the reading stops and commands are executed (ms).

x32: (x32)\Perco
x64: (x64)\Perco

SendLevelBeforePerson

0, 1

0

4.7.4 and later

Defines whether to send the access level after sending person to controller or not.

x32: (x32)\Perco
x64: (x64)\Perco

ShowSendLevel

0, 1

0

4.7.4 and later

Defines whether the Send access levels button is shown for Perco object in Intellect settings or not:
0 - disabled (by default);
1 – enabled.

x32: (x32)\Perco
x64: (x64)\Perco

Show_progress

0, 1

0

4.7.4 and later

Defines whether to show progress bar when forwarding configuration or not.

x32: (x32)\Perco
x64: (x64)\Perco

TimeOut

-

-

4.7.4 and later

Set the gateway query timeout.

x32: (x32)\Perco
x64: (x64)\Perco

VerifyLogMesDB

-

-

-

The key is not in use.

Rubeg






x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

ConvertUserBcpToUserIntellect

0, 1

0

4.7.4 and later

Defines whether to allow Rubeg users to access Intellect or not:
0 - forbid importing Rubeg users to Intellect;
1 - allow importing Rubeg users to Intellect.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

ShowError

0, 1

0

4.7.4 and later

Defines whether to show dialog boxes with Rubeg COM server errors:
0  - forbid displaying dialog boxes;
1 - allow displaying dialog boxes.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

UseThreadDynamicProcess

0, 1

1

4.7.5 and later

Sets the thread for forwarding user configuration:
0 - forwarding in the primary thread;
1 - forwarding in the secondary thread.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

UseCorrectDuplicateUsers0, 104.7.6 and later

1 - algorithm of correction of duplicated users is in use;
0 - algorithm of correction of duplicated users is not in use.

x32: (x32)\RUBEG8_ISB
x64: (x64)\RUBEG8_ISB

UseConfigurationManager0, 10ACFA 6.1

The key is required for operation of integration with Failover module.

0 – do not save Rubezh server configuration to DB.

1 – save Rubezh server configuration to DB.

If Rubezh server configuration is not saved to DB, then it is stored in rcf files. When moving configuration to backup server these files will stay at dead computer and become unavailable, i.e. all settings will be reset to their defaults.

NAC-501/W6500.CNT ACS controller






x32: (x32)\Nac\Dll
x64: (x64)\Nac\Dll

delay

> = 1

1

4.7.4 and later

Delay (ms) when sending users between them. Default - 1 (no delay).

x32: (x32)\Nac
x64: (x64)\Nac

Delay green led

> = 0

0

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after receiving the event.

x32: (x32)\Nac
x64: (x64)\Nac

Delay open door

> = 0

500

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after authorized access.

x32: (x32)\Nac
x64: (x64)\Nac

Delay prohibited access

> = 0

250

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after enabling the prohibited access mode.

x32: (x32)\Nac
x64: (x64)\Nac

Delay red led

> = 0

250

4.7.4 and later

Defines how much time (ms) the reader (NAC51P only) is excluded from the query after prohibiting access.

x32: (x32)\Nac
x64: (x64)\Nac

enable_thread

1

1

4.7.4 and later

Checkbox of forwarding configuration in a separate thread; the value is always 1 (do not modify). The key is out of date.

x32: (x32)\Nac
x64: (x64)\Nac

fqLinkSet

> = 0

1000

4.7.4 and later

Defines the rate (ms) of attempts to connect the reader if there is no connection.

x32: (x32)\Nac
x64: (x64)\Nac

FlagsLog

0x01 - erroneous file recording/reading
0x02 - sent commands
0x04 - poll
0x08 - erroneous answers to sent commands
0x10 - erroneous answers to poll commands
0x20 - the reader is occupied, repeat is in nn ms
0x40 - card status confirmation
0x80 - master card is shown
0x100 - door open/close
0x200 - TIMEOUT

0x02F9

4.7.4 and later

Sets bit values for logging to log file (what to log).

x32: (x32)\Nac\Dll
x64: (x64)\Nac\Dll

show_progress

0, 1

1

4.7.4 and later

Defines whether to show the progress when forwarding the configuration.

SATEL FAS ACS






x32: (x32)\Satel
x64: (x64)\Satel

Get_Outputs

0, 1

1

4.7.4 and later

1 - Allow getting relay states;
0 - Forbid getting relay states.

x32: (x32)\Satel
x64: (x64)\Satel

Get_Troubles

0, 1

1

4.7.4 and later

1 - Allow getting states of troubles;
0 - Forbid getting states of troubles.

x32: (x32)\Satel
x64: (x64)\Satel

Timeout

Any positive number

300

4.7.4 and later

Timeout of getting next message byte from the controller, ms.

x32: (x32)\Satel
x64: (x64)\Satel

Transmit_Cmd_Timeout

Any positive number or 0 to forbid receiving states

 

1000

4.7.4 and later

Rate of getting states (relay and troubles) in ms.

x32: (x32)\Satel
x64: (x64)\Satel

Verify_Link_Timeout

Any positive number

500

4.7.4 and later

Max. waiting time (ms) of getting an event from controller.
If the value is exceeded, then module considers that there is no connection with controller.

"HoneyWell N1000" (Northern Computers)




x32: (x32)\nc

x64: (x64)\nc

bLogReact0, 114.7.4 and laterDisplaying incoming reactions in the debug window of the module and recording them to the log file.

x32: (x32)\nc

x64: (x64)\nc

bLogEvent0, 114.7.4 and laterDisplaying incoming events in the debug window of the module and recording them to the log file.

x32: (x32)\nc

x64: (x64)\nc

bLogCOM_Write0, 114.7.4 and laterDisplaying instructions sent to the terminal. Used for debugging.

x32: (x32)\nc

x64: (x64)\nc

bLogCOM_Read0, 114.7.4 and laterDisplaying transactions (events), received form the terminal, in the debug window of the module. Used for debugging.

x32: (x32)\nc

x64: (x64)\nc

bLogCOM_ReadAnswer0, 114.7.4 and laterDisplaying responses to the sent instructions in the debug window of the module. Used for debugging.

VMS (Visitor Management System)






x32: (x32)\id_limit
x64: (x64)\id_limit

PERSON_MINID

1-99999

-

4.7.6 and later

These keys are created to generate disjoint IDs of objects on different computers.
PERSON_MINID - PERSON_MAXID – allowed range of user IDs to edit access control service.
If PERSON_Restrict = 0, then keys are not active.

x32: (x32)\id_limit
x64: (x64)\id_limit
PERSON_MAXID1-99999-4.7.6 and later
x32: (x32)\id_limit
x64: (x64)\id_limit
PERSON_Restrict0, 104.7.6 and later
Photo ID




x32: (x32)\

x64: (x64)\

Note. If this section has not been created, then the system will look for the key in the section.

HKEY_CURRENT_USER\Software\ITV\INTELLECT\

 NOT_DELETE_PHOTO 0, 1 0 ACFA 6.0

In ACFA 5.4 and later versions it is possible to delete irrelevant photos in the Photo identification module: when the Photo identification module gets an event and if there is no photo on the Server that gets the event, then this photo is considered irrelevant and the clients connected to the Server get a command to delete the photo.

They key allows keeping irrelevant photos on the computer where the key value is 1.

0 – delete irrelevant photos on the computer.

1 – do not delete irrelevant photos on the computer.

Access Manager




x32 and x64: HKEY_CURRENT_USER\Software\ITV\INTELLECT\Account Manager(n*)\Folder name GUID**

Note 1. n* is Access Manager object ID in Intellect.

Note 2. Folder name GUID** is automatically generated. If Intellect is run with no authorization (i.e. no login or password entered at start), folder name is zero GUID, i.e. 00000000-0000-0000-0000-000000000000. If Intellect is run with authorization, folder name is this user's GUID, e.g. 3bf041df-8b39-e711-80b7-c0bfc074aae0.

ApplyOnEnter>=0-ACFA 6.5

The key enables confirmation (OK) by Enter in Full name of new user and Edit card dialog boxes.

0 – nothing happens when pressing Enter in these dialog boxes.

>0 – pressing Enter is equal to clicking OK in Full name of new user and Edit card dialog boxes.

x32 and x64: HKEY_CURRENT_USER\Software\ITV\INTELLECT\Account Manager(n*)\Folder name GUID**

Note 1. n* is Access Manager object ID in Intellect.

Note 2. Folder name GUID** is automatically generated. If Intellect is run with no authorization (i.e. no login or password entered at start), folder name is zero GUID, i.e. 00000000-0000-0000-0000-000000000000. If Intellect is run with authorization, folder name is this user's GUID, e.g. 3bf041df-8b39-e711-80b7-c0bfc074aae0.
RotateAngle0, 1, 2, 30ACFA 6.5

The key sets rotation angle for the template while printing.

0 – 0 degrees

1 – 90 degrees

2 – 180 degrees

3 – 270 degrees

Bolid SDK Orion v.2




x32: (x32)\SDKOrion

x64: (x64)\SDKOrion

AllUsersInDevices0, 10ACFA 6.0

The key specifies default value of the Save in device checkbox:

0 – checkbox is removed on default while user creation.

1 – checkbox is set on default while user creation.

x32: (x32)\SDKOrion

x64: (x64)\SDKOrion

SkipUnusedInputs0, 10ACFA 6.0

The key is in use if it's required to add only configured (not disabled) loops on the dual loop controller while automatic search and configuring of integration objects.

0 – disabled loops are adding to hardware tree.

1 – disabled loops are not adding to hardware tree.

TABLE OF CONTENTS


FACE Intellect

Registry section

String parameterAvailable valuesDefaultProduct versionParameter in effect

x32: (x32)\FRS
x64: (x64)\FRS

CpuCoreCount>0
6.0

The key determines how many CPU cores the face recognition module will operate (firserver.run process). All cores are in use by default.

х32: (х32)\FRS
x64:
(х64)\FRS

CpuCoreCountSearch>=018.2

The key determines how many CPU cores will be used for face search:

0—the number of cores specified in the CpuCoreCount key. The cores are used sequentially. Each core is assigned its own recognition instance.

1—only 1 fixed core is used

2—only 2 fixed cores are used

and so on

x32: (x32)\FRS
x64: (x64)\FRS
FaceLostAge>010006.0

The key sets the timeout upon which Face Server ‘loses’ the face if there is no new data about it.

x32: (x32)\FRS
x64: (x64)\FRS
GenFirsInDetector0, 116.0

Sets the parameters of generating and attaching face biometrics in the detection tool:

1 – Face detection tools generate and attach face biometrics to the photo. 

0 – Face detection tools do not generate face biometrics - the face is only captured.

Note. Face recognition Server that performs search in the user database checks up whether it has attached biometrics when it gets a face photo. If yes, then biometrics are not further generated for search in the database - data attached to the photo is in use. If no, then recognition Server generates biometrics itself using the photo. 

Generation of biometrics is a resource-intensive process unlike search by ready data - that is why this key allows distributing load among several Servers having only one Server working with the user database.
x32: (x32)\FRS
x64: (x64)\FRS
SaveUnrecognizedFaces0, 106.0 to 6.1

Specifies what data will be stored in the database when using the Face recognition Server:

1 - all captured faces.
0 - only the faces about which there are recognition results.

The key is in use in order to avoid the database overflow.

Note. Starting from version 7.0, to minimize the amount of information stored in the database, it is recommended to use the UseFaceDB key.

x32: (x32)\Video\FaceCapture
x64: (x64)\Video\ FaceCapture
timeUntilLost>01Intellect 4.10.0

The key is used to configure the face detection tool – it sets time on the expiry of which the face is considered lost.

For instance, if timeUntilLost = 1 and a man covers his face with the hands in front of the camera and then shows it again, then the face detection tool does not capture it as it considers that the face was lost for the time it was covered.

If the parameter value is 3, then the face will be detected in this case.
x32: (x32)\FRS
x64: (x64)\FRS
IgnoreSamePeople0, 106.1The key enables function of ignoring repeatedly recognized faces. While enabling this function all vectors of captured faces are saved in cache for the specified time interval. When new face is captured, its biometric vector is comparing with already existed vectors in cache. If it coincides with one of such vectors with specified similarity rate then it doesn't send to the further processing. Duration of vector storing in a cache is specified using the Skip repeated recognitions, sec parameter of the Face Recognition Server object. Similarity rate for comparison is came from the Similarity level parameter of the same object. See also Face Intellect software package. Administrator's Guide, section Configuring the captured faces recognition parameters.
x32: (x32)\FRS
x64: (x64)\FRS
ClearIgnoreCache0, 106.1The key enables cache clearing while using function of ignoring repeatedly recognized faces.
x32: (x32)\FRS
x64: (x64)\FRS
ClearIgnoreCacheTimeTime in HH:MM:SS format-6.1The key sets time when cache crearing is to be performed while using function of ignoring repeatedly recognized faces.
x32: (x32)\FRS
x64: (x64)\FRS
FaceDetectionPeriod>02506.1Specifies time period in milliseconds equal to frequency of new faces search on the image for the Tevian recognition algorithm. See also Face Intellect software package. Administrator's Guide.
x32: (x32)\FRS
x64: (x64)\FRS
FaceDBFull path to a local or network folder-7.0The key sets a folder for storage of images and vectors for captured and reference faces when UseFaceDB key is set to 1 or 2 (see below).
x32: (x32)\FRS
x64: (x64)\FRS
UseFaceDB0, 1, 227.0

The key sets the storage mode for metadata, images and vectors of captured and reference faces.

0 - metadata, images and vectors are stored only in the database.

1 - metadata, images and vectors are stored in the database, and images and vectors are also stored in a folder on disk. The path to the folder is set by the FaceDB parameter (you can specify both local and network folders).

2 - metadata is stored in the database, and images and vectors are stored only in a folder on disk. The path to the folder is set by the FaceDB parameter (you can specify both local and network folders).

Note 1. Metadata is stored in the database in the Hits table, regardless of the value of the UseFaceDB key.

Note 2. Images of reference faces are stored in the <Intellect software installation directory>\Bmp\Person folder, regardless of the UseFaceDB key value.

Note 3. Starting from Face Intellect version 7.1.0.1161 only the UseFaceDB = 2 mode is supported, which is set automatically when Face Intellect starts if a mode other than this is detected.

x32: (x32)\FRS
x64: (x64)\FRS
FaceDBFreeMB>010007.0

The key is used if the the UseFaceDB parameter value is 1 or 2 (see above). The key sets the size of free disk space in megabytes. Once the specified size is reached, the old images, vectors and metadata of captured faces will be deleted. The cleanup is performed on a loop in portions equivalent to 1000 megabytes.

x32: (x32)\FRS
x64: (x64)\FRS
RestPortport number100007.1The key is used in case the standard port 10000 used by the Face Recognition Server to communicate with the Face Recognition and Search client is occupied by a third-party application that can not be disabled. The key allows you to specify a new port number for communication between the server and the client.
x32: (x32)\FRS
x64: (x64)\FRS
CpuCoreCountAddPerson
>=007.1

The key defines the number of CPU cores where the vectors of persons are generated when adding a reference face to the database.

0 - vectors are generated on the number of cores specified in the CpuCoreCount key. The cores are used successively. Recognition sample is bound to each core.

1 - only 1 fixed core (different from those specified in CpuCoreCount) is in use when adding a reference face to the database.

2 - only 2 fixed cores (different from those specified in CpuCoreCount) are in use when adding a reference face to the database.

etc.
x32: (x32)\FRS
x64: (x64)\FRS
Face.HardwareCPU
0, 1, 2-7.1

The key defines the order of binding streams to CPU cores when generating vectors of persons.

no value or 0 - streams are bound randomly to CPU cores.
1 - streams are bound successively to CPU cores depending on their total number.
2 - streams are bound to first cores of each CPU.

x32: (x32)\FRS
x64: (x64)\FRS
Face.RecognizeFacesSeparately0, 107.3 and later

Mechanism of displaying faces. When a new mechanism of displaying is enabled, the photo in the list of captured faces is not duplicated - it is updated in the same cell while the tracker "sees" it.  

0 - new mechanism of displaying faces. 

1 - old mechanism of displaying faces. 

x32: (x32)\FRS
x64: (x64)\FRS
FaceDetector.SaveLastFaceCaptureFrame0, 107.1 and later

The key enables saving the last recognized face and all its necessary data to a file. This image file can be sent directly to the recognition server via the iidk_client utility.

0 - General operation mode.

1 - When the face is captured, the captureFrame (cam_N) .log file is created (where N is the camera number that captured the face) in the <Intellect Installer directory>\Modules64\Firserver folder\. This file will contain the last recognized face and all its necessary data. This image file can be sent directly to the recognition server via the iidk_client utility.

Note. The file is overwritten every time a new face is captured.

x32: (x32)\FRS
x64: (x64)\FRS
XSize>=019207.0 and later

The key restricts resolution (width) of the photo when adding it to the faces database.

Set greater value to the key if the following message appears when adding a face to DB: "Adding error. The face was not added. Insufficient image quality to add".

x32: (x32)\FRS
x64: (x64)\FRS
YSize>=010807.0 and later

The key restricts resolution (height) of the photo when adding it to the faces database.

Set greater value to the key if the following message appears when adding a face to DB: "Adding error. The face was not added. Insufficient image quality to add".
x32: (x32)\FRS\CustomAlgoritm
x64: (x64)\FRS\CustomAlgoritm
Visionlabs.DetectorAlgorithm1, 2, 318.20.557 and later

The key allows to select the face detection mode:

1 − V1,

2 − V2,

3 − V3.

Tevian and VideoIntellect 1.1




x32: (x32)\FRS
x64: (x64)\FRS
TevianAlgorithmNumber0, 107.0-7.1

The key enables selecting the face recognition and search algorithm.

0 – less resource intensive algorithm is in use

1 – more resource intensive algorithm is in use 

Important! Biometric vectors received using this algorithm cannot be used with alternative one. For proper operation of Face Intellect after changing this parameter biometric vectors are to be converted as described in  Switching between the face recognition modules section. 

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.DetectionFilterAlgorithm0, 107.3 and later

An alternative algorithm for filtering false triggerings of the tracker. This key is in use if Tevian.GlobalTrackingDetectionFilter=0 and Tevian.DetectionFilterValue > 0 (see the corresponding parameters below). 

0 - ALG1

1 - ALG2

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.DetectionFilterValue0-100507.3 and later

Configuring alternative algorithm filtering. It is in use if the value of Tevian.GlobalTrackingDetectionFilter is more than 0 (see the corresponding parameter below).

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.GlobalTrackingDetectionFilter0, 117.3 and later

Activates an additional check to filter out false triggerings of the tracker. If faces in masks are not recognized, it is recommended to disable this check, however, this can cause false triggerings of the tracker.

0 - disabled

1 - enabled.

Note. It is not recommended to change this parameter without first consulting with AxxonSoft technical support.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.DetectorAlgorithm0, 107.3 and later

Face detection operation mode (identification). The recommended parameter value is 0.

0 - ALG1

1 - ALG2

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.FaceDetectionPeriod>=03507.3 and later

This parameter affects the detector captioning capacity. If there is a great value, the tracks can rend.

Note. It is not recommended to change this parameter without consulting Tevian.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.FaceDetectorConfidenceThreshold>=0507.3 and later

Face detector confidence threshold (do not confuse with face quality).

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.IdentificationAlgorithm0, 1, 207.3 and later

The key enables selecting the algorithm for recognition and face search.

0 - ALG1 less resource-intensive algorithm is in use.

1 - ALG2 identification of the higher quality, but more resource-intensive.

2 - PRECISE the highest quality of recognition, but the most resource-intensive. This algorithm is recommended if significantly less time is spent on face recognition than on detection (if there are few people in the frame).

Important! Since the biometric vectors received by one algorithm cannot be used by another, then after changing the algorithm, the biometric vectors are automatically recreated. The biometric vectors can also be recreated manually (see Switching between the face recognition modules and SDK versions).

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.TrackBestFramesCount>=017.3 and later

Specifies the number of seconds to accumulate the best frames of a track for recognition. The increase in time makes it possible to average out the recognized face characteristics, but it can result in the poorer accuracy of the face characteristics recognition.

Note. For example, if the 1 second value is set, the average error in determining the age will be 2-3 years, and if the 5 seconds value is set, it will be 3-4 years.

x32:(x32)\FRS\CustomAlgoritm
x64:(x64)\FRS\CustomAlgoritm
Tevian.TrackerMaxLostTime>=05007.3 and later

Time since the last recognition after which the track is considered ended.

Note. It is not recommended to change this parameter without consulting with AxxonSoft technical support.

x32: (x32)\FRS\CustomAlgoritm
x64: (x64)\FRS\CustomAlgoritm
Tevian.EyesClosedDetectorThreshold>=0507.3 and later

Sets the sensitivity of the closed eyes recognition. The higher the value, the less sensitive the closed eyes detector.

x32: (x32)\FRS\CustomAlgoritm
x64: (x64)\FRS\CustomAlgoritm
Tevian.IgnoreBestFrames0,108.2.0.550 and later

Specifies which frames will be recognized.

0 − only the best frame defined by Tevian will be recognized.

1 − all frames will be recognized, as a result the quality of recognition increases, but the CPU load increases, too

x32: (x32)\FRS
x64: (x64)\FRS
GenerateEyesClosedEvent0, 107.3 and later

Activates the Eyes closed event generation when closed eyes are detected.

x32: (x32)\FRS
x64: (x64)\FRS
FaceTracker.LogTrackerQuality0, 107.3 and laterThe key enables logging of every face capture event in the general log file of the Face Recognition Server debugging window, where additional information is displayed, such as: the quality of the captured face, the number of all captured faces, the number of high-quality faces, etc. (for details, see Debug window).
x32: (x32)\FRS
x64: (x64)\FRS
IsProcessObject
0, 117.4 and later

Enables the launch of each Face Recognition Server in a separate process.

0 - all Face Recognition Servers launch in the same process.

1 - each Face Recognition Server is launched in a separate process.

x32: (x32)\FRS
x64: (x64)\FRS
ThreadAffinity.Ignore0, 107.4 and later

Enables ignoring threads affinity to kernels inside firserver.run.

0 - ignoring threads affinity to kernels is disabled.

1 - ignoring threads affinity to kernels is enabled. The key is used in conjunction with the IsProcessObject=0 key.

x32: (x32)\FRS
x64: (x64)\FRS
ResizeWidth
>=007.4 and later

Sets the video resolution that is sent from cameras to all Face Detection modules.

Actually, the width of the video image is set, and the height is adjusted automatically based on the aspect ratio of the original video. For example, if the original video has a resolution of 2560x1920, then if you set the value to 960, then the video will be converted to a resolution of 960x720.

If the value is set to 0, then the video image will be received in its original resolution.

x32: (x32)\FRS\Thermal
x64: (x64)\FRS\Thermal
SaveThermalJson
0, 107.4 and later

Enables saving all json and images received from the thermal camera during face recognition to the folder. The data from the camera will be saved at the following address:

  • In case of face recognition: <Intellect installation directory>\Modules64\Firserver\ThermalImages\{Face detection tool ID}
  • In case the face is not recognized: <Intellect installation directory>\Modules64\Firserver\ThermalImages\{Face detection tool ID}\NoFaces

0 - data from the thermal camera is not saved to the folders

1 - data from the thermal camera is saved to the folders

x32: (x32)\FRS\Thermal
x64: (x64)\FRS\Thermal
ForceProcessWholeImage
0, 107.4 and later

The key is used in case the Combined work with thermal camera and Get photo from thermal camera checkboxes are set on the settings panel of the Face Recognition Server object.

Enables the face search throughout the entire frame if a face was not previously recognized due to incorrect coordinates of the face frame received from the thermal camera.

Details on this mode:

  • The number of recognitions and the system load will increase.
  • The negative face images will be displayed in the Face recognition and search interface module.
  • The same temperature will be indicated for all recognized faces in the frame.

0 - Unrecognized faces are ignored.

1 - Enables the face search throughout the entire frame if a face was not previously recognized.

x32: (x32)\FRS\Update
x64: (x64)\FRS\Update
Update.CpuCoreCount
>=118.0 and later

Sets the number of threads on which the biometric vectors are re-generated when switching between different face recognition modules or SDK versions.

TABLE OF CONTENTS


AUTO Intellect

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (x32)\LPRVIEWER
x64: (x64)\LPRVIEWER

protocollimit

<1000

-

4.7.5 and later

Sets number of lines shown in the protocol (this parameter is for testing only).

x32: (x32)\radar
x64: (x64)\radar

EmulateRefreshSpeed

1 - 2147483647

100

4.7.5 and later

Radar emulator. Sets time period (ms) for refreshing data about speed in the radar emulation mode. 0 value blocks data refreshing.

x32: (x32)\radar
x64: (x64)\radar

WriteSpeedOnTitles

0, 1

0

4.7.5 and later

Defines whether to write speed values on titles.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

DisableUrmOutput

0, 1

0

4.7.5 and later

Disables results output.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

GlobalUrmDebug

0, 1

0

4.7.5 and later

Enables displaying CZoneInfo objects in dbgview. 

x32: (x32)\URMLPR
x64: (x64)\URMLPR

OneSpeedDetect

0, 1

0

4.7.5 and later

Enables filtering the radar speed values.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

ReadSpeedFromTitles

0, 1

0

4.7.5 and later

Defines whether to read speed from titles or not.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TestWidth

-

0

4.7.5 and later

 Image width change (internal use only).

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TestHeight

-

0

4.7.5 and later

 Image height change (internal use only).

x32: (x32)\URMLPR
x64: (x64)\URMLPR

Time

-

-

4.7.5 and later

Saves time of the last viewed archive fragment in the test mode.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

UrmDebug

0, 1

0

4.7.5 and later

Enables recording of  tiff files to UrmDebug folder.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

UrmSendProcessEvents

0, 1

0

4.7.5 and later

Sends beginning (VEHICLES_BEGIN) and ending (VEHICLES_END) parameters of license plate recognition to the core.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

UseTry

0, 1

0

4.7.5 and later

Enables the seh module.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

WriteUraganErrorBuf

0, 1

0

4.7.5 and later

If failure occurs, the uragan.buf file is created (only of UseTry=1). 

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

CountryName

Text

RUS

4.7.5 and later

Sets the test country name.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

Enabled

0, 1

0

4.7.5 and later

Enables/disables test.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

ExecuteSecond

> = 0

3

4.7.5 and later

Sets time of test execution.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

Number

Text

M038EH150

4.7.5 and later

Sets the test number.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

PlateHeightPercent

> 0

15

4.7.5 and later

Sets the test license plate height.

x32: (x32)\URMLPR\UnitTest
x64: (x64)\URMLPR\UnitTest

PlateWidthPercent

> 0

25

4.7.5 and later

Sets the test license plate width.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

ParkingMode

0, 1

-

5.0

Enabling the parking mode for the CARMEN-Auto recognizer:

1 – parking mode is enabled. Recognition starts at ULPR|START reaction. As soon as one license plate is recognized, the recognition stops.

0 – parking mode is disabled. Recognition continues till getting the ULPR|STOP reaction. 

Important! For correct operation of the key make sure that the Enable on motion detection trigger checkbox is set on the settings panel of the LPR channel object corresponding to the CARMEN-parking recognition module (see Setting the joint operation of the LPR channel and the motion detector of the Intellect platform).

Note. The ULPR|START and ULPR|STOP reactions are created using the scripts. Operator command, sensor triggering, motion detection tool triggering, etc. can cause the reaction.

5.5 and later

Enabling the parking mode for the CARMEN-Auto recognizer:

1 – parking mode is enabled. Recognition starts at ULPR|START reaction. As soon as one license plate is recognized, the recognition stops.

0 – parking mode is disabled. Recognition continues till getting the ULPR|STOP reaction. 

Note. If you set the 1 value on the settings panel of the LPR channel object, the Enable on motion detection trigge checkbox will be automatically set without the possibility of removing it until this key value is set to 0 (see Setting the joint operation of the LPR channel and the motion detector of the Intellect platform).

Note. The ULPR|START and ULPR|STOP reactions are created using the scripts. Operator command, sensor triggering, motion detection tool triggering, etc. can cause the reaction.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

SaveRawRecognitionResult0,105.1

When value = 1, the key allows saving frames transmitted from Intellect to the CARMEN Parking / CARMEN-Auto module.

  • For CARMEN Parking the frames are saved to the following folders:
    < Intellect installation folder>\Modules64\UrmLpr\CPD_RawResults\idDetector\ - frames with data for recognition.
    <Intellect installation folder >\Modules64\UrmLpr\CPD_RawResults\idDetector\NotFound – frames with no data for recognition.If value = 0, then frames are not saved.
  • For CARMEN Auto the results are stored to the <Intellect>\Modules64\UrmLpr\CarmenResults\idDetector\ folder. The results are represented by pairs of files: ‘<recognition time in UTC format>.bmp’ file (with a frame to be recognized) and xml file with settings of the recognizer and recognition results.

  • If the module is restarted, the Apply button is clicked or 5000 files are saved, then the specified folder and the data in it are automatically deleted and the folder is recreated. 

When value = 1, frames are not saved.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TrackOnlyRedLight0, 115.1When value = 1, the key allows fixing violations by the traffic violations detection (crossing the stop line, stop over crosswalk line, running a red light) only for vehicles which crossed the stop line on red light.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

MaxStoppingSpeed0 - 1000010005.1Controls maximal speed in relative units (relatively from width and height of frame) at which the vehicle is still considered as the stopped vehicle (for the Stop over crosswalk line violation).

x32: (x32)\URMLPR
x64: (x64)\URMLPR

RayHardwareDelay>005.2

Sets time (in milliseconds) corresponding to the delay with which events about green/red traffic lights are received.

Example. If the key value is RayHardwareDelay=2000 and an event is received at 12:00:00, then the system thinks the event is received at 11:59:58.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

TimestampFontSize>=1391395.2The key sets the text font size on the photo of the fine (containing date and time). The value is font size multiplied by 10. For instance, if the key is 139, then the font size will be 13,9pnt.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

ReadRayFromTitles0, 105.3

The key enables the multi-stream mode emulation in IntLab.

0 – license plates recognition is performed when the ray, specified on the settings panel of the IntLab-Carriages module object, is open or closed (see Setting up the IntLab-Carriages module).

1 – information about the time when the license plates recognition is to be started is taken from the titles overlaid on the video.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

ReadRayFromTitles0, 105.5

The key includes the multichannel mode emulation for the IntLabmodule.

0 –  LP number recognition is carried out using macro specified on the IntLab module object settings panel (see Setting up the IntLab module).

1 –  when it is necessary to start the LP number recognition, the information on the time of occurrence is taken from subtitles added to a video.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

PlateImprover0, 1, 205.3

The key sets an algorithm of frame preparation before sending it to the Carmen license plate recognition module:

0 – frames are sent to the Carmen license plate recognition module without pre-processing.

1 – rectangular areas that may contain a license plate are searched in the frame. Only those rectangular areas that may contain a license plate are then forwarded to the Carmen license plate recognition module.

2 – if any rectangular area that may contain a plate number is detected on the frame, the frame in whole is forwarded to the Carmen license plate recognition module. If the Carmen license plate recognition module detects a license plate, it tries to find another plate number, and time for recognition increases as a result.

3 – if any rectangular area that may contain a plate number is detected on the frame, the frame in whole is forwarded to the Carmen license plate recognition module. If the Carmen license plate recognition module detects a license plate, it does not try to find another license plate.

0, 1, 2, 35.4

x32: (x32)\URMLPR
x64: (x64)\URMLPR

 SpeedField"FASTEST", "STRONGEST""FASTEST"5.4

"FASTEST" – a speed trap sends speed of the fastest object to the Intellect software

"STRONGEST" – a speed trap sends speed of the biggest object to the Intellect software

Important! If values other than above are specified for the key, the Intellect software does not recieve speed data from speed traps.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

Compress0, 115.2The parameter is intended for disabling compression when transferring video from the video subsystem (the Camera object) to the LPR channel, if the video subsystem and the LPR channel are on the same local computer. This allows reducing the load on the Server processor.

0 – the video is transmitted to the local LPR channel without compression.

1 – the video is transmitted to the LPR channel after compression.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

RemoteLpr.NearestTimeFull path to local or network folder05.3

The key specifies the time difference (in milliseconds) between the moments of receiving the frame and license plate recognition event, sufficient to allow these events to be linked. The key is to be in use if data about recognized license plates are not displayed on the On-line monitor in Auto Intellect, although there are recognition events in the Debug window.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

RemoteLpr.x.NearestTime

X is the object identifier of the LP recognition channel in the Intellect software.

>=0

-5.5

For the specified object of the LPR channel with the assigned remote recognition module, the key sets the time difference in milliseconds between the moments of receiving the frame and event on the LP recognition enough to bind these events. You should use the key if the data on the recognized LPs are not displayed in the Active Monitor of the Auto Intellect although they are found in the Debug window and Event protocol.

x32: (x32)\URMLPR
x64:(x64)\URMLPR
LprDB.Path0, 1C:\ProgramData\AxxonSoft\LprDB5.5Specifies the local or network folder for storing the recognized LP images and vehicle images if the LprDB.Use key value 1 (see below) is specified.
x32: (x32)\URMLPR
x64:(x64)\URMLPR
LprDB.Use0, 115.5

Specifies the way of storing images.

0 – metadata and images are stored only in the database.

1 – metadata is stored in the database, and images are stored in the local or network folder. Full path to the folder is specified by the LprDB.Path key (see above).

Note. Recognized LP numbers information is stored in the database regardless of the LprDB.Use key.

x32: (x32)\URMLPR
x64:(x64)\URMLPR
LprDB.FreeMB>050005.5

Specifies the amount of free storage space in a directory. When its limit is exceeded, the overwriting process starts, rewriting the oldest images with the most recent ones. The key is used if the LprDB.Use key value is 1 (see above).

x32: (x32)\URMLPR
x64: (x64)\URMLPR
Alarms.LimitedByBestResult0, 105.5

The parameter allows ignoring all the tracks after the best frame detected by SDK.

0 - tracks after the best frame detected by SDK are not ignored.

1 - all the tracks after the best frame detected by SDK are ignored.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
Alarms.CrossWalkOne0, 105.5

The parameter activates alarm even if only one plate is recognized at the crosswalk (regardless of if the vehicle was moving or not).

0 - the system tries to detect crossing the crosswalk and only after that activates alarm.

1 - activates alarm even if only one plate is recognized at the crosswalk.

x32: (x32)\URMLPR
x64:(x64)\URMLPR
SaveRecognitionResult0, 105.5

Activates saving the recognition results to the hard drive. It is used for the Traffic violations detection module debugging.

0 - the recognition results are saved to the Auto Intellect DB.

1 - the recognition results are saved to the hard drive.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
AutoUragan.SDKVersion3.5, 3.73.55.5 

The key sets the SDK version which is being used in the Auto-Uragan software module.

Note. It is applied to all activated Auto-URAGAN software modules in Auto-Intellect.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
AutoUragan.Parallel0, 105.5

The key activates the LP numbers recognition simultaneously on several CPUs using parallel computing, which increases the performance of the Auto-URAGAN software module.

Note. It is applied to all activated Auto-URAGAN software modules in Auto-Intellect.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
AutoUragan.Kernels>=115.5

The key sets the number of CPUs that will be used for parallel computing by the Auto-URAGAN software module, if the parallel computing is activated.

Note. It is applied to all activated Auto-URAGAN software modules in Auto-Intellect.

x32: (x32)\URMLPR
x64:(x64)\URMLPR
VIT.TimeoutLostNumber>=005.5 

The key enables the tracking of the recognized number disappearance and sets the time in milliseconds, after which the lost number event will be generated if this number has disappeared from the camera field of view.

0 - tracking of the recognized number disappearance is disabled.

>1 - after the specified time has passed, if the recognized number disappeared from the camera field of view, a lost number event will be generated.

x32: (x32)\URMLPR
x64:(x64)\URMLPR
SaveFilterToDB0, 115.5 

The key enables saving the filtered numbers to the database.

0 - filtered numbers are saved to the database.

1 - filtered numbers are not saved to the database.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
RemoveNewLine0, 115.5 

The key activates the display of two-line numbers in the Event Log in two lines.

0 - two-line numbers are displayed in two lines.

1 - two-line numbers are displayed in one line.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
ExpiredPlateNumberMinutes>=055.2

The key sets the time in minutes, after which the violation detected by the main recognizer is ignored if the second recognizer, which is paired with the main one, also detected a violation.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
RestartTimeout0, 105.4

The key activates the automatic restart by the timeout for the Auto-URAGAN recognition module if no recognition results are received from it.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
IgnorePhotoFromBaseCamera0, 105.2

The key disables the receiving of photos from the main cameras of the recognizers.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
FrameBuffer>=005.4

The key sets the number of frames that are stored in the buffer for the CARMEN-Auto module. It is applicable if there is skipping of numbers, but it may cause a delay in the numbers recognition.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
FrameBuffer>=005.5 

The key sets the number of unprocessed frames that are stored in the buffer for all license plate recognition modules. It is applicable if there is skipping of numbers, but it may cause a delay in the numbers recognition.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
SaveRecognitionResult0, 105.5 

The key activates the saving of the number recognition result in the * .jpg format for the VIT module. As a result of the module operation, the AutoRecongitionResult folder will be created at the path: <Intellect installation directory>\Modules64\UrmLpr\, into which the files with the following names will be saved: recognizer ID in Intellect - recognized number - violation <if any>.jpg.

Note. This setting is required for debugging.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
InternalDirection0, 1, 21only 5.5 

The key sets the mode of determining the vehicle direction of movement of the vehicle.

0 - the direction is determined by the SDK.
1 - the direction is calculated by the position of the upper part of the number. If at the start of tracking the upper part of the number is lower than the upper part of the number at the end of tracking, then the direction is defined as “From the camera”, otherwise “To the camera”.
2 - the direction is calculated by the area of the LP number. If at the start of tracking the area of the number is larger than at the end of tracking, then the direction is defined as “From the camera”, otherwise “To the camera”.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
GueTrack.Timeout>=005.5 

The key sets the waiting time in seconds required for the number to appear if the vehicle is detected several times after stopping.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
Intlab.BestFrame0, 105.5 

The key activates the mechanism for the IntLab module that displays the frame where the number is the most visible, however, it causes a time delay in the displaying of the results.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
Alarms.LimitedByBestResult0, 105.5 

The key activates the discarding of all tracks after the best frame which was defined by the recognition module.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
Alarms.CrossWalkOne0, 105.5 

The key activates an alarm if there is at least one number identification at the pedestrian crossing. Vehicle traffic is not taken into account.

Note. By default, the system tries to determine the traffic on a pedestrian crossing.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
VehiclePlateSearch.Arabic0, 105.5 

The key enables the entry of an Arabic LP number in the search field.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
VehiclePlateSearch.PersianCalendar0, 105.5 

It is necessary to activate this key if the Persian calendar is used on the LPR channel.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
WritesAllSecondaryFrames0, 115.5 

Internal setting. Disables saving of frames from a synchronous video camera to the LprDB.Path folder and the [lprex].[dbo].[FramesSecondary] database.

0 - saving of all images from a synchronous video camera is disabled.

1 - saving of all images from a synchronous video camera is enabled.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

Ulpr.NumberDetectedRestartTimeout

>=005.5 

This key should be created if the LP recognition on one or more LPR channels stop from time to time. The key sets the time in minutes; if during this time no LPs were recognized, then the reaction is sent to the Intellect software core:

ULPR|N|NUMBER_DETECTED_TIMEOUT

where N is the identifier of the LPR channel object. Having received this reaction, the core re-sends the settings to the recognition module, thus emulating the Apply button click on the settings panel of the LPR channel object.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

AutoInfo.Use

0, 105.5 

The key automatically enables the display of the vehicle type in the Online Monitor window if the Vehicle Type Recognition Module (UrlServer) is activated.

0 - the detected vehicle type is not displayed in the Online Monitor window.

1 - the detected vehicle type is displayed in the Online Monitor window.

Note. The key value changes automatically.

x64: (x64)\URMLPRIntlabSDKx32PathString valueC:\Program Files (x86)\Intlab5.5

The key specifies the folder in which the Intlab x32 SDK is installed.

x64: (x64)\URMLPRIntlabSDKx64PathString valueC:\Program Files\Intlab5.5

The key specifies the folder in which the Intlab x64 SDK is installed.

x32: (x32)\URMLPR
x64: (x64)\URMLPR

AutoInfo.Url

http-address
http://127.0.0.1:8091/GetAutoInfo
5.5 

The key sets the http-address for the interaction with the Vehicle Type Recognition Module (UrlServer).

x32: (x32)\URMLPR
x64: (x64)\URMLPR
UrlServerFrameBufferWhole numbers-15.5 

The key sets the number of frames that are stored in the buffer for the Vehicle Type Recognition Module (UrlServer). It is defined as the approximate time spent by the vehicle in the frame multiplied by the fps of video.

If 0 - then the MMR (VIT) works.

If < 0 - then the Vehicle Type Recognition Module (UrlServer) works with the 350 value.

If > 0 - then the Vehicle Type Recognition Module (UrlServer) works with the specified value.

x32: (x32)\URL_SERVER
x64: (x64)\URL_SERVER
SavePicturesString value-5.5 

The key specifies the folder into which the frames processed by the Vehicle Type Recognition Module (UrlServer) will be saved (cropped frames containing only the vehicle). These frames are necessary for training a neural network (see Saving the frames processed by the Vehicle Type Recognition module).

x32: (x32)\URL_SERVER
x64: (x64)\URL_SERVER

VehiclePlateSearch.RightToLeft

0, 115.5 

When using the CARMEN-Auto software module and the Arabic license plate numbers recognizer, the key sets the sequence of Latin numbers and letters in the second line of the recognized LP number displayed in the Online monitor.

0 - Latin numbers are displayed first, then letters.

1 - Latin letters are displayed first, then numbers.

x32: (x32)\URL_SERVER
x64: (x64)\URL_SERVER
DeferLeft>02.05.6

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate width will be multiplied. The photo will be cropped from the left relative to the number plate at a distance equal to the product.

x32: (x32)\URL_SERVER
x64: (x64)\URL_SERVER
DeferRight>02.05.6

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate width will be multiplied. The photo will be cropped from the right of the number plate at a distance equal to the product.

x32: (x32)\URL_SERVER
x64: (x64)\URL_SERVER
DeferUp>021.85.6

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate height will be multiplied. The photo will be cropped from the top relative to the number plate at a distance equal to the product.

x32: (x32)\URL_SERVER
x64: (x64)\URL_SERVER
DeferDown>03.85.6

The key works only if saving the frames processed by the Vehicle Type Recognition module (UrlServer) is enabled. 

The key value indicates the coefficient by which the number plate height will be multiplied. The photo will be cropped from the bottom relative to the number plate at a distance equal to the product.

x32: (x32)\Video
x64: (x64)\Video
RandomOrder0, 105.6

The key allows you to send a message about the number, even if the frame dimensions, which are necessary for the correct calculation of the number plate coordinates, are not initialized. This solves the problem of incorrect linking of numbers when sending the number plate coordinates.

0 - a message about the number is not sent if the frame dimensions are not initialized.

1 - a message about the number is sent even if the frame dimensions are not initialized.

x32: (x32)\URL_SERVER\An
x64: (x64)\URL_SERVER\An
An.port>0201115.6Sets the port for connection to Axxon Next (see Setting up the joint operation of Auto Intellect and Axxon Next).
x32: (x32)\URMLPR
x64: (x64)\URMLPR
VehiclePlateSearch.ConnectTimeOut>=010Only 5.7

Sets the timeout in seconds for connecting to the selected Auto Intellect servers when the Event search in the Recognizers DBs window is opened. If the specified time is exceeded, connection attempts are stopped and a list of servers to which it was not possible to connect is displayed.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
LprDB.Log
0, 105.7

Enables recording of LP recognition logs to the Logs table of the lprex DB. The records in the table are cleared according to the specified records retention period in the database. Used for debugging.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
RestPortport number100015.6

The key is used if the standard port 10001 used by the LPR channel for communication with the Vehicle Tracer module client is occupied by a third-party application that cannot be disabled. The key allows you to set a new port number for communication between the server and client parts.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
ClearOnlyFirstPageDB0, 116.0

The key is used to control the number of events to be deleted from the Auto Intellect internal database.

0 - all records that exceed the specified amount of archive storage will be deleted from the database.

1 - a maximum of 1000 records will be deleted from the database with a 3-minute timeout.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
VehicleTracer.ShowDataFile0, 106.0

The key displays the data file about the triggered engine in the Online monitor window.

0 - the data file is not displayed.

1 - the data file is displayed.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
Carmen.DistanceX>=0105.7, 6.0The key is the minimum horizontal distance in pixels between the license plate characters. The key is used to insert a separator into the license plate. The separator will be added where the distance between the characters is maximum and at the same time it is not less than the value specified in the key. The key is only used for Arabic license plate numbers.
х32: (х32)\URMLPR
x64: (х64)\URMLPR
Carmen.ExcludeCountriesSpacecountry codes separated by a commanone5.7, 6.0The key defines the countries for which special characters won’t be displayed during license plate recognition. Country codes are specified separated by a comma in ISO 3166 Alpha-3 format, case-insensitive, e.g. VAT,ARE for Vatican, UAE
х32: (х32)\URMLPR
x64: (х64)\URMLPR
IgnoreRepeatTime >=005.7, 6.0

The key specifies the time in seconds, during which the repeated license plate recognitions on all channels within one physical server are ignored.

x32: (x32)\URMLPR
x64: (x64)\URMLPR
IsProcessObject0, 105.7, 6.0

The key enables the mode of evenly distributing the load on the CPU cores.

0—the mode isn't enabled

1—the mode is enabled

x32: (x32)\URMLPR
x64: (x64)\URMLPR
PicturesInNumberDetectedEvent 0, 105.7, 6.0

The key adds to the NUMBER_DETECTED event the image parameter that stores the image of the entire frame, and the image_plate parameter that stores the image of the cropped frame, encoded using Base64:

 0—the NUMBER_DETECTED event is generated without the image and image_plate parameters

1—the NUMBER_DETECTED event is generated with the image and image_plate parameters

TABLE OF CONTENTS

POS-Intellect

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (x32)\POS
x64: (x64)\POS

Capture

0, 1

1

4.7.3 and later

Defines whether to store log-files or not. 
Log-files are stored in the IntellectFolder\Modules\PosCapture folder.

x32: (x32)\POS
x64: (x64)\POS

Dos2Win

0, 1

1

4.7.3 and later

Detects encoding:
1 - read XML encoding in DOS codepage;
0 - read  XML as it is

x32: (x32)\POS
x64: (x64)\POS

GlobalTextDelay

-

0

4.7.3 and later

Sets the shift of Text data from video to TextSearch.

x32: (x32)\POS
x64: (x64)\POS

Nohotkey

0, 1

1

4.7.3 and later

Allows disabling hot keys used for POSVIEWER and TITLEVIEWER. If Nohotkey = 1, then when clicking
Ctrl+Shift+E - the frame export folder is opened;
Ctrl+Shift+T - the Tools folder is opened.

x32:(x32)\POS
x64:(x64)\POS
DecodeUtf80, 104.8.3 and later

The key enables the UTF-8 encoding to ensure the correct display of captions in cases when the incoming to the POS terminal packages have the UTF-8 encoding.

x32: (x32)\POS
x64: (x64)\POS

PosLogMaxsize

>0

10

5.1 and later

The key sets maximum size (in MBs) of the POS terminal’s log.

Note. POS terminal logging is enabled using the Capture key – see above.

x32: (x32)\POS
x64: (x64)\POS
SetFlowControlNone0, 115.4 and laterCOM port control. Set to 0 if POS terminal fails to operate while connecting to POS-Intellect.
x32:(x32)\POS
 x64:(x64)\POS
UseLocalTimestamp0, 105.4 and later

The key enables the received local timestamp conversion to UTC when creating a record in the corresponding POS-Intellect database.

0 - received local timestamp will be recorded to the corresponding database without any changes.

1 - received local timestamp will be converted to UTC when creating a record in the corresponding database.

x32:(x32)\POS
 x64:(x64)\POS
UseLastCashierInfo0, 105.4 and later

In case the D-store POS-terminals are used, the key enables saving the info about the last cashier whose data was received by the POS-terminal. Until there is no data, the following default values are used: cashier_name = "Jane B."; cashier_number = "1147911";

0 - the info about the last cashier whose data was received by the POS-terminal, is not saved.

1 - the info about the last cashier whose data was received by the POS-terminal, is saved.

x32:(x32)\POS
 x64:(x64)\POS
NewReceipt.Use0, 105.4 and later

In case the D-store POS-terminals are used, the key enables initiating the receipt creation by any data input. In addition to that, the text line specified in the NewReceipt.Word key (see below) is added to the receipt text.

0 - the receipt creation is initiated by the word specified to trigger the receipt creation.

1 - the receipt creation is initiated by any data input, and the text line specified in the NewReceipt.Word key (see below) is added to the receipt text.

Note. This key works only if the UseLastCashierInfo key (see above) is enabled.

x32:(x32)\POS
 x64:(x64)\POS
NewReceipt.Word
String valueNEW RECEIPT5.4 and laterThe key enables specifying the text line which will be added to the receipt text if the NewReceipt.Use key (see above) is enabled.
x32:(x32)\POS
 x64:(x64)\POS
PrintTime0, 105.4 and later

The key activates displaying in the Monitor the time (UTC) when each caption appeared.

0 - the captions timestamps (UTC) are not displayed in the Monitor.

1 - the captions timestamps (UTC) are displayed in the Monitor.

TABLE OF CONTENTS

ATM-Intellect

Registry section

String parameter

Available values

Default

Product version

Description

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PeakWorkingSetSizeQuota

>=0

100

from 8.0


The maximum memory size in megabytes used by the process videosrv.exe on ATM-Intellect Pro. If the parameter is set to 0, then the check for the used memory is not performed.

Once a day, the ATM-Intellect Pro checks the size of the memory it uses. The check is performed at the time specified by the TimeOfCheckWorkingSetSize key (see below).

After exceeding the specified value, the videosrv.exe module is rebooted.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeOfCheckWorkingSetSize

>=0

3

from 8.0

Time to check memory usage in hours. Default value is 3 (3:00 AM). See also the PeakWorkingSetSizeQuota key description above.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StoreVideoFiles

>0

3

from 5.0

Time period for storage of not completely downloaded files on ATM-Intellect Pro. After the storage period is exceeded, the not completely downloaded files are deleted.


x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)


run_intellect


0.1


1


from 5.0

The key sets the ATM-Intellect Pro actions in case if the Intellect software is shut down.

0 – do not start the Intellect software

1 – start the Intellect software




x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)




socket_connect_tout




>=0




0




from 5.0

The key defines TCP/IP connection mode with ATM-Intellect Workstation.

0 – blocking mode. ATM-Intellect Pro connects to ATM-Intellect Workstation without specifying connection timeout.

>0 – non-blocking mode. ATM-Intellect Pro connects to ATM-Intellect Workstation with a connection timeout set by the socket_connect_tout > 0 parameter in seconds.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

write_buffer_enable

0.1

1

from 7.0

Data buffering while recording on disc when receiving video data on ATM-Intellect Workstation. ATM-Intellect Pro transfers video data to ATM-Intellect Workstation in packages of 800 to 4096 bytes (4096 by default). When buffering is enabled, a 264 Kb block of memory is allocated to the ATM-Intellect Workstation for receiving video data, and data is saved to the disk when this memory block is full, not every time a packet is received from ATM-Intellect Pro.

0 – buffering is enabled.

1 – buffering is disabled.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

stop_data_by_trx

0.1

1

from 5.0

The key determines the actions of ATM-Intellect Pro in case if, during the transfer of video data to ATM-Intellect ARM, a financial transaction has begun on the ATM.

0 – video data transfer is not stopped.

1 – video data transfer is suspended until financial transaction if completed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

IPPort> 07755from 5.0

The key specifies the port on the ATM-Intellect Workstation used for connecting the clients.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

financial_trx_tout

>0

60

from 7.0

Timeout for waiting for the financial transaction to complete in minutes. If after the start of the financial transaction during the time-out, there is no message from the ATM about its end, it will be considered to be completed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeAlarmFromAgent


0, 10from 10.0The key enables registration of the alarm with the time it occurred on the site.

0 – In the Alarm date field in the interface objects, the time of loading the alarm into the database after it is received from the Agent of Control is shown, not the time of occurrence of the alarm on site.

1 - In the Alarm date field in the interface objects, the time of alarm occurrence on site is shown.

Note. The key is set on the ATM-Intellect Workstation.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FileQueryEnable0, 10from 10.0

The key enables automated video clip loading.

0 – automated video clip loading is disabled.

1 – automated video clip loading is enabled.

Note. The key is created at ATM-Intellect Workstation and/or Additional workstation

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FileQueryPath
TextC:\Query\from 10.0

The key sets folder to share data with third party systems which is necessary for automated video clip loading.

Note. The key is created at ATM-Intellect Workstation and/or Additional workstation

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

OldLogPanel0, 10from 11.0

The key changes the Log Panel interface color theme.

0 - dark interface theme.

1 - light interface theme.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StreamViewerExportPathText<Intellect installation directory>\exportfrom 11.0

The key specifies the path to the catalog of frames and video clips which were exported from the Monitoring interface during the live and archive video playback from a certain camera.

See Playing back live video and archive from a specific camera.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

MonitoringReserving0, 10from 11.0

The key removes the restriction on adding the same cameras for tracking in different Surveillance Objects.

0 - the restriction is enabled.

1 - the restriction is removed.

x32: HKLM\SOFTWARE\BitSoft\MonitorSSTV\Loader

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\MonitorSSTV\Loader

UseBulkInsert0, 1
from 10.0

The key accelerates the speed of data loading from files to the MonitorSSTV database by activating the group operator of data loading if the database is installed locally.

0 - do not use the BULK INSERT operator (if the SQL Server is remote)
1 - use the BULK INSERT operator (if the SQL Server is local)

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PrefixForTimeOutText-from 10.0The key specifies the prefix in the identifier of the Surveillance Objects for which the waiting timeout specified in the TimeoutForPrefix key should be specified.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeoutForPrefix>06from 10.0The key sets the waiting timeout in minutes for the ATM-Intellect Workstation to receive the packets with the technical state of ATM-Intellect Pro. After this time the "No connection" error will be displayed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

UsingTimeoutForPrefix0, 10only 10.0The key enables the waiting timeout set in the TimeoutForPrefix key for all Surveillance objects with the identifier prefix specified in the PrefixForTimeOut key.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PostfixForTimeOutText-from 11.0The key specifies the postfix in the identifier of the Surveillance Objects for which the waiting timeout specified in the TimeoutForPostfix key should be specified.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeoutForPostfix>06from 11.0The key sets the waiting timeout in minutes for the ATM-Intellect Workstation to receive the packets with the technical state of ATM-Intellect Pro. After this time the "No connection" error will be displayed.
HKEY_CURRENT_USER\SOFTWARE\BitSoft\MonitorSSTVMAXRECORDSONPAGE1,000 - 2,000,000,00010,000from 11.0Sets the maximum number of events to be displayed in the Event Log window without navigation buttons.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LastLoadThreshold >= 030from 11.0

The key sets the time in minutes, after which, if the data in the MonitorSSTV database is outdated, the corresponding indication on the ATM-Intellect Workstation will appear.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

DisableMonitoring0, 10from 13.0

The key disables the ability to accept alarms and force error closing.

0 - the ability to confirm alarms and force error closing is enabled.

1 - the ability to confirm alarms and force error closing is disabled.

If the key is set to 1, then:

  • the area for comments and buttons for confirming the alarm are not displayed in the Reaction to alarm window; when you set the Confirm checkbox, nothing happens;
  • when you click on the Force error closing button on the toolbar, the window with confirmation of force error closing does not open.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StreamViewerLowestPriority0, 10from 13.0

The key sets low priority of the StreamViewer process when it starts.

0 − The StreamViewer process starts with normal (medium) priority.

1 − The StreamViewer process starts with low priority.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

SleepAfterDisarminteger in ms50from 14.0

The key sets the time interval of recording delay in ms after disarming the camera

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

SleepAfterRecStopinteger in ms50from 14.0

If the continuous recording mode is enabled, the key sets the time interval of recording delay by camera in ms after the camera is stopped.

If the camera is armed, the key sets the time interval of camera arming delay in ms after the camera is stopped

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

KeepVideoDataInBase>00from 14.0

If the parameter isn’t created or equals 0, the video data isn’t stored in the ATM Intellect database (MonitorSSTV).

If the parameter > 0, its value equals the number of days the video data should be stored in the ATM Intellect database. When this period is exceeded, the video data is deleted from the database

Restricting the Operator’s access to the camera's functional menu and its options

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_DISABLE_OPTION0, 10from 11.0

The key hides the camera's menu.

0 - The menu is displayed.

1 - The menu is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_ARM_DISABLE_OPTION0, 10from 11.0

The key hides the Arm menu option.

0 - The Arm menu option is displayed.

1 - The Arm menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_REC_DISABLE_OPTION0, 10from 11.0

The key hides the Start recording menu option.

0 - The Start recording menu option is displayed.

1 - The Start recording menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_CAMS_DISABLE_OPTION0, 10from 11.0

The key hides the Camera menu option.

0 - The Camera menu option is displayed.

1 - The Camera menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_TITLES_DISABLE_OPTION0, 10from 11.0

The key hides the Show titles menu option.

0 - The Show titles menu option is displayed.

1 - The Show titles menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_DISABLE_OPTION0, 10from 11.0

The key hides the Processing menu option.

0 - The Processing menu option is displayed.

1 - The Processing menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_EXPORT_DISABLE_OPTION0, 10from 11.0

The key hides the Export menu option.

0 - The Export menu option is displayed.

1 - The Export menu option is hidden.

Restricting the Operator’s access to the Processing menu within the camera's functional menu

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_DEINTERLACE_DISABLE_OPTION0, 10from 11.0

The key hides the Deinterlacing menu option.

0 - The Deinterlacing menu option is displayed.

1 - The Deinterlacing menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_ZOOM_DISABLE_OPTION0, 10from 11.0

The key hides the Zoom-in menu option.

0 - The Zoom-in menu option is displayed.

1 - The Zoom-in menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_CONTRAST_DISABLE_OPTION0, 10from 11.0

The key hides the Contrast menu option.

0 - The Contrast menu option is displayed.

1 - The Contrast menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_MASK_DISABLE_OPTION0, 10from 11.0

The key hides the Detector mask menu option.

0 - The Detector mask menu option is displayed.

1 - The Detector mask menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_SHARPNESS_DISABLE_OPTION0, 10from 11.0

The key hides the Sharpen menu option.

0 - The Sharpen menu option is displayed.

1 - The Sharpen menu option is hidden.

Restricting the Operator’s access to the CamMonitor component buttons

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_ARCH_DISABLE_OPTION0, 10from 11.0

The key hides the Archive button.

0 - The Archive button is displayed.

1 - The Archive button is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_TIME_DISABLE_OPTION0, 10from 11.0

The key hides the time.

0 - The time is displayed.

1 - The time is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_NAME_DISABLE_OPTION0, 10from 11.0

The key hides the camera name.

0 - The camera name is displayed.

1 - The camera name is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_MENU_DISABLE_OPTION0, 10from 11.0

The key hides the Menu button.

0 - The Menu button is displayed.

1 - The Menu button is hidden.

Restricting the Operator’s access to the CamMonitor control via the keyboard and mouse

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

KEYS_DISABLE_OPTION0, 10from 11.0

The key disables the control over the CamMonitor component using the hotkeys available for Video Monitor (see Video surveillance monitor).

0 - The control over the CamMonitor component using the hotkeys is enabled.

1 - The control over the CamMonitor component using the hotkeys is disabled.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

TELEMETRY_ENABLE_OPTION0, 10from 11.0

The key enables the Telemetry control using the CamMonitor component (see Telemetry control).  

0 - The Telemetry control using the CamMonitor component is disabled

1 - The Telemetry control using the CamMonitor component is enabled.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

ARCH_DELETE_ENABLE_OPTION0, 10from 11.0

The key activates the Delete menu item which is used to remove the recordings from the archive. It is used only in Intellect version 4.11 and higher (see Deleting video recordings from the archive).

0 - The Delete item is hidden.

1 - The Delete item is displayed.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

ARCH_PROTECT_ENABLE_OPTION0, 10from 11.0

The key activates the Protect menu item which is used to protect the archive recordings from rewriting. It is used only in Intellect version 4.11 and higher (see Protection of separate record and disable of protection).

0 - The Protect item is hidden.

1 - The Protect item is displayed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

ExportPathText

DISK:\Export\

, where DISK is the drive on which the operating system is installed

-

Sets the path to the export directory on ATM-Intellect Workstation

 TABLE OF CONTENTS

 

ATM Event Capture

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnTOut

>0

10

from 9.0


Timeout in seconds for waiting for the information about the card insertion to appear in the ATM log after the actual card insertion.

For m_JrnMode=2 mode only (MAK3 TUSSON)

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

Mask>=0--

Specifies the options for masking the card number. By default, the first 6 and last 4 characters of the card number are not masked.

0 – if no mask to be applied to the card number.

1-6 – number of digits in the beginning of the card number which are not masked.

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnMode>=00-

Defines the mode of operating the journal.

0 – card number is read from the card reader

1 – card number is read from the ATM journal through the Protopas software (Wincor)

2 – card number is read from the ATM journal through the MAK3 (TUSSON) software

3 – card number is read from the ATM journal through the TellMe (SCS) software

4 – card number is read from the ATM journal through the APTRA Advance NDC (NCR) software

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnPath >=0--

Specifies the path to the ATM journal.

If JrnMode = 1, then JrnPath = C:\JOURNAL\

If JrnMode = 2, then JrnPath = C:\scs\atm_h\PRJ\

If JrnMode = 3, then JrnPath = C:\scs\atm_h\PRJ\

If JrnMode = 4, then JrnPath = C:\program files\ncr aptra\advance ndc\data\

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

JrnTrack2Substring >=0--

Specifies the substring for searching the card number.

If JrnMode = 1, then JrnTrack2Substring = (TRACK 2 DATA)

If JrnMode = 2, then JrnTrack2Substring = @++

If JrnMode = 3, then JrnTrack2Substring = CARD

If JrnMode = 4, then JrnTrack2Substring = CARD

x32: (x32-ATM Event Capture)

x64: (x64-ATM Event Capture)

LogEnable0, 10-

Enables logging the ATM Event Capture utility operation

0 - event log is disabled

1 - event log is enabled. After you quit and start ATM Event Capture utility again, the EventATM.log file appears in the installation folder.

 TABLE OF CONTENTS


Monitoring

Registry section

String parameter

Available values

Default

Product version

Description

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LPRDBsearchresultUnicodeBase64

0, 1

1

8.0

The key sets how to process message in param0<> for the SEARCH_RESULT event of the LPRDB ("External database") object – as ANSI line or Unicode line additionally encoded in base64.

0 – ANSI

1 – UnicodeBase64


x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PeakWorkingSetSizeQuota

>=0

100

from 8.0


The maximum memory size in megabytes used by the process videosrv.exe on  Agent of Control. If the parameter is set to 0, then the check for the used memory is not performed.

Once a day, the  Agent of Control checks the size of the memory it uses. The check is performed at the time specified by the TimeOfCheckWorkingSetSize key (see below).

After exceeding the specified value, the videosrv.exe module is rebooted.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeOfCheckWorkingSetSize

>=0

3

from 8.0

Time to check memory usage in hours. Default value is 3 (3:00 AM). See also the PeakWorkingSetSizeQuota key description above.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StoreVideoFiles

>0

3

from 5.0

Time period for storage of not completely downloaded files on  Agent of Control. After the storage period is exceeded, the not completely downloaded files are deleted.


x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)


run_intellect


0.1


1

from 5.0

The key sets the  Agent of Control actions in case if the Intellect software is shut down.

0 – do not start the Intellect software

1 – start the Intellect software




x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)




socket_connect_tout




>=0




0

from 5.0

The key defines TCP/IP connection mode with  Server of Control.

0 – blocking mode.  Agent of Control connects to  Server of Control without specifying connection timeout.

>0 – non-blocking mode.  Agent of Control connects to  Server of Control with a connection timeout set by the socket_connect_tout > 0 parameter in seconds.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

write_buffer_enable

0.1

1

from 7.0

Data buffering while recording on disc when receiving video data on  Server of Control.  Agent of Control transfers video data to  Server of Control in packages of 800 to 4096 bytes (4096 by default). When buffering is enabled, a 264 Kb block of memory is allocated to the  Server of Control for receiving video data, and data is saved to the disk when this memory block is full, not every time a packet is received from  Agent of Control.

0 – buffering is enabled.

1 – buffering is disabled.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

stop_data_by_trx

0.1

1

from 5.0

The key determines the actions of  Agent of Control in case if, during the transfer of video data to ATM-Intellect ARM, a financial transaction has begun on the ATM.

0 – video data transfer is not stopped.

1 – video data transfer is suspended until financial transaction if completed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

IPPort> 07755from 5.0

The key specifies the port on the Server of Control/Central Server of Control used for connecting the clients.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

financial_trx_tout

>0

60

from 7.0

Timeout for waiting for the financial transaction to complete in minutes. If after the start of the financial transaction during the time-out, there is no message from the ATM about its end, it will be considered to be completed.

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

ULPRspecialProcessing>=0-from 10.0

The key enables special operation mode of the Monitoring software joint with Auto Intellect.

1 – the special operation mode of the Monitoring software joint with Auto Intellect is enabled.

Any other value – the special operation mode is disabled.

Note. The key is created both on Agent of Control and Server of Control.

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

PlaceOfRecognitionN1,2-from 10.0

This parameter corresponds to the point of recognition. PlaceOfRecognitionN, where N is the ID of the LPR channel object.

1 – entrance.

2 – exit.

Note 1. The key is in use in special operation mode of the Monitoring software joint with Auto Intellect.

Note 2. The key is created at Agent of Control

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

CamOfRecognitionN>0-from 10.0

This parameter corresponds to the ID of a camera added to the recognition module. CamOfRecognitionN, where N is the ID of the LPR channel object. 

The value of this parameter corresponds to the Camera object ID specified in the LPR channel object settings.

Note 1. The key is in use in special operation mode of the Monitoring software joint with Auto Intellect.

Note 2. The key is created at Agent of Control

x32: HKLM\SOFTWARE\BitSoft\VHOST\ULPR

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\VHOST\ULPR

AlarmMsgOne>=0-from 10.0

The key enables the LP found in the database alarm both for Entrance and Exit recognition points.

0 – enables the LP found in the database alarm both for Entrance and Exit recognition points.

Any other value – the LP found in the database alarm is generated for Entrance recognition point only.

Note 1. The key is in use in special operation mode of the Monitoring software joint with Auto Intellect.

Note 2. The key is created at Server of Control

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeAlarmFromAgent0, 10from 10.0

The key enables registration of the alarm with the time it occurred on the site.

0 – In the Alarm date field in the interface objects, the time of loading the alarm into the database after it is received from the Agent of Control is shown, not the time of occurrence of the alarm on site.

1 - In the Alarm date field in the interface objects, the time of alarm occurrence on site is shown.

Note. The key is set on the Server of Control.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FileQueryEnable   


0, 10from 10.0

The key enables automated video clip loading.

0 – automated video clip loading is disabled.

1 – automated video clip loading is enabled.

Note. The key is created at Server of Control and/or Additional workstation

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FileQueryPath


TextC:\Query\from 10.0

The key sets folder to share data with third party systems which is necessary for automated video clip loading.

Note. The key is created at Server of Control and/or Additional workstation

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

OldLogPanel0, 10from 11.0

The key changes the Log Panel interface color theme.

0 - dark interface theme.

1 - light interface theme.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StreamViewerExportPathText<Intellect installation directory>\exportfrom 11.0

The key specifies the path to the catalog of frames and video clips which were exported from the Monitoring interface during the live and archive video playback from a certain camera.

See Playing back live video and archive from a specific camera.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

MonitoringReserving0, 10from 11.0

The key removes the restriction on adding the same cameras for tracking in different Partitions of Control.

0 - the restriction is enabled.

1 - the restriction is removed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

AccessByCardEnable0, 10from 11.0

The key activates the special  mode of Monitoring operation together with ACFA-Intellect, as well as the ability to customize the long alarm description.

0 - Special operation mode is off.

1 - Special operation mode is on.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

CustomisedLongAlarmNameTextObject disarmedfrom 11.0

The key changes the description of the long alarm Object disarmed in the Monitoring and Monitoring reports interface objects.

x32: HKLM\SOFTWARE\BitSoft\MonitorSSTV\Loader

x64: HKLM\SOFTWARE\Wow6432Node\BitSoft\MonitorSSTV\Loader

UseBulkInsert0, 1
from 10.0

The key accelerates the speed of data loading from files to the MonitorSSTV database by activating the group operator of data loading if the database is installed locally.

0 - do not use the BULK INSERT operator (if the SQL Server is remote)
1 - use the BULK INSERT operator (if the SQL Server is local)

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PrefixForTimeOutText-only 10.0The key specifies the prefix in the identifier of the Partitions of Control for which the waiting timeout specified in the TimeoutForPrefix key should be specified.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeoutForPrefix>06only 10.0The key sets the waiting timeout in minutes for the Server of Control to receive the packets with the technical state of Agent of Control. After this time the "No connection" error will be displayed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

UsingTimeoutForPrefix0, 10only 10.0The key enables the waiting timeout set in the TimeoutForPrefix key for all Partitions of Control with the identifier prefix specified in the PrefixForTimeOut key.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PostfixForTimeOutText-from 11.0The key specifies the postfix in the identifier of the Partitions of Control for which the waiting timeout specified in the TimeoutForPostfix key should be specified.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

TimeoutForPostfix>06from 11.0The key sets the waiting timeout in minutes for the Server of Control to receive the packets with the technical state of Agent of Control. After this time the "No connection" error will be displayed.
HKEY_CURRENT_USER\SOFTWARE\BitSoft\MonitorSSTVMAXRECORDSONPAGE1,000 - 2,000,000,00010,000from 11.0Sets the maximum number of events to be displayed in the Event Log window without navigation buttons.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PassiveModeForFTP 0, 11from 11.0

The key sets the operation mode of the Central Server of Control software via FTP.

0 - Active mode.

1- Passive mode.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

PeriodRequestOfStatistic> 05from 11.0

The key sets the statistics polling period in minutes for the Servers of Control.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LogArchPeriod> 0168from 11.0

The key sets the log archiving period in hours of the Communication module (CentralNetServer.log)

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LogMaxSize> 0100from 11.0

The key sets the maximum size of the communication module log file at which it begins to archive ignoring the LogArchPeriod parameter.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LogArchDelPeriod> 03from 11.0

The key sets the log files archive retention period in months (CentralNetServer.log).

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

KeepDB> 06from 11.0

The key sets the data retention period of closed errors and alarms in the Server SSTV DB.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

LastLoadThreshold >= 030from 11.0

The key sets the time in minutes, after which, if the data in the MonitorSSTV database is outdated, the corresponding indication on the Server Of Control/CSC will appear.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

DisableMonitoring0, 10from 13.0

The key disables the ability to accept alarms and force error closing.

0 - the ability to confirm alarms and force error closing is enabled.

1 - the ability to confirm alarms and force error closing is disabled.

If the key is set to 1, then:

  • the area for comments and buttons for confirming the alarm are not displayed in the Reaction to alarm window; when you set the Confirm checkbox, nothing happens;
  • when you click on the Force error closing button on the toolbar, the window with confirmation of force error closing does not open.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

StreamViewerLowestPriority



0, 10from 13.0

The key sets low priority of the StreamViewer process when it starts.

0 − The StreamViewer process starts with normal (medium) priority.

1 − The StreamViewer process starts with low priority.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

SleepAfterDisarminteger in msec50from 14.0

The key sets the time interval of recording delay in msec after disarming the camera

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

SleepAfterRecStopinteger in msec50from 14.0

If the continuous recording mode is enabled, the key sets the time interval of recording delay by camera in msec after it stops.

If the camera is armed, the key sets the time interval of camera arming delay in msec after it stops

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

KeepVideoDataInBase> 00from 14.0

If the parameter isn’t created or equals 0, the video data isn’t stored in the Monitoring database (MonitorSSTV or ServerSSTV).

If the parameter > 0, its value equals the number of days the video data should be stored in the Monitoring database. When this period is exceeded, the video data is deleted from the database

Restricting the Operator’s access to the camera's functional menu and its options

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_DISABLE_OPTION0, 10from 11.0

The key hides the camera's menu.

0 - The menu is displayed.

1 - The menu is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_ARM_DISABLE_OPTION0, 10from 11.0

The key hides the Arm menu option.

0 - The Arm menu option is displayed.

1 - The Arm menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_REC_DISABLE_OPTION0, 10from 11.0

The key hides the Start recording menu option.

0 - The Start recording menu option is displayed.

1 - The Start recording menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_CAMS_DISABLE_OPTION0, 10from 11.0

The key hides the Camera menu option.

0 - The Camera menu option is displayed.

1 - The Camera menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_TITLES_DISABLE_OPTION0, 10from 11.0

The key hides the Show titles menu option.

0 - The Show titles menu option is displayed.

1 - The Show titles menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_DISABLE_OPTION0, 10from 11.0

The key hides the Processing menu option.

0 - The Processing menu option is displayed.

1 - The Processing menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_EXPORT_DISABLE_OPTION0, 10from 11.0

The key hides the Export menu option.

0 - The Export menu option is displayed.

1 - The Export menu option is hidden.

Restricting the Operator’s access to the Processing menu within the camera's functional menu

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_DEINTERLACE_DISABLE_OPTION0, 10from 11.0

The key hides the Deinterlacing menu option.

0 - The Deinterlacing menu option is displayed.

1 - The Deinterlacing menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_ZOOM_DISABLE_OPTION0, 10from 11.0

The key hides the Zoom-in menu option.

0 - The Zoom-in menu option is displayed.

1 - The Zoom-in menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_CONTRAST_DISABLE_OPTION0, 10from 11.0

The key hides the Contrast menu option.

0 - The Contrast menu option is displayed.

1 - The Contrast menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_MASK_DISABLE_OPTION0, 10from 11.0

The key hides the Detector mask menu option.

0 - The Detector mask menu option is displayed.

1 - The Detector mask menu option is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

MENU_PROCESSING_SHARPNESS_DISABLE_OPTION0, 10from 11.0

The key hides the Sharpen menu option.

0 - The Sharpen menu option is displayed.

1 - The Sharpen menu option is hidden.

Restricting the Operator’s access to the CamMonitor component buttons

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_ARCH_DISABLE_OPTION0, 10from 11.0

The key hides the Archive button.

0 - The Archive button is displayed.

1 - The Archive button is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_TIME_DISABLE_OPTION0, 10from 11.0

The key hides the time.

0 - The time is displayed.

1 - The time is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_NAME_DISABLE_OPTION0, 10from 11.0

The key hides the camera name.

0 - The camera name is displayed.

1 - The camera name is hidden.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

BUTTON_MENU_DISABLE_OPTION0, 10from 11.0

The key hides the Menu button.

0 - The Menu button is displayed.

1 - The Menu button is hidden.

Restricting the Operator’s access to the CamMonitor control via the keyboard and mouse

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

KEYS_DISABLE_OPTION0, 10from 11.0

The key disables the control over the CamMonitor component using the hotkeys available for Video Monitor (see Video surveillance monitor).

0 - The control over the CamMonitor component using the hotkeys is enabled.

1 - The control over the CamMonitor component using the hotkeys is disabled.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

TELEMETRY_ENABLE_OPTION0, 10from 11.0

The key enables the Telemetry control using the CamMonitor component (see Telemetry control).  

0 - The Telemetry control using the CamMonitor component is disabled

1 - The Telemetry control using the CamMonitor component is enabled.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

ARCH_DELETE_ENABLE_OPTION0, 10from 11.0

The key activates the Delete menu item which is used to remove the recordings from the archive. It is used only in Intellect version 4.11 and higher (see Deleting video recordings from the archive).

0 - The Delete item is hidden.

1 - The Delete item is displayed.

x32: HKEY_LOCAL_MACHINE\SOFTWARE\BitSoft\VHOST\CamMonitor

x64:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\BitSoft\VHOST\CamMonitor

ARCH_PROTECT_ENABLE_OPTION0, 10from 11.0

The key activates the Protect menu item which is used to protect the archive recordings from rewriting. It is used only in Intellect version 4.11 and higher (see Protection of separate record and disable of protection).

0 - The Protect item is hidden.

1 - The Protect item is displayed.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

RequestFullStatisticOnStartup 
0, 10from 12.0

By default, the Central Server of Control requests a complete package of statistics from all Servers of Control only once, when it first connects to the Servers of Control.

The key activates the request on the Central Server of Control for a complete statistics package from all Servers of Control every time the CentralNetServer.exe communication module is launched.

0 - disabled.

1 - a complete statistics package will be requested from all Servers of Control each time the CentralNetServer.exe communication module is launched.

Attention! Requesting a complete statistics package is a resource-intensive operation. It is only necessary to activate this key if absolutely necessary.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

RequestFullStatistic[N]

Note. [N] is the internal identifier of the Server of Control object in Intellect

0, 10from 12.0

By default, the Central Server of Control requests a complete package of statistics from all Servers of Control only once, when it first connects to the Servers of Control.

The key activates the request for a complete statistics package from a specific Server of Control once. The request will be executed when the CentralNetServer.exe communication module is launched, and the value of this key will automatically change to 0.

0 - disabled.

1 - a complete statistics package from a specific Server of Control will be requested once when the CentralNetServer.exe communication module is launched.

Attention! Requesting a complete statistics package is a resource-intensive operation. It is only necessary to activate this key if absolutely necessary.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

FtpPathText<Intellect installation directory>\Vhost\DATA\FTP\from 13.0

Sets the path to the FTP directory on the Server of Control for working with the Central Server of Control.

x32: (x32-ATM/Monitoring)

x64: (x64-ATM/Monitoring)

ExportPathText

DISK:\Export\

, where DISK is the drive on which the operating system is installed

-Sets the path to the export directory on the Server of Control

 TABLE OF CONTENTS


IP integration (drivers and codecs pack for Intellect)

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

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

ArchiveFps

1-24


4.7.5 and later

Sets the number of frames recorded to the archive (max.resolution). LiveFps and ArchiveFps parameters are not to exceed 24 in total.

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

ArecontVision

0, 1


up to  4.8.0

Enables the protocol for integrating Arecont cameras. The key is not in use.

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

DoubleStream

0, 1


4.7.5 and later

Defines whether asynchronous video display mode is enabled or not.

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

IpIntDrivers3

Brand name: Axis; Acti, etc.


4.7.3 and later

The IpIntDrivers3 string parameter is created and the names of brands that need 3.0 driver are listed.

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

IpIntDriverVersion

2, 3


4.7.3 and later

Defines the version number of loaded drivers:
2 – to load drivers version 2.0;
3 - to load drivers version 3.0;
This parameter has a high priority and cancels IpIntDrivers3 parameter.

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

LiveFps

1-24


4.7.5 and later

Sets the number of frames displayed in the 800x600 format. LiveFps and ArchiveFps parameters are not to exceed 24 in total.

x32: (X32)
x64: (x64)

LoadIpIntDirectly

0, 1

 

4.9.0 and later 

1 - enable IntegratedDevice via video.run. If the setting is enabled and at least one IntegratedDevice is added, then other IP video capture cards are disabled.

0 - IIntegratedDevice operates as a separate run-module.

x32: (X32)\Video\TransportProtocols
x64: (x64)\Video\TransportProtocols
<Driver name><protocol>-DP 3.1.1 and later

The key is used to change a transport protocol used by the IP device.

Example of the key value: "ONVIF"="tcp" means that TCP protocol is used to transfer data via ONVIF.

See details in Changing the transport protocol used by IP-device

Example of the key value: "rtsp"="multicast" allows enabling Multicast mode of the RTSP Server. The object configuration is required in addition to the key.

See details in Configuring RTSP Server module.

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

The name of camera driver (in the driver parameter of the

C:\Program Files\ Common Files\ AxxonSoft\ Ipint.DriverPack \3.0.0\ Ipint.<Driver name>.rep file)
The name of transport protocol (is to be the same as one of the values specified in metadataTransportProtocol property in the corresponding .rep file).-DP 3.31.1613 and laterThe key is used to change a metadata transport protocol. At the time of writing this documentation change of a metadata transport protocol was available for ONVIF driver only (possible values are tcp and udp).
x32: (X32)\Video
x64: (x64)\Video
UnloadUnusedDriverTimeout>=060DP 3.32.1638 and later

The key sets unused driver unload timeout for cameras. For instance, if camera brand is in several drivers, all of them are loaded at camera connection. To unload the unused drivers, set non-zero value to this key.

If the key is not created, then unused drivers are unloaded in 60 seconds.

0 – drivers do not unload (such behavior was in DriverPack versions older than the current one).

The key value that is > 0 sets unused driver unload timeout.

If the key is created but it consists of NaN value, then unused driver unload timeout is set to the default value – 60 seconds.

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

PresetCompatibility0, 1-DP 3.43.1950 and later

The key is used to enable the compatibility between presets in Intellect and previous versions of Drivers Pack, i.e. to decreasing the preset number by 1 when sending it to the driver.

0 – a new operation mechanism with presets the same as in AxxonNext is in use in Intellect. If preset 1 is selected in Intellect interface, then value 1 is sent to the driver.

1, or if the key is not created – the compatibility mode is in use: if preset 1 is selected/created in Intellect interface, then value 0 is sent to the driver.

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

FFTHREADCOUNT>=01DP 3.43.1955 and later

The key sets the number of streams created in FFmpegDecoder.

0 – decoder automatically selects the number of created streams.

>0 – sets the number of streams in use.

By default if there is no key or the value is incorrect, then value 1 is in use.

Auto selection of the number of streams can result in the system load reduction or its increase as the number of streams recreated during decoding increases – this affects the performance.

x32: (x32)\EventSources
x64: (x64)\EventSources

<brand>.<model> (for example, ONVIF.1_channel_device).

If all models of some manufacturer require a specific method of getting events, then there must be a string key named <brand> in the section.

Pull point

Meta data

Disable

Meta dataDP 3.35.1692

By the date the documentation in created, this key is supported for three brands: ONVIF, RVi and IDIS. For models of these brands, the key is created automatically when the Drivers Pack is installed.

The key sets a method of getting data about the analytics and the sensors of the device:

  • Pull point – getting events by http request of the camera
  • Meta data – getting events from the metadata stream
  • Disable – getting events is disabled.
All other values (including an empty string) or if there is no key for the model and brand in the specified section mean that you must use the default method, created as default in the rep file for the given model.
x32: (x32)\Video\UseSsrcChecking
x64: (x64)\Video\UseSsrcChecking
RTSP

enable

disable

enableDP 3.45.2055

The key is intended for setting up synchronization source (SSRC) for RTSP stream:

enable – SSRC check enabled;

disable – SSRC check disabled.

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

FFLOGDELAY0, 10CP 1.580Enables logging of delays of frames decoding and idle time for FFMPEG codec.
x32: (x32)\Video\TsConverters
x64: (x64)\Video\TsConverters

<brand>.<model>, for example, Tattile.ANPR Mobile

If all brand's models require a certain method of the timestamp adjustment, then the section must contain a string key with the name <brand>.

  • InfrequentTs
  • ValidDeviceTs
  • None
Depends on the brandDP 3.34 and later

The keys in this section specify the method of the frame timestamp adjustment.

If the key is not created, the timestamp transferred to the Intellect equals 0, and then the current time is set as its value.

The None value is used if it is necessary to disable the adjustment and transfer the timestamp received from the camera as is.

The ValidDeviceTs value means that the timestamp adjustment method is used before the timestamps transmission to the Intellect if the timestamp received from the camera differs from the current time by the value greater than the one specified in the MaxTimestampDeviation key (see below). After the adjustment, the timestamp calculated on the basis of the previous frame's timestamp and the time elapsed since its reception is transmitted to the Intellect.

InfrequentTs value discards the relative timestamps, transferring 0 to the Intellect instead (i.e., the current time is set as the timestamp value), and it also transfers the absolute timestamps with the ETimestampValidityFlag flag. This adjustment method should be used for the devices with the license plates recognition which transfer the separate frames to the external system, rather than a continuous video stream.

For some manufacturers, when installing the Drivers Pack, the keys with the necessary values are automatically created in the appropriate registry key.

x32: (x32)\Video
x64: (x64)\Video
MaxTimestampDeviation>=0-DP 3.34 and later

The key is used for the ValidDeviceTs key value from the TsConverters branch (see above).

The key sets the maximum permissible deviation of the frame timestamp from the current Server time.

x32: (x32)\Video
x64: (x64)\Video
ErrorSensitivity0, 10DP 3.54 and later

The key enables the interruption of the H.265 video decoding via the ffmpeg decoder in case of the slightest error in the video stream.

0 - if the video stream contains errors, then a buffer with artifacts will be received from the ffmpeg decoder.

1 - if the video stream contains errors, then an empty buffer will be received from the ffmpeg decoder.

x32: (x32)\Video\RTSP
x64: (x64)\Video\RTSP
AudioSeparatedConnection0, 10DP 3.60 and laterEnables RTSP audio over a separate TCP connection.
x32: (x32)\Video
x64: (x64)\Video
servicesVersionauto, ver1, ver2autoDP 3.61 and later

The key sets the version of ONVIF services (only for ONVIF and ONVIF 2.X):

auto – get available versions and choose the latest if possible.

ver1 – use old versions of services.

ver2 – use new versions of services.

x32: (x32)\Video
x64: (x64)\Video
servicesSourcegetServices, getCapabilitiesgetServicesDP 3.61 and later

The key determines the source of the ONVIF services version (only for ONVIF and ONVIF 2.X):

getServices – get a list of services using the new interface.

getCapabilities – get a list of services using the old interface.

x32: (x32)\Video\Virtual
x64: (x64)\Video\Virtual
​playFileOnce0, 10DP 3.62 and later

Disables looping files in a virtual video capture device of a Virtual bench type.

0 - videos in a Virtual bench virtual capture device are played in a loop.

1 - videos in a Virtual bench virtual capture device are played once.

See also Creating and configuring a virtual Video Capture Device.

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

"/cgi-bin/ptz.cgi?", "/stw-cgi/ptzcontrol.cgi?"

-DP 3.58 and later

The key is required for PTZ operation with Hanwha Techwin IP-devices:

"/cgi-bin/ptz.cgi?" – for old models (not X-series)

"/stw-cgi/ptzcontrol.cgi?" –  for new models X-series

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

DecompressorResetOnErrorTimeout0 - 18060

DP 3.69 and later

Compatibility: Intellect 4.10.5.4526 and later

Time in seconds before the decompressor resets after an error. The value for the key should be selected empirically based on the stream parameters of a particular video camera.

Attention! It is recommended to change the value for the key only with the assistance of technical support.

x32: (x32)\Video
x64: (x64)\Video
IQS_ADDITIONTAL_VIDEO_FRAMES_COUNT>=11DP 3.71 and later

The key sets the number of buffered decoded frames for the IntelQuickSync decoder.

TABLE OF CONTENTS


DetectorPack Intellect

Registry section

String parameterAvailable valuesDefaultProduct versionParameter in effect

x32: (х32)\DetectorExt\BARCODE_DETECTOR

x64: (х64)\DetectorExt\BARCODE_DETECTOR

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Barcode Detection: External Detector - BARCODE_DETECTOR.1

x32: (х32)\DetectorExt\BASE_POSE_DETECTOR

x64: (х64)\DetectorExt\BASE_POSE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Pose Detection: External Detector - BASE_POSE_DETECTOR.1

x32: (х32)\DetectorExt\CONVEYOR_BELT_DETECTOR

x64: (х64)\DetectorExt\CONVEYOR_BELT_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Conveyor Belt Detection: External Detector - CONVEYOR_BELT_DETECTOR.1

x32: (х32)\DetectorExt\CROWD_COUNTER

x64: (х64)\DetectorExt\CROWD_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Detection of moving against crowd flow: External Detector - CROWD_COUNTER.1

x32: (х32)\DetectorExt\CROWD_COUNTER_TVN

x64: (х64)\DetectorExt\CROWD_COUNTER_TVN

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Crowd detection (TVN): External Detector - CROWD_COUNTER_TVN.1

x32: (х32)\DetectorExt\EQUIPMENT_DETECTOR

x64: (х64)\DetectorExt\EQUIPMENT_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Equipment detection (PPE): External Detector - EQUIPMENT_DETECTOR.1

x32: (х32)\DetectorExt\FIRE_DETECTOR

x64: (х64)\DetectorExt\FIRE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Fire detection: External Detector - FIRE_DETECTOR.1

x32: (х32)\DetectorExt\FLUID_DETECTOR

x64: (х64)\DetectorExt\FLUID_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Fluid level detection: External Detector - FLUID_DETECTOR.1

x32: (х32)\DetectorExt\GLOW_DETECTOR

x64: (х64)\DetectorExt\GLOW_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Detection of light indication control: External Detector - GLOW_DETECTOR.1

x32: (х32)\DetectorExt\HEAT_ZONE_DETECTOR

x64: (х64)\DetectorExt\HEAT_ZONE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Heat map detection: External Detector - HEAT_ZONE_DETECTOR.1

x32: (x32)\DetectorExt\HeatZoneDetector

x64: (x64)\DetectorExt\HeatZoneDetector

ReportFrequency >0900Intellect 4.9.0 and later

Sets the data collection frequency (sec) for heat zone detection tool.

x32: (x32)\DetectorExt\HeatZoneDetector

x64: (x64)\DetectorExt\HeatZoneDetector

DebugReportFrequency >010Intellect 4.9.0 and later

Sets the data update frequency (sec) from heat zone detection tool in the Debug window in seconds.

x32: (х32)\DetectorExt\NEURO_COUNTER

x64: (х64)\DetectorExt\NEURO_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Neurocounter: External Detector - NEURO_COUNTER.1

x32: (х32)\DetectorExt\NEURO_TRACKER

x64: (х64)\DetectorExt\NEURO_TRACKER

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Neurotracker: External Detector - NEURO_TRACKER.1

x32: (х32)\DetectorExt\OCCUPANCY_COUNTER

x64: (х64)\DetectorExt\OCCUPANCY_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Queue length detection: External Detector - OCCUPANCY_COUNTER.1

x32: (х32)\DetectorExt\PEOPLE_COUNTER

x64: (х64)\DetectorExt\PEOPLE_COUNTER

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the People counter detection: External Detector - PEOPLE_COUNTER.1

x32: (х32)\DetectorExt\SMOKE_DETECTOR

x64: (х64)\DetectorExt\SMOKE_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Smoke detection: External Detector - SMOKE_DETECTOR.1

x32: (х32)\DetectorExt\STOPPED_CAR_DETECTOR

x64: (х64)\DetectorExt\STOPPED_CAR_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Stopped vehicle detection: External Detector - STOPPED_CAR_DETECTOR.1

x32: (х32)\DetectorExt\SWEETHEARTING_DETECTOR

x64: (х64)\DetectorExt\SWEETHEARTING_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Sweethearting at checkout detection: External Detector - SWEETHEARTING_DETECTOR.1

x32: (х32)\DetectorExt\TRAFFIC_LIGHTS

x64: (х64)\DetectorExt\TRAFFIC_LIGHTS

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Traffic lights detection: External Detector - TRAFFIC_LIGHTS.1

x32: (х32)\DetectorExt\TRAIN_DETECTOR

x64: (х64)\DetectorExt\TRAIN_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. Example of a separate process for the Train detection: External Detector - TRAIN_DETECTOR.1

x32: (х32)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR

x64: (х64)\DetectorExt\VIDEO_INTELLECT_INTERNAL_DETECTOR

 

IsProcessObject0, 10DP 2.8 and later

Activates the start of the VideoIntellect detection tool in a separate process:

0—detection tool is started in one common External Detector process, all messages and reactions from this detection tool go to the common process

1detection tool is started in a separate External Detector - Detector type.Detector Id process, all messages and reactions from this detection tool go to the separate process. If there are sub-tools, their messages go to the parent process. 

Examples of separate processes for the VideoIntellect detection tools:

VideoIntellect embedded detector: External Detector - VIDEO_INTELLECT_INTERNAL_DETECTOR.1
VideoIntellect detection of movement in prohibited area: External Detector - VI_FORBIDDEN_DETECTOR.1
VideoIntellect detection of prohibited direction: External Detector - VI_DIRECTION_DETECTOR.1
VideoIntellect detection of crowd: External Detector - VI_CROWD_DETECTOR.1
VideoIntellect abandoned objects detection: External Detector - VI_ABANDONED_DETECTOR.1
VideoIntellect detection of camera state: External Detector - VI_FAULTER_DETECTOR.1
VideoIntellect abandoned objects street detection: External Detector - VI_ABANDONED_STREET_DETECTOR.1

x32: (X32)\Video\
x64: (x64)\Video\
report_frequency>=03000DP 2.6 and laterSets the time period in milliseconds, during which the repeated triggering of the Sweethearting detection module is ignored
x32: (X32)\
x64: (x64)\
ShowVideoIntellectObjects ><=0-DP 2.8 and later

Hides the VideoIntellect detector objects from the Intellect objects tree

0—the VideoIntellect detector objects are hidden

><0—the VideoIntellect detector objects are displayed

x32: (X32)\Video
x64: (x64)\Video
LongInZoneTimeout2>=0-DP 2.8 and later

The key sets the time in seconds which defines the time the object stays in the zone, after which the NeuroTracker VMDA detection tools with the Staying in the area for more than 10 sec detector type, created under the Neurotracker object, are triggered. If this key is not specified, then it is considered equal to the LongInZoneTimeout key value (see Intellect Enterprise base version)

TABLE OF CONTENTS

 

Intellect Web Report System

Registry section

String parameter

Available values

Default

Product version

Parameter in effect

x32: (x32)
x64: (x64)


LogingPersonChangesRequired

0, 1

0

3.4 and later


Enabling of this parameter is necessary for the correct operation of the Issued pass cards report

x32: (x32)
x64: (x64)
RestPortport number224413.5 and later, Intellect 4.11.3 and later

Sets the port that is used for the data exchange via HTTP requests with Intellect Web Report System

If the key value is 0, data exchange via HTTP won't work

TABLE OF CONTENTS

  • No labels