Dynamic Masking

Change log:

• Dynamic Masking - thanks to @classObject! Any detection that are repeated in the same area will be ignored
• Camera option for 'Trigger Cancels' - Basically, rather than the URL triggering an event in BI, it will only be called when the detection is CANCELED. Note that you MUST change &flagalert=1 to &flagalert=0. As I understand this is how Sentry AI works - it just cancels a detection sent by BI.
• Images are put into a true queue to be processed, and the log/Overview tab shows you current/max/average queue levels so you know if BI is overloading AITool. (MaxImageQueueSize defaults to 100 and can be changed in the settings .JSON file if needed)
• Sort cameras on load
• Telegram chat id was not being saved correctly
• Fixed crashes related to stats tab, various null references, errors writing to history.csv, etc

Fixed running as service

This minor update will now allow a second instance, but it will not enable the folder watchers. It will also not update the history window unless you close/restart the app. The log tab will not display output from another running instances (such as a service). The log file has to be directly opened in order to see updates from the service.

If you need the UI to be fully functional with history updates, file watching, etc then simply stop the other running service/instance of aitool.exe first.

Many Enhancements

Here is a fork of the project with a number of useful changes. This is based off GentlePumpkin's awesome '1.67 preview 7' release - I hope some of the good bits here will be merged into his main app.

It will read in current 1.65/1.67 settings & cameras, but you should certainly keep a backup copy of the previous version and settings you were using if you ever need to revert back!

• Enhanced error catching, logging and log window. Log files renamed every day and deleted after 60 days. Log tab with colored logging and enhanced timing. Show average/min/max timing for detection and how long an image had to wait in the queue to be processed. Logging to log or history csv will wait for previous operations to complete to avoid errors. Log file writing done on another thread so the app doesnt have to wait for each log entry to be written.

• Directly control DeepStack (Windows version only). Automatically start/stop DS with AI TOOL. View debug output from deepstack processes within AITOOL logs. Run process at "high" priority for slight speed improvement.

• Start with Windows option

• Blue Iris class - Dropdowns for new camera and input paths will display configured BI paths if installed on the same machine. Camera paths will be auto selected if named the same as the camera. Ie "AICAM1" is in input path \cams\AICAM1

• Support for multiple watch paths - One for each camera

• Cameras and Settings now saved to .JSON file rather than subfolder/files

• SAFE reading/writing of settings file and camera settings. - backup is created, corruption detected and automatically revert to backup copy (my original settings and camera files kept ending up all null's for some reason?)

• Minor enhancements to history tab. Colorize relevant alerts, gray out files that no longer exist, fade rectangle shown around objects. Prevent multiple operations from trying to write to history CSV at same time.