FINE-TUNE YOUR INSTALLATION ACCORDING TO YOUR NEEDS
Config - Config file
You can finetune your installation in the Config file. The config file is the file containing all your settings. When you do a change in the page Config > Main options, those are actually useful shortcuts, and your choices are written in the config file.
You can find the config file either in the control center (in Config > Config file) or in the folder containing VidiReports.exe, that contains the folder data. The config file is named vidireports.local.cfg . You can open it and edit it with any text editor.
In the config file, any line that starts with # is commented: it means that everything that comes after the # on this line will not be interpreted by the computer.
We are going to address here only the mostly used parameters of the config file. If you want to know all of them, you will find a very well documented article on our knowledge base.
You can let your license auto-renew: if they come to an end and you decide to extend them, we will change the expiration date in VidiCenter. If the auto license update is enabled (value 1)
BoxID and BoxMAC
The BoxID and the BoxMAC are given to your instance of VidiReports upon first start. It is a unique ID that allows to know that this box is sending data.
Do not copy the boxID or the BoxMAC to other instances. They are unique ID. Two instances using the same ID will create a conflict and data will be lost.
Part to never edit
Do not touch this part.
This is what allows to grab your BoxID again even if you accidentally delete it.
The webserver is the control center.
You can choose to clock the control center (so it wouldn’t show when people type localhost:81), and you can also choose to disaply it on another port. Be careful though ! You cannot just choose any port: many of them already serve another purpose.
The snapshot lets you see what the camera sends as an image to vidireports, to make sure that it is installed correctly. After a few minutes, we disable it. If you want to never show the snapshot (not even upon start, write webserver_enable_snap = true.
You can specify which webcam you want to use in the config file, and if it is not set to “any available” then, the UID of that camera will be written in the config file. Upon each start of VidiReports, this camera will be chosen. If it is not found, it will generate a “Camera not found” alert.
nthreads is the number of threads used to analyze the image sent by the camera to VidiCenter. To improve the performance of your computer, you could try to use nthreads = 2 if you have a dual core or better (it uses multiple CPU cores to analyze images). Try and see if it allows you to get better FPS.
You should have a nthreads number that is less than the number of physical cores of your CPU. If you have an other applications running in parallel, we suggest to leave an extra core unoccupied.
Increasing the number of threads increases the global performance of VidiReports but deteriorates the performance of the tracking algorithm, so we recommend to be conservative with this number : use only what is needed.
Image as a mirror
When you show a demo, it is always better to have the camera set in mirror mode, so that when people move to one side, their image on screen moves to the same side.
For that, just uncomment the line image_mirror = true by deleting the # sign in front of it.