Wednesday, October 6, 2021

Quick Blue Iris with DeepStack debug

Note this write refers to Blue Iris version which is a beta release so there may be some differences to the version you are using.

Turn on DeepStack save details.

To do real debug you need to turn on Save DeepStack analysis details for the camera. Open camera properties, go to the Trigger tab and click on Artificial Intelligence.
AI options dialog

This will create a ".dat" file in the Alerts folder for each alert with info about the frames DeepStack processed.
Alerts folder listing

Find the alert pic.

If you are here you are probably have this but if you are just not seeing an alert clip for something you know should be there start here. Open the cancelled alerts folder and find the alert picture you think should have triggered and alert. 

Note if there is no alert you have a motion detection issue. DeepStack analysis below sends frames ignoring motion and object to detect settings for the camera.

If you have an alert that you think DeepStack should have triggered an notification for here are some simple things to check:

Does the motion alert have a return 100 or -1 for the memo?

If so DeepStack has crashed or hung. Either way it needs restarted.

Still getting a return 100 or -1 for the memo after restart?

Ran into this the other day on one of my servers. After a restart DeepStack would work for a few minutes and the stop. Looked in the logs (docker logs for Docker installs) and found the return codes of  200 changed to a 400 then 500s. I tried several things. I backed out the last change, restarted and watched to see if I could sort an event causing the crash but it just kept working. So hard to say what to do other than keep restarting DeepStack till it stays running.

Does the motion alert have a nothing found for the memo?

Double click on the alert picture you want to debug and turn on analyze by right clicking in the playing clip and selecting.

Analyze options select 

I find it helpful to turn on overlays as well.
Overlay options selection

Next open the DeepStack console via the status icon.

You will want to restart playing the clip at this point and play it backwards. Note the Alert picture appears to be the last frame of the clip just double clicking on that alert plays forward from that position.

Stop when you get to the place where the thing was not detected that you think should have been.

IDed frame

Now you can compare the saved (.dat file) info against the IDed frame. In the above instance it IDed a "cat" at a few places but checking the 2 frames sent to DeepStack we see the alert clip does not necessarily match. 
First DeepStack frame

Second DeepStack frame

Notice the above is the alert picture and that they are in reverse order in the listing.

If I switch to Analyze with motion detector and play forward from a little before the first sent frame I can then see what motion triggered the alert. It appears to be about half a second after the first sent frame. It appears this is related to the make time and the first frame sent to DeepStack is from the start of the make time and the rectangle below is the end of the make time.

So at least one issue here is that the IDed frame from analyze came between the frames sent. So in some cases (but not this one) playing with the make and break times might help. 

In this case the camera is set to send a picture to DeepStack every 750ms for up to 30 images but BI appears to have only sent 2 frames 2.061 seconds apart. Though looking at the timestamps on the images shows about 4 seconds actually passed between them. This would seem to indicate something it wrong in Blue Iris.

Then there is also the issue with DeepStack not seeing anything in the second sent frame. That would seem to indicate a model issue. Short of creating your own model there is little to be done about that.

It IDed something else in the picture but not the thing I wanted.

Again running analyze on the clip may help. For example in this image below from DeepStack analyze we see this.

And from motion analyze we see this.

You will note there are 6 raccoons in this shot. The lone one is mainly IDed from its tail. Two motion blocks are on a second raccoon by BI's motion detection and the reset are unseen. DeepStack seems to connect the lone raccoon to its tail to ID it as a cat but takes the 4 in a group, along with the dog house as one objects and IDs it as a dog. Note too the confidence was higher in the second clip but the results returned were from the first clip. I could see how this might been interpreted as a bug though whether to return the min, max, average, confirmed, first or last could be a matter of taste or best fit for a given target. This also might give some insight into tweaks in motion detection settings that might help you get better notifications.

Thursday, August 26, 2021

Simple copy paste reply for "what cam / system should I get?" posts.

People seem to not read the links so I've made this reply to copy paste in.

The probs with asking for info like this are that setups can be VERY subjective as to what is good enough and you mostly get I like or hate X for replies even if you have specs for what you need.

First thing you need to think about is what is it you expect to see. For cameras there are DORI (Detection, Observation, Recognition, Identification) numbers that tell you at how many feet you can expect what level of detail you can see. So pick a level, Detection, Observation, Recognition or Identification that you can live with first or you are just wasting your time and money. If you really have no idea then stop here and get something cheap like a Blink Mini to get a feel for what you can and can not see.

