Ken recently shared that
Blue Iris would identify 'protected' Alerts during a Database/Regenerate action by checking if existing JPG and/or DAT files had the 'read-only' file attribute set.
I recently found issues with this strategy when I noticed that the JPG and DAT files were not always having their 'read-only' attribute set when Alerts were protected via the following methods:
- via UI3
- via the Android Blue Iris app
- via the iOS Blue Iris app
I reported these to Ken a few days ago. As of version
5.7.9.11, this issue appears to be
fixed.
This should provide more confidence that protected Alerts will survive a Database/Regenerate action.
Of course, this applies only if you are saving hi-res JPGs, or DAT files with the Alerts you are trying to protect.