----- FIXED!! ------Under Settings check the server URL addresses. You appear to have both 127.0.0.1:81 and 127.0.0.1:8282. I'm guessing 127.0.0.1:81 is present when is should not be there unless you are running more than one server.
Thank you @Nick3399 , before to upgrade we used to follow this guide, but now I have not any cameras folder,(v 2.0.760.7721) Do which steps to upgrade and keep all setting we must follow?
Spoiler: How to update
This will keep all the camera profiles and the software settings:
- Close the old AI Tool.
- Delete everything in the software main folder (where the old aitool.exe is located), except the /cameras subfolder.
- Open the zip containing the new version.
- Extract everything except the /cameras subfolder into the software main folder.
The Camera folder has been discontinued for some time now. Config data is now held in JSON files and the registry.
There is the DeepStack integration that is part of BI in a recent update, and this thread you are in is a 3rd party add-on that someone has created that runs separate of BI.I currently use Dahua's IVS, but would prefer to be able to configure object recognition in BI instead. I am curious if you guys run the built-in Deepstack inference on the substream, or the main stream?
I noticed that when I run the analysis off the main stream (I don't use sub streams at the moment), the CPU spikes up to a 100% when the python process is running.
I have seen posts mentioning almost no CPU usage from Deepstack, so maybe processing full 4MP is the reason why I'm seeing high usage? Or perhaps you guys use hardware-accelerated inference with a GPU?
As an aside, I also noticed that (perhaps due to a delay in processing), the Deepstack labeling does not work as well as Dahuas, which is almost instant. In many cases by the time a label is applied, the object has already moved out of frame. I also get issues with cars that were already parked triggering alerts (might be able to tweak that).