Before looking at brands sort the number cams and specs each needs to be to see that level of detail at the distance each camera is expected to monitor. Here are instructions for a free online tool that lets you virtually add cams to your site and play with specs to see coverage and expected results.
Then you can make a plan for what you will need and not end up tossing stuff for upgrades.Remember you do not need to do it all cameras, lights and sensors at once so this can also help prioritize the order to add things. 

Avoid WiFi wherever you can. Since you need to get power out there anyway you should look at Ethernet Over Power adapters where running Ethernet cable is not practical.

That said the $100-200 per cam range seems to be the sweet spot for bang for the buck. Though as I've said some will be fine with cheaper and others will not consider any cam under $1K. So sorting what works for you is key. My "go tos" if you have a bit of light and your target is under 50 feet max are ColorVus. For further I like Dahua varifocals (zooms). But I have a dozen brands, much less models in use.

As far as a NVR you will want to make a list of features you want and then see which of the ones that has those looks easiest for you to work with. Personally I like Blue Iris. Mainly because it is so easy to interface with things like home automation and AI systems. Plus relatively simple to upgrade a PC to well beyond the limits of a standalone NVRs. But for example if you wanted camera and radar linkage you might be better off with a Dahua setup. Of course we are talking serious money there. Either way leave room to grow as odds are you will want to add to your system.

Even if you have the bandwidth for recording to the cloud I would only plan on it as a backup. The ultimate setup would be recording 24/7 to a SD card in the cam and a local NVR then backing up alerts to the cloud. As a rule being able to record 24/7 means no battery powered cams.

Lastly think about supplemental lighting like accent lighting and or IR floods as in camera lights tend to draw bugs and spiders. You will want to place these extra lights off axis from the cam to avoid glare issues too.

Wednesday, July 14, 2021

Blue Iris with DeepStack Notes

Been keeping notes of what I've see since DeepStack has been integrated with Blue Iris. Moving here for others to see. Hopefully to help them when encountering similar issues.

Iris6: Updates so far: timestamp is when the version was backed up / replaced, not installed. 

C:\Program Files\Blue Iris 5\BlueIris_*.exe

-rwxr-x---+ 1 Administrators avata 17048024 Apr 23  2020 BlueIris_52601.exe

-rwxr-x---+ 1 Administrators avata 17048536 Apr 26  2020 BlueIris_52603.exe

-rwxr-x---+ 1 Administrators avata 17049048 May 16  2020 BlueIris_52712.exe

-rwxr-x---+ 1 Administrators avata 17873880 Apr  5 18:47 BlueIris_54102.exe

-rwxr-x---+ 1 Administrators avata 17875416 Apr  6 10:54 BlueIris_54200.exe

-rwxr-x---+ 1 Administrators avata 17877464 Apr  8 13:40 BlueIris_54202.exe

-rwxr-x---+ 1 Administrators avata 17885144 Apr 14 17:10 BlueIris_54305.exe

-rwxr-x---+ 1 Administrators avata 17975256 Apr 17 16:09 BlueIris_54308.exe

-rwxr-x---+ 1 Administrators avata 17975256 Apr 20 17:40 BlueIris_54309.exe

-rwxr-x---+ 1 Administrators avata 17976280 Apr 22 19:00 BlueIris_54311.exe

-rwxr-x---+ 1 Administrators avata 17976280 Apr 25 14:54 BlueIris_54312.exe

-rwxr-x---+ 1 Administrators avata 17979864 May  6 22:02 BlueIris_54407.exe

-rwxr-x---+ 1 Administrators avata 17982424 May 13 13:57 BlueIris_54503.exe

-rwxr-x---+ 1 Administrators avata 17985496 May 19 16:21 BlueIris_54602.exe

-rwxr-x---+ 1 Administrators avata 17986008 May 20 14:05 BlueIris_54603.exe

-rwxr-x---+ 1 Administrators avata 17995736 Jun  2 17:58 BlueIris_54707.exe

-rwxr-x---+ 1 Administrators avata 17995736 Jun  4 17:04 BlueIris_54708.exe

-rwxr-x---+ 1 Administrators avata 17996760 Jun  8 16:46 BlueIris_54709.exe

-rwxr-x---+ 1 Administrators avata 17997784 Jun 11 17:04 BlueIris_54711.exe

-rwxr-x---+ 1 Administrators avata 18009048 Jun 17 13:03 BlueIris_54801.exe

-rwxr-x---+ 1 Administrators avata 18323416 Jun 19 11:07 BlueIris_54802.exe

