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

Is that the only error you are getting? You must keep your alerts in a location not stock?? I do not move clips, so I do not see this issue. Send a note to BI support.
 
5.9.9.77

Changelog: One new item added to the changelog (bolded).
Help PDF: remains unchanged; has not been updated since 5.9.9.68.

Changelog:

[5.9.9.77] – 2025-09-15

Added
• N/A

Fixed
• Non-system admin users will no longer see camera IP addresses in the JSON "camlist" results
Crash bug resulting from ONVIF dates not properly set in the camera when using GetEvents. When using ONVIF events, camera dates should be set properly or automatically maintained with a time server.

Changed
• Version 6 database. The DB code has been redesigned and then rebuilt from the ground up. The DB now consists of only 2 files, records.dat (the essential elements) and extra.dat (data that can be regenerated including preview images). If you make DB backups, only the records.dat is required.
• Given the sheer enormity of this change, data will be migrated to the new files when you install this update, but the old files (clips.dat and other view.dat files) will not be deleted automatically until stability is assured, allowing you to safely return to a previous release if required. If you do return to an earlier version, you can run a repair to adopt any new files into the old format and then delete the records and extra files so that they will once again be created when you return to 5.9.9.75 or newer.

Known issues
• Remote management has not been extensively tested against the new database code. The timeline display will be missing until a future release.
 
  • Like
Reactions: looney2ns
5.9.9.77

Changelog: One new item added to the changelog (bolded).
Help PDF: remains unchanged; has not been updated since 5.9.9.68.

Changelog:

[5.9.9.77] – 2025-09-15

Added
• N/A

Fixed
• Non-system admin users will no longer see camera IP addresses in the JSON "camlist" results
Crash bug resulting from ONVIF dates not properly set in the camera when using GetEvents. When using ONVIF events, camera dates should be set properly or automatically maintained with a time server.

Changed
• Version 6 database. The DB code has been redesigned and then rebuilt from the ground up. The DB now consists of only 2 files, records.dat (the essential elements) and extra.dat (data that can be regenerated including preview images). If you make DB backups, only the records.dat is required.
• Given the sheer enormity of this change, data will be migrated to the new files when you install this update, but the old files (clips.dat and other view.dat files) will not be deleted automatically until stability is assured, allowing you to safely return to a previous release if required. If you do return to an earlier version, you can run a repair to adopt any new files into the old format and then delete the records and extra files so that they will once again be created when you return to 5.9.9.75 or newer.

Known issues
• Remote management has not been extensively tested against the new database code. The timeline display will be missing until a future release.
Where are you getting these release notes from?
 
BTW, I asked Ken this week if he would consider adding an argument to the install file to enable users to preview the changelog and help PDFs before deciding to update.

His reply...

Not a bad idea! I use the software Advanced Installer for the main installer. And something very ancient for the updates, basically a self extracting zip. Maybe time to roll my own one of those ...
 
Found that the android app 3.0.46 does not show alerts correctly. New by camera, will freeze app. Or select a camera, then click the calendar icon, then click the red lightning alert icon. It will show the correct camera name and time...but the alert picture is wrong. I have proven this with 2 different phones. Also the IOS app seems to work fine. I have emailed support on this issue.
running current 5.9.9.78

Screenshot_20250916-151113.pngScreenshot_20250916-151149.png

Notice the second pic shows the alert image is the same picture.
 
Last edited:
Good simple util called Recuva that can be used to get some of the clip files back that you may have lost over the last day.

Make to recover the files to another drive and not onto the same drive, then copy over the files and run a reindex.
 
5.9.9.78

Changelog: New items, including V6 DB-related bug fixes
Help PDF: updated (details below)

Changelog...

[5.9.9.78] – 2025-09-16

Added
• N/A

Fixed
• Clip paths returned by many web server operations were not properly formatted.
• DB instability when the console adds new records while surpassing the current number of allocated records (viewer features)

Changed
• N/A

Known issues
• Remote management has not been extensively tested against the new database code. The timeline display will be missing until a future release.


HELP PDF changes...

This is a summary of the changes I've found (see attached, best viewed in Acrobat's two-page view)...
  • Multiple instances of the change of the Blue Iris forum address from https://blueirissoftware.com/forum/ to https://blueirissoftware.com/bbs/
  • Updated description of the Motion Sensor 'Persistence' setting (p102); reproduced below
  • Updated description of the 'Run a Program or Write to a File' action dialog (p184); finally updates the dialog screenshot, and describes a setting that was added way back in August 2023 ('Wait for process to complete')

Persistence defines the time in milliseconds an object might exist without moving before beginning to be considered as part of the background. A longer persistence helps an object to reach its minimum duration for existence. For example, a person walks into a room and then remains extremely still. The motion sensor will notice this, but after a while, it will "give" up and see the person to be no longer moving, or in other words, as part of the background. Persistence defines the amount of time that must pass before this happens. Therefore a longer persistence makes the detection more sensitive because the object will exist for a longer period of time, even when not moving.
 

Attachments

Last edited:
  • Like
Reactions: anijet and Tinman
5.9.9.78

Changelog: New items, including V6 DB-related bug fixes
Help PDF: updated (details below)

Changelog...

[5.9.9.78] – 2025-09-16
I downloaded this release this morning and everything seemed to work. But I came back to my session and Blue Iris had crashed. I restarted it and it will briefly show the main window and then exit. I restarted my computer and same behavior.

Application error log entry:
Code:
Faulting application name: BlueIris.exe, version: 5.9.9.78, time stamp: 0x68c99d16
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0x750
Faulting application start time: 0x01dc27eb12e9cec7
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\windows\System32\ucrtbase.dll
Report Id: 86490f34-9fc2-47bc-9ba1-f7f2a9792f3c
Faulting package full name:
Faulting package-relative application ID:
 
Last edited:
I downloaded this release this morning and everything seemed to work. But I came back to my session and Blue Iris had crashed. I restarted it and it will briefly show the main window and then exit. I restarted my computer and same behavior.

Application error log entry:
Code:
Faulting application name: BlueIris.exe, version: 5.9.9.78, time stamp: 0x68c99d16
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0x750
Faulting application start time: 0x01dc27eb12e9cec7
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\windows\System32\ucrtbase.dll
Report Id: 86490f34-9fc2-47bc-9ba1-f7f2a9792f3c
Faulting package full name:
Faulting package-relative application ID:
I have three systems running 5.9.9.78 and no apparent issues, none are crashing and no errors in the log files!
 
  • Like
Reactions: Tinman
I downloaded this release this morning and everything seemed to work. But I came back to my session and Blue Iris had crashed. I restarted it and it will briefly show the main window and then exit. I restarted my computer and same behavior.

Application error log entry:
Code:
Faulting application name: BlueIris.exe, version: 5.9.9.78, time stamp: 0x68c99d16
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0x750
Faulting application start time: 0x01dc27eb12e9cec7
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\windows\System32\ucrtbase.dll
Report Id: 86490f34-9fc2-47bc-9ba1-f7f2a9792f3c
Faulting package full name:
Faulting package-relative application ID:
Try updating your Microsoft Visual C++ to the latest version.
 
Latest update has rearranged all my cameras when viewing remotely in browser (Firefox). 1st Camera is now bottom right and last is top left.
 
Last edited: