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

The 5.9.9.80 appears to have fixed the UI3 sort order :) Also fixed the android app alert issue too. So currently everything seems good :)
 
Last edited:
  • Like
Reactions: Vettester and jrbeddow
5.9.9.80

Help PDF: not updated

Changelog...

[5.9.9.80] – 2025-09-18

Added
• N/A

Fixed
• Camera order bug
• Crash bug for alerts list display with long memos

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.
 
  • Like
Reactions: Oneup and looney2ns
hubbend said:
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:
Click to expand...
5.9.9.80 is working fine for me now.
 
  • Like
Reactions: Tinman
Haha oh boy, came here when I noticed I could not export clips. Looks like it reset the clipboard folder location

Also, my drives are not being filled. Updated to .80, hopefully that resolves!

1758254569295.png
 
jaydeel said:
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.
Click to expand...

This statement in the changelog "If you make DB backups, only the records.dat is required."

Can somebody please check? Reason I ask is on my test system I see data being written to the file extra.dat but my records.dat was last update some 4 days ago ?
 
IReallyLikePizza2 said:
Haha oh boy, came here when I noticed I could not export clips. Looks like it reset the clipboard folder location

Also, my drives are not being filled. Updated to .80, hopefully that resolves!

View attachment 228347
Click to expand...
When I first updated to new DB I gained back some free space on all 3 of my clip drives. Don't ask me how, but I did not lose any clips or alerts. As far as your clipboard location, not sure on that.
 
Has anybody noticed that with the most recent updates the mobile phone app, iOS for me no longer indicates that a clip has been recorded

Used to show a red dot before but now most have nothing and some have a dark grey dot?
 

Attachments

  • IMG_2428 Large.jpeg
    IMG_2428 Large.jpeg
    145.9 KB · Views: 0
Tinman said:
BI still keeps .dat files for each recording though, I think these are also required for the database to function.
Click to expand...
If you are taking about the recently added DAT files in the New folder (5.9.9.44), here's Ken's reply to a few of my questions (9/13/25)...

1. Are DAT files created only when the associated BVR file has Alerts?

yes created when there is an alert. This is used to navigate alerts without the DB in the viewer. I will be adding a header record to these .dat for the BVR as a whole. ​

2. Are DAT files created for any other reason? For example, if I add a memo to the BVR clip and it has no Alerts? In my limited testing, I do not see the creation of DAT files on old (not actively recording) clips to which I've added a memo.

Not yet ... see answer to #1. ​

3. It appears that the automated deletion of old DAT files is managed with their associated BVR files, yet the logfile shows no 'DeleteFile OK:' entries for DAT files.

Correct. Should these be logged as well? They are just tagalongs for the BVRs.​

~~~~~
Re #3... I replied that I thought both creation and deletions should be logged, as this eliminates any ambiguity as to the management of these files.
 
Last edited:
  • Like
Reactions: Tinman
Below is Ken's reply to inquiry about the new database file 'records.dat'...

It feels a bit cryptic but does explain the timestamps.

I just watched the file update in Windows File Explorer when I restarted the Blue Iris service.

Me...

The changelog for 5.9.9.75 says "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."​
​
I'm monitoring the timestamp and file size of file 'records.dat' and it is not updating. It appears that it has the same timestamp as the last-executed update*.exe file.​
​
If only 'extra.dat' contains alert and clip details, and these can be regenerated, how will backing up 'records.dat' help you recover the database?​

Ken...

"There will be pages cached in memory. The file will not be up to date until the software is stopped and the file is closed."​
​
​
 
jaydeel said:
Below is Ken's reply to inquiry about the new database file 'records.dat'...

It feels a bit cryptic but does explain the timestamps.

I just watched the file update in Windows File Explorer when I restarted the Blue Iris service.

Me...

The changelog for 5.9.9.75 says "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."​
​
I'm monitoring the timestamp and file size of file 'records.dat' and it is not updating. It appears that it has the same timestamp as the last-executed update*.exe file.​
​
If only 'extra.dat' contains alert and clip details, and these can be regenerated, how will backing up 'records.dat' help you recover the database?​

Ken...

"There will be pages cached in memory. The file will not be up to date until the software is stopped and the file is closed."​
​
​
Click to expand...
That makes sense except when I restarted my test system the file didn’t get updated, the logs did have an entry along of the lines of unexpected shutdown so maybe the BI service on restart didn’t terminate properly?
 
jaydeel said:
Ken...

"There will be pages cached in memory. The file will not be up to date until the software is stopped and the file is closed."​
​
​
Click to expand...
And when the system crashes? All is lost?
 
You must log in or register to reply here.
Top Bottom