Blue Iris full changelog

Changed:
Continued tweaking of the algorithm for periodic AI scanning and static object determination
Added:
A check for security software and possible LSP (layered service provider) interference, which can cause socket and camera problems. These are now posted to the Status/Log upon startup to assist with verification of the required Security Software Exemptions.

Fixed:
An issue with the new RTSP server code with some players (Scrypted)
Changed:
The algorithm for periodic AI scanning and static object determination; it now more intelligently tracks objects and their states of movement
Simplified the periodic AI scanning dialog by removing unnecessary options
Added:
A camera window right-click option to display the periodic AI scanning objects live; object borders are green for new, blue for moving, yellow for static, red for missing, and orange for triggered (if rules are configured).
New periodic AI scan rules to specifically look for moving or static objects, not just existing/non-existing objects

Fixed:
Additional fortifying of decoder and network stability vulnerabilities in low-resource situations or hardware driver deadlock
Added:
H.265 for the RTSP server, including direct-to-wire capability
“Nothing found” messages missing from AI inspector:
Continued work to bring stability when camera streaming or decoding fail under rare circumstances. The previous “FORCE quitting” of threads was highly problematic for stability and alternative measures are now used. Network sockets are now handled in a more robust fashion to allow for better recovery in “hung” situations.

Fixed:
Additional fortifying of decoder and network stability vulnerabilities in low-resource situations or hardware driver deadlock
Added:
H.265 for the RTSP server, including direct-to-wire capability
“Nothing found” messages missing from AI inspector:
Continued work to bring stability when camera streaming or decoding fail under rare circumstances. The previous “FORCE quitting” of threads was highly problematic for stability and alternative measures are now used. Network sockets are now handled in a more robust fashion to allow for better recovery in “hung” situations.

Fixed:
Addressed font issues once again
When using the “clipstats” JSON command for an alert, it would return the same record locator as was passed, breaking the ALERT_DB macro if sent to UI3.
When using Plate Recognizer for ALPR, the built-in AI OCR is no longer used. Previously, existing plate characters would prevent a call to PR.
Objects were rejected as static even when the option to do so was not enabled for alert confirmation. That option will soon be combined with the “require motion” option to simplify things.
Deletion of clips from UI3 may have inoperable if the clip was recently previewed
Changed:
Now using ipv4.icanhazip.com to fetch your IP4 using the Refresh button on Settings/Webserver. The previous connection to the Blue Iris server would return an IPv6 address if you connected that way, and not all routers support that for remote access.
Added:
If errors are “caught” when using the built-in AI, they are now logged. As a result of and error, the analyzer instance may be reinitialized as well, adding some delay. Some users are finding the need to lower the number of simultaneous analyses from the previous maximum value of 32 down to something more reasonable, perhaps 8 or 4, or even 2. Each instance can use significant RAM and graphics memory, which not all systems can accommodate

Fixed:
Addressed font issues once again
When using the “clipstats” JSON command for an alert, it would return the same record locator as was passed, breaking the ALERT_DB macro if sent to UI3.
When using Plate Recognizer for ALPR, the built-in AI OCR is no longer used. Previously, existing plate characters would prevent a call to PR.
Objects were rejected as static even when the option to do so was not enabled for alert confirmation. That option will soon be combined with the “require motion” option to simplify things.
Deletion of clips from UI3 may have inoperable if the clip was recently previewed
Changed:
Now using ipv4.icanhazip.com to fetch your IP4 using the Refresh button on Settings/Webserver. The previous connection to the Blue Iris server would return an IPv6 address if you connected that way, and not all routers support that for remote access.
Added:
If errors are “caught” when using the built-in AI, they are now logged. As a result of and error, the analyzer instance may be reinitialized as well, adding some delay. Some users are finding the need to lower the number of simultaneous analyses from the previous maximum value of 32 down to something more reasonable, perhaps 8 or 4, or even 2. Each instance can use significant RAM and graphics memory, which not all systems can accommodate

Fixed:
Addressed font issues once again
When using the “clipstats” JSON command for an alert, it would return the same record locator as was passed, breaking the ALERT_DB macro if sent to UI3.
When using Plate Recognizer for ALPR, the built-in AI OCR is no longer used. Previously, existing plate characters would prevent a call to PR.
Objects were rejected as static even when the option to do so was not enabled for alert confirmation. That option will soon be combined with the “require motion” option to simplify things.
Deletion of clips from UI3 may have inoperable if the clip was recently previewed
Changed:
Now using ipv4.icanhazip.com to fetch your IP4 using the Refresh button on Settings/Webserver. The previous connection to the Blue Iris server would return an IPv6 address if you connected that way, and not all routers support that for remote access.
Added:
If errors are “caught” when using the built-in AI, they are now logged. As a result of and error, the analyzer instance may be reinitialized as well, adding some delay. Some users are finding the need to lower the number of simultaneous analyses from the previous maximum value of 32 down to something more reasonable, perhaps 8 or 4, or even 2. Each instance can use significant RAM and graphics memory, which not all systems can accommodate

Fixed:
Joystick enumeration and acquisition was non-functional
An issue where when hardware video decoding became non-functional (perhaps due to system resources or use by other software such as games, 3D design), cameras may enter a state where they are endlessly in a triggered state and the decoder begins to consume memory. This should now be recognized as a “no signal” state, the trigger should end properly and the stream restarted.
A bug where the clip right-click menu to Move items between folders was operating on the wrong items.
Changed:
Continued improvement to the viewer Find/Find-next function
Record locators passed to UI3 are now in a format which survives DB compact and repair operations.

Fixed:
Issues with Find in Clips in the Viewer with regard to AI
Changed:
Improved Find in Clips to be more useful. You may now choose to simply search for
objects regardless of motion settings, or use them together.
Added:
A new “Find Next” command to search forward without reopening the Find in Clips
dialog. Control-click the search icon, or add a keyboard shortcut (F3 for example)

Fixed:
Issues with Find in Clips in the Viewer with regard to AI
Changed:
Improved Find in Clips to be more useful. You may now choose to simply search for
objects regardless of motion settings, or use them together.
Added:
A new “Find Next” command to search forward without reopening the Find in Clips
dialog. Control-click the search icon, or add a keyboard shortcut (F3 for example)