-rwxr-x---+ 1 Administrators avata 18327000 Jun 26 11:09 BlueIris_54901.exe

-rwxr-x---+ 1 Administrators avata 18329048 Jun 28 19:03 BlueIris_54902.exe

-rwxr-x---+ 1 Administrators avata 18352088 Jul  8 17:25 BlueIris_54906.exe

-rwxr-x---+ 1 Administrators avata 18358744 Jul 12 16:41 BlueIris_54907.exe

Initial gotchas from testing with single indoor cam

Hell Yeah! Direct Deepstack Integration - 5.4.0 - March 31, 2021

Testing with Amcrest 4k in living room, Blue Iris and DeepStack CPU version for Windows. Doing basic test of walking the same path to see how various options affected detection.

Alerts must be enabled and set to triggered for AI to work even though no actions might exist.

Turning on any "advanced objection" (for instance to only check motion in zones) will limit to to ~30 secs min between AI calls.

Dropping the break to .1 secs still only got down to one pic per 1 sec make and only one AI recog/10 secs (even with make of .5 and breal of .1 only got 23 pics in ~30 seconds of action with only 2 of those AI rec pics. Though on one run I got 4 AI rec pics of 24 in 40 seconds of action.

Setting min time between alerts got me 4 of 23 in 37 secs of action.

Adding also on retriggers got 3 of 23 in 42 secs of action.

Switch from edge vector to simple algorithm and got 4 of 11 in 31 secs (Note 3 of the 4 were in a 9 sec window)

Switch back to edge vector and added hi-def and got 2 of 24 in 41 secs

Increased min obj size and contrast to 608/50 from 550/25 which got me 0 of 8 in 26 secs

Turned off hi-def and got 1 of 8 in 27 secs

Reduce contrast back to 25 got 2 of 18 in 33 secs

set min obj size to 401

Set to send 30 frames to AI per alert and set make to 30 sec. Got 0 of 1 frame IDed

Set break to 3 secs and got 3 of 3 frames IDed

Set break to 0.5 and got 6 of 15 frames IDed


On version

Setup on most of the live outdoor cams on Iris6.

4/17/2021 @ 16:54 Iris6

Changed DeepStack from Medium to High

Upgrade to

4/20/2021 20:08

Upgrade to

4/23/2021 19:32




Seeing some issues with person detection.

4/27/2021 11:11

Adding email and SMS alerts using sites gmail. Variables available are:

&ALERT_DB The DB record locator for the most recent alert image for the camera.

&ALERT_PATH The path to the most recent alert image on the camera. Note that alert images are not saved to disc by default;

this is controlled with a setting on the Trigger page in camera settings.

&CAM Camera’s short name

&FILE The path to the currently recording clip on the camera

&MOTION_RECT The coordinates of a rectangle enclosing the motion [left,top,right,bottom]; values are normalized 0-1.

&NAME Camera’s long name

&PLATE License plate captured with ALPR if configured

&PRESET The most recently used PTZ preset on the camera

&PROFILE The active profile number

&SERVER The system name as set on the Settings/About page

&TYPE The source of the camera trigger, for example MOTION_A, EXTERNAL, or DIO. The letters following MOTION refer to the motion zones. Most useful for knowing if motion or external sensor trigger

&WAN The current system WAN address as shown on the Settings/Web server page

%x, %X, etc. Date and time. See the table below for a full list of time formatting macros.

&MEMO info like object type and confidence %

Email template

Blue Iris alert &MEMO on &CAM

Motion detected on camera: &CAM 

Name: &NAME

Alert Type: &TYPE


Profile: &PROFILE

Preset: &PRESET

Memo: &MEMO

plate: &PLATE

Select first 2 attaches

SMS template

Blue Iris alert &MEMO

Motion detected on camera: &NAME


No attachments

Facial recognition seems iffy at best.



Added script and alert actions to copy confirmed alerts into folders by object found.

Note a space in the comma delimited list of object types will stop the AI from processing!


Add actions to copy alert files to folders based on object types detected.

Pics are in folders by type AI detected, not what is actually in the shot.

Known types

bird, cat, dog, horse, sheep, cow

lumped into other folder: elephant, bear, zebra, giraffe, person

See robmarkcole/HASS-Deepstack-object.

Bumped min confidence to 60% on DAH412



noticed mouse was not in "animal" list but is in object type list so added things to look for on DAH412

Set min confidence to 60% on DAH628 to cut down on seeing a tree as a person

Added save flagged actions to AM476

AI set to detect 


copyPublic.bat script is

echo %* >> F:\BlueIris\cpLog.out

copy E:\BlueIris\Alerts\%2 C:\_dea\odrive\\cams\flagged\%1 2>&1 >> F:\BlueIris\cpLog.out

Note first line is just for a debug log

Action looks like 


Note this action on fires if the AI detects at least one of the Required AI objects. In this example elephant,bear,zebra,giraffe,person

other is the folder here and &ALERT_PATH is the filename of the marked up alert.


made aliases for scripts so could tell in actions windows which was which and moved the bat and log files to the flagged folder.

Added scripts and folders for bear and person.

Also added &MEMO to all the actions so will be in log.




5/7/2021 10:16

Upgrade to

5/8/2021 14:39

Noticed a typo in copyPublic.bat script made on 5/4 broke all the saving of flagged alerts fail. Fixed it.

Also changed repost when triggered from every 10 sec to every 60 to try and stop Odrive warnings about long wait times.

5/9/2021 13:10

Removing "truck,bus,bicycle,motorcycle,car" from DAH616 AND IPcam124 now detection set to


DAH628 changed to mouse,bird,cat,dog,horse,sheep,cow,elephant,bear,zebra,giraffe,person:70

Replacing dead DAH626 with DAH345 set to 

mouse,bird,cat,dog,horse,sheep,cow,elephant,bear,zebra,giraffe,person @ 60%

5/14/2021 System hung ~4:42 AM

rebooted and upgraded to (note is now listed as stable)


upgrade to to get custom models support. (note almost no detected objects after)


Note: Turned out you can only have one custom model.


upgrade to try and sort almost nothing being detected. Helped but still detecting less than before. Seem to be getting fewer triggers causing fewer frames sent to AI.


Increase extra frames to 30

upgrade to try and sort almost nothing being detected. 


turned off custom models which helped on cams set to 10 sec end triggers so set all cams to 10 secs.

It appears the second model is causing the issues. Left just the logo model in the custom folder and things seem to be back to normal.

Also turning off ignore static objects as that seems to be causing issues.

6/15/2021 11:33

switch custom model from logos to plates and upgrade to


update to Adds DeepStack stats dialog.

6/22/2021 9AM

update to (note said 6/17/2021 though not there 6/18)

Finally got a licence-plate hit.

10:10 AM

Added plates to saved alerts.




6/26/2021 14:34

update to

6/29/2021 15:30

Swapped logo custom model for plate one since all it tells you is there is a readable plate in the frame and often mistakes signs for plates.


update Iris6 to

Set up a flag archive script for logo objects


Cloned cams from Iris4 (BI4) to Iris7 with BI5. Massive CPU reduction so installed and setup DeepStack Working well.


update Iris6 and Iris7 to

Iris6:lmost no alerts much less IDed. Cancelled alerts say DeepStack -1. Tried rebooting and such.

Iris7: still working as before.

7/12/2021 17:00

update Iris6 to

Iris6: Still almost nothing getting IDed. Running a clip of me returning from the mailbox registered my face and nothing else. I've unchecked custom models, "default objects and face recog but that did not help. Cancelled alerts say DeepStack -1. Tried rebooting and such.

Iris7: still working as before.


reverted to

Started see alerts almost immediately. Ran the clip through analyse again and is seeing multiple times.

7/14/2021 11:47

Without changing anything IDs on Iris7 seem to have returned to normal.

Update Iris5 to BI5 so now the 4 outdoor and 1 indoor cam servers are all on BI5.
Iris6 (south cams) has DeepStack on the same PC. Iris3 (central cams), Iris5 (north cams) and Iris7 (indoor cams) are pointed at docker instance of DeepStack on separate CentOS 7 server.

Created generic shell script to use with Cygwin to sort flagged alerts into folders by the first thing found.

## where &ALERT_PATH is like DAH412.20210731_143912.4034343.3.jpg
## and &MEMO is like person:93%,dog:81
set -x
export FLAGGED=/cygdrive/e/odrive/
export ALERTS=/cygdrive/e/BlueIris/Alerts
echo "$*" >> /cygdrive/c/DeepStack/cpLog.out

obj=`echo $2 | cut -f1 -d':'`
mkdir ${FLAGGED}/${obj}

cp ${ALERTS}/$1 ${FLAGGED}/${obj} 2>&1 >> /cygdrive/c/DeepStack/cpLog.out

Set script trigger to
C:\cygwin\bin\sh.exe -x C:\DeepStack\ &ALERT_PATH &MEMO
Set objects on the Iris5 cams to mouse,bird,cat,dog,horse,sheep,cow,elephant,bear,zebra,giraffe,person @ 60% and 2 spare frames @ 1 fps. And truck,bus,bicycle,motorcycle,car to the cams looking at the driveway.

Release notes from the help file:

5.4.9 - June 25, 2021

Specify a maximum trigger time [].
Playback offsets for new alerts [] will begin at the motion-leading position rather
than the beginning of the entire pre-trigger buffer.
Hold Control as you double-click to open an alert in order to position directly and then
pause at the AI-confirmed frame [].
Specify zones used for DeepStack []
Specify known plates for Plate Recognizer for alert rules; “myplates” and “notmyplates”
objects may be applied to individual alert actions []
Enhanced synchronization between alert images and alert processing. Alert images are not
created until timer conditions are met on the Alert tab in camera settings. Processing of “re-
triggers” is improved following a cancelled alert.
Improved handing of DeepStack static objects and objects outside of detected motion areas.
On the DeepStack status page you may now choose to show/hide Blue Iris detected motion
rectangles, helpful for diagnosing objects which do not overlap these areas. Also you may
now drag & drop saved alert analysis “.dat” files into this window.
The “run a program or script” action is now “run a program or write to a file.” This will be
handy for external logging.

5.4.8 - June 16, 2021

RTMPS is now supported for Flash live video streams to Facebook, etc.
A DeepStack status page has been added. This allows you to inspect DeepStack results and
performance following an alert confirmation or when using the testing & tuning options in
the clip viewer.
You may now specify 2 objects together with “and” logic on the “to confirm” and “to cancel”
fields for DeepStack alert confirmation by combining them with a +. For example,
An option to add motion overlays when re-encoding has been added to the Convert/Export
clip function.

5.4.7 - May 25, 2021

Support for DeepStack custom model files; specify the path on Settings/AI. Use a custom
folder name, not sharedfiles as this will conflict with DeepStack’s own models. []
select custom models per camera, per profile.
Support for Plate Recognizer’s Make/Model/Color analysis for cars.
A new option to only use Plate Recognizer for alerts where either DeepStack or Sentry has
confirmed a vehicle alert.

5.4.6 - May 17, 2021

As requested by several customers, a continuous + triggered recording mode is now offered
separately from the continuous + alerts mode. This mode ensures that the main stream is
also recorded for cancelled alerts as well as confirmed alerts.
Replacing the Analyze image with DeepStack option on the viewer’s right-click menu is a
Testing & tuning menu with an Analyze with DeepStack option. This option pushes
BVR video frames through DeepStack as quickly as possible (may not always update in real-
time unless you pause and step).
With dual-streaming and direct to disc enabled, main stream frames that are sent through
DeepStack when the camera is triggered are flagged in the BVR file. As these are played in
the viewer with the Analyze with DeepStack option enabled, the image border will be
shown in blue, allowing you to identify precisely which frames were used for the alert
confirmation. A catch-22 arises however if you are using the continuous + alerts recording
mode, as these frames are never actually recorded—use continuous or continuous + triggered if
you want to take advantage of this tuning feature.
When analyzing multiple frames with DeepStack against both “to confirm” and “to cancel”
object lists, an effort is made to choose the “best” confirmed image according to higher
confidences and the presence of (more) faces. By default, the alert will continue with a
single found “to confirm” object, but you can force continued analysis by placing any object
label in the “to cancel” box (even one that will never be found).
The “to confirm” and “to cancel” boxes may now contain labels ending with the * wildcard.
This is handy if you have multiple faces for a single person—you might use chris* for
example to match defined faces for chris_1, chris_2, chris_side, etc.
A new right-click option in the Alerts list allows you to manually cancel and confirm alerts.

5.4.5 - May 10, 2021

( The pre-trigger image is now used as the first image sent to AI for alert confirmation.
This is an image captured at first motion rather than at the moment of trigger, so it may be
earlier in time by as much as the motion sensor’s make time.
When recording continuously (including the new continuous + alerts mode), physical
recording is delayed by the duration of the pre-trigger buffer. This allows the opportunity to
record the main stream frames in the pre-trigger buffer as required. In addition, this means
that if you manually record or start/stop using the traffic signal icon, the pre-trigger buffer
will now also be recorded.
By default, the main stream is decoded when a camera is in full-screen or “solo” in the
window. A new option on the camera right-click menu allows you to disable this and force
the continued use of the sub-stream in these cases.

5.4.4 - April 27, 2021

( face recognition must now substantially overlap a “person” object detection. Too
many false-positive “unknown” faces result otherwise. A new macro &JSON may be used
for access to raw DeepStack object detection data during an alert.
When the continuous+alerts record mode is used with a dual-streaming camera along with
direct-to-disc, the result is a BVR file which will contain the sub-stream continuously
recorded, but the main-stream only recorded when the camera is in a triggered state.
During main-stream playback, the sub-stream will be upsampled whenever the main-stream
is not available.
The DeepStack detect/ignore static objects option will now force a re-analysis of the image each
10 minutes when not triggered in order to refresh the static objects collection.

5.4.3 - April 9, 2021

( Minimum confidence may be overridden by appending a : and the number to any
label placed in the “to confirm” or “to cancel” boxes on Trigger/AI as well as on each alert
action by, for example person:80,car:70.
DeepStack objects recognized only when substantially overlapping areas where Blue Iris is
also tracking objects in order to reduce the detection of static objects.
Require AI objects or use them to skip individual alert actions.
Motion detection updates to produce fewer/larger object rectangles with more effective
edge-vector tracking.
DeepStack “mode” setting. Processing time added to object detection log entries.

5.4.2 - April 6, 2021

A new action set “immediate actions” has been added to the Trigger tab in camera settings.
This action set runs before alert AI confirmation.
You may now specify up to 999 images to be sent through DeepStack for alert confirmation
(or until the trigger ends).
By popular demand, you may now delay recording or snapshots until alerted rather than
starting immediately upon a trigger. This allows the AI time to analyze the trigger before
recording begins.
With a new option on Settings/AI you may now select to save unknown faces to a specific
folder for later review or import.
At startup and after PTZ movement, DeepStack will now analyze the scene for initial objects
in order to prevent alerts on static objects.
The marked-up alert image is now re-saved to the database so that it will appear on the
alerts list.
With a right-click option in the Viewer, you may run a snapshot through DeepStack for
analysis. This will eventually be expanded to include BVR content.

5.4.1 - April 3, 2021

Support for DeepStack facial recognition. Maintain the face list from the AI page in
Alerts may now be cancelled with specific DeepStack labels. It’s now possible to Alert only
when “unknown” faces appear or only when there is NOT a dog present, etc.

5.4.0 - March 31, 2021

Support for DeepStack integration (without the separate AI Tools package) via new Settings
AI page. DeepStack may be used for object classification to confirm alerts containing
persons, vehicles, pets, and more.
Plate Recognizer ALPR configuration has been moved to the new Settings AI page. You will
need to reconfigure this integration, now done globally.
Support for legacy SeaIO devices from SeaLevel.
Test button added and UI updates to the camera Schedule/Events page.
You may now select to use a specific global schedule on the camera Schedule page.
“Use defaults” button added to the video encoding configuration pages.
Updated Apple push notification service which will expire February 28, 2021; use
or newer for uninterrupted push notifications from the iOS app. The new expiration is

Tuesday, February 23, 2021

Uncheck preserve time order unless you need the 000 image to always be the latest.

Not sure how but somehow I seemed to miss what Post tab, check Post JPEGs, check Maintain a ring of [some number], check preserve time order actually does. The default seems to be checked though I notice it is unchecked on some of my cams which I guess is why I had not noticed that when checked it renames all the posts in the ring so the newest is 000. Similar to log file rings if you are familiar. Now this is great if you want to use the 000 image on a web page or app to show the latest and only keeping a few. Not so great if your ring is a larger number like 10K or you are, as I was just trying to do, generate a time lapse from them. Since the file names keep changing it gets messy real fast. Especially if you are trying to save off some before they cycle off and then add the newer ones. I saw names changing mid copy for instance. Even worse if you are syncing those images to the cloud since it is not only having to process uploads but name changes. Assuming you upload app even recognizes name changes of course and is not reuploading each file multiple times. Not sure what CPU load this having but considering I have some rings set to 10K on servers that are about max safe CPU it is probably not insignificant. 

So make sure "preserve time order" is unchecked unless you really need that image order.

While here you might want to think about "Also post No Signal images". Again checking this might make sense for a local display of the latest image but in most cases it is a waste of resources.

For more on optimizing your Blue Iris server performance check out Optimizing Blue Iris's CPU Usage