fenderman
Staff member
- Joined
- Mar 9, 2014
- Messages
- 36,901
- Reaction score
- 21,270
5.5.4 - December 8, 2021
.DAT files created by DeepStack analysis are now formally managed in the Alerts folder.
They are now represented in the Alert folder size calculations. If you use these files, you
may want to run a Database/Regenerate so that their sizes are loaded into the database and
any orphan files are adopted, even if there are no associated .JPG files.
If you use the option to burn DeepStack analysis onto alert images, the memo (person:85%
for example) and license plate data are added as metadata to the .JPG files so that this
information is no longer lost with a full Database/Delete & Regenerate.
Trigger zones are now added to the alert .JPG filename alongside flags so that this
information is no longer lost with a full Database/Delete & Regenerate.
.DAT files created by DeepStack analysis are now formally managed in the Alerts folder.
They are now represented in the Alert folder size calculations. If you use these files, you
may want to run a Database/Regenerate so that their sizes are loaded into the database and
any orphan files are adopted, even if there are no associated .JPG files.
If you use the option to burn DeepStack analysis onto alert images, the memo (person:85%
for example) and license plate data are added as metadata to the .JPG files so that this
information is no longer lost with a full Database/Delete & Regenerate.
Trigger zones are now added to the alert .JPG filename alongside flags so that this
information is no longer lost with a full Database/Delete & Regenerate.