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

[jaydeel]

Thanks for the heads up. Do you know what version this went into? This is causing a number of bugs in UI3 of course, mainly because I was not normalizing character case (to upper or lower case) when using camera or group IDs as part of a settings key. I have to start doing that now.

Issues discovered so far:

• Group Settings for the "All cameras" group were lost (or, shall we say, misplaced?) because they were keyed with the name "Index", but there is no longer a group with the key of "Index". The next UI3 release will restore whatever settings were orphaned by this change, potentially overwriting folks's new settings for the All cameras group. Yippee.
• Breaks something related to All cameras cycle stream .. not sure exactly what but it wasn't being detected properly anymore.

It seems like nobody cares about backwards compatibility anymore.

I believe it was implemented in 5.9.9.81

 

[NonTech]

5.9.9.75

The changelog is reproduced below. The highlights are mine.

Notes:

1. Remote Management users should heed the final 'Known Issues' heads-up BEFORE UPDATING.
2. As others have reported, I've also successfully updated without incident (so far).
3. The two new (and now only) database files (notably still *.dat files) are highlighted in this screenshot:

4. 5.9.9.75
   
   The changelog is reproduced below. The highlights are mine.
   
   Notes:
   

   1. Remote Management users should heed the final 'Known Issues' heads-up BEFORE UPDATING.
   2. As others have reported, I've also successfully updated without incident (so far).
   3. The two new (and now only) database files (notably still *.dat files) are highlighted in this screenshot:
      View attachment 228074

   
   CHANGELOG:
   
   [5.9.9.75] – 2025-09-14
   
   Added
   • N/A
   
   Fixed
   • Non-system admin users will no longer see camera IP addresses in the JSON "camlist" results
   
   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.

   
   
5. 
   View attachment 228074

CHANGELOG:

[5.9.9.75] – 2025-09-14

Added
• N/A

Fixed
• Non-system admin users will no longer see camera IP addresses in the JSON "camlist" results

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.

My apologies for being late to the "party". Did not know I was supposed to be having problems and assumed if I just kept updating, like I always have, any issue would get fixed, like it always has, at least for me. Would you be so kind as to tell me exactly which of these .dat files I need to keep and which to delete. I run a very simplified setup, no concerns about losing anything. I can easily start fresh if need be even with a new copy of BI if necessary. Thank you for your hard work and all of this information.

 

[jaydeel]

My apologies for being late to the "party". Did not know I was supposed to be having problems and assumed if I just kept updating, like I always have, any issue would get fixed, like it always has, at least for me. Would you be so kind as to tell me exactly which of these .dat files I need to keep and which to delete. I run a very simplified setup, no concerns about losing anything. I can easily start fresh if need be even with a new copy of BI if necessary. Thank you for your hard work and all of this information.

I don't think you actually need to do anything.

But if you like to keep things tidy, and your system is working normally, then you can delete (or move) all files in the C:\BlueIris\db folder EXCEPT records.dat and extra.dat.

Just FYI, my system's been running fine without taking any action, but just now I created a new folder named 'db archive' and moved the legacy files there for temporary safekeeping.

You should be seeing a message like the following in the messages log. If you are not seeing it, then definitely don't take action.

 

[NonTech]

I don't think you actually need to do anything.

But if you like to keep things tidy, and your system is working normally, then you can delete (or move) all files in the C:\BlueIris\db folder EXCEPT records.dat and extra.dat.

Just FYI, my system's been running fine without taking any action, but just now I created a new folder named 'db archive' and moved the legacy files there for temporary safekeeping.

You should be seeing a message like the following in the messages log. If you are not seeing it, then definitely don't take action.

View attachment 228581

Thank you for your reply. That is exactly what I have been seeing in my log.

 

[jaydeel]

5.9.9.83

Help PDF: not updated

Changelog...

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

[5.9.9.83] – 2025-09-23

Added
• Deletion of temporary streaming profiles upon startup
• Start/ending time controls on calendar control for clips and timeline selection --- see Screenshot #1 below
• A new "Delete camera" dialog to let you decide how to handle orphaned clips and alerts --- see Screenshot #2 below

Fixed
• Adding items to an unmanaged folder resulted in posted DB errors
• Adding or deleting groups while running as a service did not update the group selection box

Changed
• Further improved use of encoding sharing with stream overrides via UI3 (and fixed new .82 issues)
• Using the calendar from the timeline, then cancel, removes the time selection

NEW FEATURES...

Screenshot #1 - new Start/ending time controls on calendar control for clips and timeline selection



Screenshot #2 - new "Delete camera" dialog to let you decide how to handle orphaned clips and alerts

 

[BORIStheBLADE]

I keep coming here to see the 6.0....

 

[IAmATeaf]

Not noticed or seen this before. Seems like the cam got triggered by a group and the trigger then ran for 15+ hours? I have the system set to cut the file at either 4 hours or 1Gb so it does mean that BI thought that this was a single event?

Any info I can check to try and get more info on the possible issue?

 

[Tinman]

Not noticed or seen this before. Seems like the cam got triggered by a group and the trigger then ran for 15+ hours? I have the system set to cut the file at either 4 hours or 1Gb so it does mean that BI thought that this was a single event?

Any info I can check to try and get more info on the possible issue?View attachment 228647

I have seen this before due to accidently starting a camera recording by not realizing it. The spacebar can start/stop recording in BI. It's one of the first things I change in the keyboard shortcuts options. Just guessing here. The BI log may tell you more of what triggered it.