5.9.9 - January 17, 2025 - More Pre-6.0 feature releases

dan martin 29 said:
"Super helpful post! The step-by-step visuals really make it easy to follow. That tmpfiles.org integration under the hood is clever—can see this being really useful for lightweight push workflows."
Click to expand...
I just learned another new tidbit about this feature today...

When it is used, Blue Iris creates a logfile entry like
0 4/7/2025 4:10:57.322 PM FE tmpfiles.org: OK https://tmpfiles.org/dl/24068939/image.jpg
 
  • Like
Reactions: looney2ns
5.9.9.39

[5.9.9.39] Improved memory management for the clips view and database, targeting some instability experienced by some with larger databases

1746117820866.png

Also, not mentioned, is the addition of a 'special' macro %066 = Hourly precipitation, always in mm/hour units (where available)

1745250693926.png

For more details, see this post.

PS - For those who've not seen it before, here's a post describing how I often discover these kinds of minor changes in the Help PDF that are not mentioned in the Updates section of the Introduction chapter.
 
Last edited:
  • Like
Reactions: looney2ns and mvoss
[5.9.9.39] and [5.9.9.40]

Encountered issues with DB corruption, missing clips, and UI responsiveness when performing actions that interact with the clip list. Reported this to BI Support and rolled back to 5.9.9.38 (Compact/Reindex required to reinstate missing clips)
 
slabbel said:
[5.9.9.39] and [5.9.9.40]

Encountered issues with DB corruption, missing clips, and UI responsiveness when performing actions that interact with the clip list. Reported this to BI Support and rolled back to 5.9.9.38 (Compact/Reindex required to reinstate missing clips)
Click to expand...
Thanks for posting. I assumed there was an issue given the quick release of 5.9.9.40.

Luckily, I managed to avoid any issues after updating to 5.9.9.39 this morning.

As I've previously posted , I've made performing a DB Compact/Reindex BEFORE updating a part of my pre-update routine. I've been doing this since the very challenging updates around v5.9.4.8. My luck so far may still be a coincidence.
 
Last edited:
  • Like
Reactions: looney2ns and slabbel
jaydeel said:
Thanks for posting. I assumed there was an issue given the quick release of 5.9.9.40.

Luckily, I managed to avoid any issues after updating to 5.9.9.39 this morning.

As I've previously posted , I've made performing a DB Compact/Reindex BEFORE updating a part of my pre-update routine. I've been doing this since the very challenging updates around v5.9.4.8. My luck so far may still be a coincidence.
Click to expand...

...now up to .41
 
5.9.9.44

[5.9.9.44] Database metadata is now stored alongside BVR files in separate .DAT files. If the database is ever lost or alerts are deleted, they may be restored from these files. The viewer window also uses these files to navigate alerts independently of the database by using new next/previous alert buttons. Forward/backward navigation buttons are now positioned near one another for easier use.

1746112283243.png

Comments...

1) The next screenshot is the Help PDF's description of the new next/previous buttons.

Usage Notes:
  • Both button sets are active when playing back a clip.
  • Only the first button set is active when playing back an alert.

1746114864799.png

2) The screenshot below shows the location of the new 'alert backup' DAT files (New folder).

Usage Notes:
  • It's not obvious yet how to use these DAT files for recovery. I'm still digging through the Help PDF and menus. And I've emailed Ken for guidance (his reply).
  • These DAT files appear for the first time only after new alerts are triggered.

1746112999334.png
 
Last edited:
  • Like
Reactions: JNDATHP and jrbeddow
Here's Ken's reply regarding how the new 'alert backup' DAT files (New folder) will be used.

RIght now they will be used by a DB regenerate, but only if the clip has no alerts currently in the DB or alerts folder.​
 
You must log in or register to reply here.
Top Bottom