@fenderman, Dude, what the F.... Ease up a bit buddy! All I said is that they should be more honest about what the updates me. THEY ARE NOT honest about that. They should indicate that it expires in a year. They did not. They make it sound like you get unlimited updates until you decide to go to the next major upgrade.
You made an accusation about "bait and switch" and that the developer is "dishonest" when in fact its you who cant read. It says it in black and white, CURRENT VERSION UPDATES!!! Its not his fault that your reading comprehension is poor. PLEASE use another product. You dont deserve BI. Also answer me this - I posed this earlier. Would your parasitic mind feel better if he called it BI6? Essentially its an OCD problem on your end. Here are the updates that were included in BI in the last year, including deepstack integration and dual steaming. NONE of these were promised to you. You got them. He could easily have waited to publish these updates for 1 year and called it BI6. Just like every other VMS does. Instead you get it right away yet you BITCH like a little girl over 30 dollars.
5.5.3 - November 16, 2021
A Copy button has been added to the camera settings page to facilitate the quick replication
of settings between profiles and cameras.
Right-click menu shortcuts added to several of the command buttons at the top-left of the
main window.
5.5.2 - November 3, 2021
Export camera status in CSV format.
Status Alerts now offer the ability to fire on both a timed basis and more quickly for
important status updates.
TLS/SSL is now supported for MQTT connections, with the requirement that valid
certificates are provided in PEM format.
When DeepStack is auto-started it is added to a Windows “job” object so that if
Blue Iris
exits unexpectedly, DeepStack is closed as well, preventing a system resource leak.
5.5.1 - September 23, 2021
The DeepStack AI feature to detect/ignore static objects has been improved by
implementing some hysteresis—it now takes time (up to 2 minutes) to consider an object
either static or “gone” from the scene. This prevents false alerts caused by static objects
that only temporarily disappear from detection. Also these algorithms are now applied to all
objects, not just those enumerated in the to confirm box.
Utilizing the new dynamic group layout functionality, the group setting to Only cycle when at
least one camera is detecting motion, triggered or alerted behaves on the browser or client app
as it does on the console—showing all cameras at once that meet this requirement.
The camera layout option to Open in desktop frame is now memorized per group as well as per
camera. When selecting a group on the console, cameras are automatically moved to the
desktop or back to the console. Cameras that are not in the selected group are left as they
were. Camera desktop window position is currently not group dependent at this time.
PAG E 12
Zoom in the clip viewer will now fill all available space.
5.5.0 - September 13, 2021
Groups are now created and deleted explicitly. Previously, the only way to delete a group
was to remove each camera individually. In addition, the role of a group has also been
expanded to include layout. A group’s layout now consists of a set of cameras in a particular
order. Each camera may have a default zoom position, relative size, and aspect ratio. The
group itself may specify a height and aspect ratio, or these may be determined automatically.
In addition to the existing left-right ordering, a group’s layout may also be broken into
columns and subgroups.
When a camera is zoomed, all layout space available is utilized (previously the zoomed
portion was cropped to fit the original aspect). Using this new camera zoom functionality
together with layout options to “scale to fill,” it’s now possible to create layouts which force
cameras into grid patterns without spacing via scaling and cropping.
Groups, when displayed via clients, now appear as the group does on the console with
headers, borders and icons. You can also force a group’s height/aspect on the console to
make adjustments easier.
Dynamic layout for phone and other clients. If a group is configured for an automatic aspect
ratio and the client sends both a width and height request (&w=xxx&h=yyy) then a
temporary layout is created to custom-fit the requested aspect ratio (and resolution if the
group is also configured for an automatic height). The next release of the phone apps will
support this feature, making group streaming look great in both landscape and portrait on
any device.
5.4.9 - June 25, 2021
Specify a maximum trigger time [5.4.9.12].
Playback offsets for new alerts [5.4.9.11] 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 [5.4.9.11].
Specify zones used for DeepStack [5.4.9.9]
PAG E 13
Specify known plates for Plate Recognizer for alert rules; “myplates” and “notmyplates”
objects may be applied to individual alert actions [5.4.9.9]
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,
car+licenseplate.
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. [5.4.7.7]
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.
PAG E 14
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
(5.4.5.3) 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
PAG E 15
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
(5.4.4.3) 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
(5.4.3.5) 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.
PAG E 16
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
Settings.
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.
PAG E 17
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 5.3.9.10
or newer for uninterrupted push notifications from the iOS app. The new expiration is
March 25, 2022.
5.3.9 - January 29, 2021
A new option on Settings/Other allows you to perform an encryption on all passwords
stored by Blue Iris (they are otherwise Base-64 encoded). Changing this setting does not
affect stored passwords until they are next loaded and re-saved. While this does provide
strong security for your passwords in the event someone will have access to your PC
registry, the major disadvantage of password encryption is that if you must transfer
your .REG settings to another PC, you will need to re-enter all of your passwords, as they
may only be decrypted on the PC on which they were encrypted—not ideal for a backup/
restore unless they are done on the same PC.
A new button in the Timeline view for “instant reply.” This will automatically begin
timeline playback 30 seconds back. You may click it multiple times to transport back 30
seconds at a time.
A new interface to the Sentry Smart Alerts system allows you to select person and/or
vehicle detection. Make this change by using the Artificial Intelligence button found on the
Trigger tab in camera settings. This may not be fully functional until 5.3.9.1.
When switching from main stream decoding back to sub stream decoding, the main stream
frame buffer is now deallocated, returning RAM to the system. Previously once the buffer
was allocated, it remained until the camera was reset.
5.3.8 - January 12, 2021
By default, alerts are simply database entries which reference actual video files (clips). You
may now right-click on the alerts list to export individual alert segments as video files. If
you choose to “replace” the alert, the MP4 file reside in the Alerts folder. When you open
PAG E 18
the alert while it’s still associated with a clip, the clip will be opened for playback, not the
exported file.
You may also choose to automatically export alerts as MP4 videos with a new option on the
Trigger tab in camera settings. This may be useful for immediate backup or AI analysis of
alert video.
When you delete a clip, its alerts which have their own associated files (JPEG or MP4), now
will remain in the alerts list and the alerts folder.
Alert list items are now updated with any additional trigger sources and zones when the
trigger ends.
Clip list preview images are prepared and drawn asynchronously in order to display the clip
list more efficiently and to retain UI responsiveness on systems with very large displays and/
or large databases.
5.3.7 - December 20, 2020
There are now a total of 16 possible drive folders configured on the Settings/Clips page.
Added “On red shield” and “On green shield” actions sets editable from the Schedule page
in Settings.
Smoother transitions will now occur with auto-cycle both locally and remotely when using
dual-streaming. The software attempts to start main-stream decoding on the “next” camera
in the cycle at 2.5 seconds prior to the switch.
Settings/Users may be configured with Profile/schedule changes access separate from
Administrator access.
The /admin?trigger and JSON trigger commands, when supplied with either a memo or JPEG
image, will always force a new alert list image to be created. Normally, when a camera is re-
triggered (triggered again while already triggered), no additional alert list image is created.
Alert counters are maintained for each camera for each user. Previously, these counters
were incremented when an alert image was created—now they are incremented only when
alerts are actually fired (a push, email, etc). This allows time to cancel the alert via AI
extensions without the counters increasing.
PAG E 19
The “main menu” button has been replaced with a Settings button and an “add camera”
button was added. The pop-up menu is still available by right-clicking.
Video overlays are now always written to the BVR file. Each overlay object has a new flag
Require live display of overlay at the time of recording which determines whether or not the overlay
is displayed during playback. This allows you to decide whether or not the overlays should
also be toggled during playback when you toggle the overlays on and off while actively
recording.
Toast popup alert actions will now display a large “hero image” of the camera’s current
image.
5.3.6 - December 2, 2020
The JSON alertlist command with optional parameter v=2 now reads only the index.dat file
which greatly improves the performance for pulling the alerts list from the client phone apps
when there are hundreds or thousands of alerts. Individual alert item detail is now
appended to the /alerts/ image request with optional parameter v=2.
On the Settings window, Check for Updates is now Check for News and Updates. Notices posted
here ultimately will replace Mailchimp email blasts which are now used to advertise our
Friday Quick-start Webinar series. When there is news, a clickable blue circle icon will
appear in the Blue Iris status bar.