Novedades (Versión 2)

Según vayan publicándose nuevas actualizaciones del programa, se irá completando esta página con una lista detallada de las novedades y cambios.

2.64

  • You may now specify a port number for your FTP server if it does not use the default of 21.

  • You now have the option to enable web server authentication for non-LAN connections only.

  • The Options page export/backup button now creates a file in the RegEdit text format instead of the binary format.

  • The camera properties page now has a setting for Event Color.  This will be used first by the iOS client to mark clips in a timeline view.

  • There's a new advanced option for network IP cameras to use the socket option for TCP keep-alive.  This should only be used is situations where it is known to be necessary.

  • RTSP streaming startup errors are now displayed to make configuration easier

2.63

  • The Options page now has a field to specify a name for your Blue Iris system.  This will be used to identify the connection once established from the iOS client.

  • The Options page also has a new button to export or backup your entire Blue Iris configuration from the registry.

  • The Trim feature now allows you to specify MP4 format with H.264 encoding.

  • You may specify a volume setting (1-100) for sound alerts.

  • A potential pitfall for H.264 decoder instability with some IP cameras has been resolved.

2.62

  • Two new Options pages have been added for Mobile Devices and Digital I/O.

  • From the Options/Digital I/O page you may now enable serial port communication with the Arduino UNO open-source project board.  This is a very inexpensive device available at electronics hobby shops or online via eBay.  Although less expensive, configuration of this device will not be as simple as the Sealevel board.  The UNO must actually itself be programmed to respond to data it receives via the serial port from Blue Iris.  When an alert is triggered, Blue Iris will send a single byte of data to the UNO, an ASCII number 0-7 representing the output number specified on the Alerts tab.  Blue Iris also monitors for incoming serial data, and interprets each incoming byte as the 8-bits representing digital input numbers 0-7, which may be used to trigger the motion detector.

  • A Blue Iris iOS client is under development.  When this app is released next month, and you use it to connect to your Blue Iris server, an entry for each device will appear on the Options/Mobile devices page.  In addition to tracking mobile device client connections, this page will allow you to "pair" with each device, in order to allow your Blue Iris to send "push notifications" to these devices.  Following the release of the iOS client, work will begin on an Android version.  Client apps are not planned for other devices at this time.

  • On the Alerts page, support for the IM alert has been discontinued.  This alert relied upon outdated technology.  It has however been replaced by the Mobile device push notification option.

  • Development has begun on the JSON (JavaScript Object Notation) interface.  This HTTP-based interface will provide the basis for a very powerful set of remote administration capabilities which will be leveraged first by the upcoming mobile device clients before then being applied to the basic web browser-based access pages.

  • A new and long-overdue FAQ page has been started to address the most commonly asked support questions.

2.61

  • ActiveX version 1.0.3.4 allows the ability to select between 3 preconfigured streaming configurations for varying connection speeds.  Right-click on the window to select.  On the Options/Web server page, you may now configure these streams independently.

  • The use of the pre-trigger frames recording option is now much easier on your system resources.  These images are now maintained in RAM as 12-bit I420 (YUYV422) blocks of memory instead of the previous full 32-bit RGB DIBs, saving considerable RAM.  This new format is also more easily digestible by the encoders, so when it comes time to record all of those images all at once, it's not as great of a shock to the system.

  • Up to 10 seconds of audio is now also recorded into a pre-trigger buffer to be recorded along with the pre-trigger frames.

2.60

  • This update focuses on providing stability in low-memory conditions.  We may see a 64-bit build of Blue Iris soon.

2.59

  • If you are using Windows 7 or Vista, you will notice a considerable performance improvement when using the clip viewer to shuttle or to playback BVR files.  The Media Foundation's Enhanced Video Renderer is now used to draw video instead of GDI+ calls.

  • The EVR is also used by the updated version 1,0,3,4 of the ActiveX control.  You should manually click on the link at the top of the default HTML page to install this updated component.

  • Audio/Video sync has been improved when playing BVR files locally or remotely

2.58

  • This version is now Unicode compatible.  It is now possible to use characters from any language throughout the software, including the web server.  All installed HTML pages, as well as email alerts, are formatted in UTF-8.

  • This version is now more easily localizable into other languages.  It is possible to link to an external resource file which will be made available for several requested languages.

  • A new version of the ActiveX component is installed, 1,0,2,0, which is also Unicode compatible, and has been signed with a renewed code-signing certificate.  This version also allows you to right-click to select a new option "Copy image to clipboard."

  • When attaching an image to an email alert, two images are now inserted, one at the leading edge of motion and another taken from the current image stream.

  • A new Software Option for double-click to open the temporary full-screen window on either the Blue Iris UI monitor or at the camera desktop window's most recent monitor.

  • The Recycle Bin option for clip deletion is now defaulted OFF.  It was found that this feature has a tremendous OS performance impact (excessive CPU and memory utilization for extended periods).  If you have seen Blue Iris inexplicably use high system resources for large blocks of time, this may be the culprit.

  • By placing a hyphen (-) at the end of a preset name/number, it is excluded from the preset auto-cycle.

2.57

  • The Alternate frame rate option that was previously only available for Continuous recording may now be used for manual and motion based video recording.

  • A new Options page has been added to manage Email Server settings.  Instead of re-entering this information over and over again on each camera's alert/email and SMS pages, it's now done in one centralized location.  The Email server configuration page now also features a Preset option to help configure many popular email servers such as GMail.

  • Support for email servers which require the STARTTLS command have been added.  These include Yahoo and AOL.

  • A new Options page has been added to manage FTP Server settings. Instead of re-entering this information over and over again on each camera's Post page as well as the Options/Clips page, it's now done in one centralized location.  The FTP server configuration page features a Test option to check your settings prior to deployment.

  • A new Options page has been added to manage User settings.  The role of the user eventually will be expanded to allow for varying levels of access to management features of the software.

  • Support for the Sealevel SeaDAC Lite (P/N 8112 and similar) has been added.  This is a DIO (Digital Input/Output) device which will allow you to trigger a camera's motion detector based on a digital input signal received from an external source such as an alarm system, home security system, PIR sensor, electric gate, electric eye, etc.  It may also be used to send an output signal to another device or system when the motion detector is triggered.  The Sealevel 8112 has 4 digital inputs and 4 digital relay outputs.  Support for other devices may be added based on device manufacturer's developer support and customer demand.  In addition to the device and its drivers being installed, you must also have the SeaMAX.dll in your Blue Iris program folder.

2.56

  • The Audio trigger has been modified to use an average-energy algorithm instead of a peak value in order to allow for further "less sensitive" settings.  This was necessary to account for devices on which it is not possible to adjust the audio gain downward.

  • A new software option allows you to select to Prioritize cameras which are sensing motion during the Full-screen auto-cycle

  • A new recording option to record continuously, but cut (create a new movie file) each time the motion sensor is triggered

  • A new Web server option to List only clips from enabled cameras.  This was previously the default mode of operation, but you may now disable this functionality.

2.55

  • The Motion Detector algorithms have been overhauled and enhanced.  A quantization algorithm is first applied which has an inherent de-noise effect.  A persistence algorithm is employed to provide for more accurate background separation.  Finally blob detection algorithm may be enabled which attempts to locate a rectangular region of interest.  With the "overlay motion" test option enabled, you will see this represented as a red rectangle.  This will form the basis for advanced motion-tracking.

  • The MIME type for the ActiveX video streams has been changed from application/streamingmedia to video/mpeg.  It was discovered that the former MIME type caused the stream to be subject to scanning by antivirus "web shield" software, adding significant buffering and stream delays.  As a reminder, you should add blueiris.exe to exclusion and "trusted process" lists in these types of packages whenever possible in order to achieve maximum performance.  Also add the New and Storage folders to your "file system shield" exclusion lists.  Also add the MIME type application/sdp to your "web shield" exclusion list if you are streaming from any RTSP network cameras.

  • Video latency and audio sync issues have been addressed with use of the ActiveX control.  You should be able to open a browser on your Blue Iris PC or LAN to the default.htm page and receive no dropped frames when viewing a single camera.  If you do, you may have a network/web scanning issue as noted above.

2.54

  • A new option on a camera's PTZ tab allows you to automatically cycle through a camera's preset positions during specific scheduled times

  • A new option on a camera's Schedule tab will disable live video and webcasting while the camera is inactive

  • Following a watchdog network reconnection attempt, the camera image will become blue to indicate a loss of signal

  • The web server now properly handles absolute URI requests (which may assist with proxy server support)

  • The ActiveX control has been updated to 1.0.1.5 in order to properly handle "chunked" HTTP transfer-encoding, again for proxy support

  • If the console process crashes while Blue Iris is running as a service, you may now re-run the console without having to first reset the service

2.53

  • HTTP Live Streaming support has been advanced for iPhones/iPads to request live AVC/AAC streams from /h264/cam1/x.m, where cam1 is the camera's "short name."

  • A requirement for having a sound card that was inadvertently added to version 2.52 has been removed.  Without a sound card, the Clip Viewer crashed for non-BVR files.

  • PTZ commands including those from the TrackIT software no longer cancel the motion detector's triggered state

  • The camera Audio tab now has a checkbox to disable audio webcasting for live streaming

2.52.07

  • A memory leak bug was been fixed with the MP4 movie email alert attachment option.

  • The XVID MPEG4 codec may be preferred for recording on slower systems, or on systems where you will be recording from many cameras at once, and you find that your CPU utilization is too high with the H.264 codec.

2.52

  • The ActiveX control has been updated to version 1.0.1.4.  This version has several enhancements, including 8 PTZ presets instead of 5, a higher-quality rendering technique, and a full-screen mode.

  • The clip viewer has been updated to use higher-quality rendering techniques to smooth images.

  • The clip viewer will now open and display MP4 and M2T file types in preparation for these recording formats.  If you plan to use these formats, you should install the K-Lite codec pack onto your Windows systems.

  • The email alert now offers the option to include a 10 second MP4 movie file attachment in place of a still image.

2.51

  • The default video recording compression is now H.264.  MJPEG and WMV are still options, but support for recording with XVID or MP42 has been discontinued.  Older recordings will however still open with the Viewer.  The default video quality for H.264 in percentage terms is now 70%, and you will find that higher values consume much larger amounts of hard drive space without much benefit, so you should re-examine your quality settings for all cameras.

  • The H.264 codec is not found on the majority of Windows systems.  So, if you attempt to create an AVI file with the H.264 codec, it may open on your system only if you install the FFdshow codec.  To obtain this, it is recommended that you Google for and install the K-Lite codec pack.  If you use only BVR files locally or WMV files, this step is not necessary.

  • In a future release, new file formats may be introduced as well such as MP4 (which could potentially replace WMV) and M2TS (which could potentially replace BVR).

  • Dates shown in the Clip List, Viewer, and remote access now reflect "file creation time" rather than "last modified time". 

2.50

  • Efficiency of the console's video display (when running as a service) has been greatly increased.  Display bugs as well as a potential "hang" while shutting down have also been fixed in the console.

  • The 4-up camera display option was briefly removed but has been restored.  A new 2-up option has also been added.

  • Local camera window layout options have changed.  You may now select the previous "fit to window" option, where all cameras are sized equally, or you may choose one of the new ratio options (from 1:2 to 1:8) to specify the relative size of the first window to the others.  A slider has been placed on the main UI to quickly change this setting.

  • Local camera window position layout is now managed graphically via drag-and-drop.  When you have multiple camera windows, click on a camera and drag it onto another camera's window to move it to the new position.  By default the move is a remove/insert.  If you would like to "swap" the two camera positions, hold the Control key while dropping.   

2.49

  • ActiveX webcasting now supports camera audio; next release BVR audio playback as well

  • ActiveX webcasting has been greatly enhanced in terms of throughput and quality by implementing a new buffering mechanism and H.264 video compression.  You may choose the encoder settings from the Options/Web server page.  The Quality and Scale settings on each camera's Webcasting tab now only apply to JPEG (and motion JPEG) webcasting.

  • The legacy MP42 codec has been removed from the webcasting code and will be removed soon from the clip recording code where it will also be replaced with H.264.

  • The Motion sensor page now has Copy and Paste buttons so that you can quickly transfer one profile's settings to another profile.  Also the word "triggered" now appears on to the right of the meter to emphasize the fast that the sensor is triggered when the meter reaches 100%, and not just when it crosses the position of the sensitivity slider.

2.48

  • The RTSP camera stream option now supports MJPEG streams (RTP/AVP 26), as used by the LeveoOne WCS-0030.

  • The Web Server now supports the HTML "Ranges" header to allow clients to download partial files; as a result it's now possible to serve MP4 files to iPhones.

  • The Stats window has been revised to contain a single camera activity summary page, and a single web server connections page.

  • The Web server now uses a single connection sound setting, which may be overridden on a per-user basis for custom user login alerts.

2.47

  • If you are using camera groups, each group now has its own index page (all cameras view), and the entire "all cameras" view has been restored for logins with admin access.

  • JPEG/MPEG/H.264 video stream serving has been improved to better distribute CPU load.

  • You may pull a virtual M3U8 file (MIME type application/vnd.apple.mpegurl) from the Blue Iris server using /h264/{cam}/temp.m or .m3u8.  This will play in QuickTime, iPad and the iPhone using the iPhone Live Streaming format.  This stream is not yet segmented as per the specification, but will provide an hour of viewing at a time with the appropriate bandwidth.  This is experimental at the moment, but is functional, and will be formalized in the near future.

2.46

  • You may pull a raw H.264 stream (MIME type video/H264) from the Blue Iris server using /h264/{cam}/temp.h264.  This stream will play in a tool like VLC, and may be used in future versions of the ActiveX control.

  • You may pull an MPEG-2 transport stream (MIME type video/MP2T) from the Blue Iris server using /h264/{cam}/temp.ts.

2.45

  • You may pull a raw audio stream (MIME type audio/x-wav) from the Blue Iris server using /audio/{cam}/temp.wav.  Audio playback will be added to the ActiveX control very soon using this capability.

  • You may limit the framerate for video preview from the Options/Software page.  Previously, frames were written to the screen as rapidly as they were received from the camera, which may not be desirable if either CPU cycles or video display capability is nearing physical limits.  Note that all frames continue to be internally processed and recorded as configured.

  • Serial port Pelco-D and Pelco-P protocols are now supported from the camera PTZ page.

  • New DDE commands: "schedule=1 or 0" to enable/disable the schedule for a camera, and "profile=x" to override the active Motion Sensor profile for a camera.  If x=0, the camera is inactive (no recording or alerts at all).  Use x=1 for the default Motion Sensor profile.  The schedule is automatically disabled if you send the profile=x command.

  • If you specify the Motion Sensor option to "Restore window when triggered," Blue Iris will also "wake" your monitor if it's in power-saving mode.

2.44

  • Specify the camera number 0-3 in the Parameters box when adding multiple Aviosys 9100/a/b cameras and set the device for round-robin.  Images will be automatically routed to the correct Blue Iris camera.

  • It is now possible to use the Sound alert while running as a service.

  • When using remote desktop the camera image is updated once each 10 seconds instead of displaying the message "Remote terminal session detected."  You may still use a checkbox on the Options/Startup page to override this and display video as quickly as possible.

2.43.02

  • Fix for PTZ double-clicking on all remote pages and the ActiveX control.  It was possible to get the camera to continue moving to its pan/tilt limits by double or triple-clicking the PTZ buttons on the remote pages.  For cameras which have separate motor start/stop commands, you may now hold down the PTZ buttons to move longer distances.

2.43

  • The install now includes an XCastInstall.exe which should be used to install and update the ActiveX control.  Too many systems are blocking the automatic download and installation of the Blue Iris ActiveX control.  A link has been placed on the default.htm page.

  • PTZ cameras with separate button-down and button-up events (for variable duration movement) are now better supported in the main UI, the ActiveX component, as well as the Java and JPEG web pages.

  • The JAVA/JPEG remote page requires that you install JAVA from http://java.com.  JAVA version 6 update 21 has been tested and does fixe the IE crash that would sometimes cause IE to hang/crash when navigating away from the JAVA/JPEG page.

  • The efficiency and throughput of the Web Server has been greatly improved for larger file downloads, such as the ActiveX EXE installer.

2.42

  • Assign each camera to a group by entering a group name on the camera General properties page

  • Specify camera groups accessible to each remote view user on the Options/Web server page

  • Specify additional camera groups to trigger when any camera's motion sensor is triggered

  • The range of the sensitivity slider on the motion sensor page has been widened to allow you to make the detector even more sensitive than previously possible

2.41

  • A new DDE command "ptzpreset=" to move a camera to a PTZ preset

  • In full-screen video mode, double-click outside of any camera rectangle to close full-screen (so no keyboard or right-click necessary)

  • A new Windows Media webcasting option to limit connection to specific IP addresses

  • A new software option to choose how double-clicks within camera windows are handled.   The default is to open the camera in full-screen mode.  Instead, you may choose to open the camera in a desktop window or to open its properties window.

  • AAC audio decoding for RTSP streams, added for Vivotek audio support

  • Fix for Asante Voyager MPEG4+Audio

  • Run Alert errors are now logged

  • Fix for Foscam/BSTi audio decoding

  • Fix for H.264 RTSP decoding

  • Support for all of the latest Intellinet cameras, including audio, using MPEG4 or H.264 RTSP

  • A new option on the Software options page to force the main window or the camera window to the top of the desktop if the "Restore window when triggered" option is also enabled on the camera's Motion sensor page.

2.40

  • Foscam/BSTi audio decoding

  • The ActiveX control has been updated to version 1,0,0,29 which allows a larger XVID frame size, allowing for large index (all cameras) streams.

  • H.264 streaming cameras that support the RTSP protocol may be added using the RTSP stream network IP camera device option. 

  • It should now be possible to connect a camera to a Windows Media (ASF stream) server by using the WM/ASF stream Network/IP camera device type.  You must separate the URL into two components, the IP/host name and the video path.  For example, http://abctest123.c123.a.bc.akamaistream.net/H/111/23222/v0001/reflector:23222.asf  would be host name = abctest123.c123.a.bc.akamaistream.net and video path = /H/111/23222/v0001/reflector:23222.asf

  • The mouse wheel was not working for certain mice/settings to digitally zoom video, and this has been corrected

  • The 4-up camera window layout no longer swaps out the camera in the 4th position for the currently selected camera; this camera-swapping now only occurs in the 1-up view.  The camera "position#" setting controls the ordering of the cameras for now; in a future release, a way to graphical arrange your camera windows will be offered.

2.39

  • A significant change to the motion detection "make time" algorithm has been made.  If you set the make time to 0, the detector will be triggered immediately just as before.  In order to trigger the detector with higher values, additional motion must continue to occur without a time equal to half of the make time elapsing.  The advantage to this is that it's now easier to configure the rejection of ephemeral motion.  However, if you are triggering recording, you may miss some of the initial motion in your recording.  To compensate for that, you may use the "include pre-trigger images" option on the Record tab.

2.38

  • XVID bugs fixed in custom xvidcore.dll distribution

  • The camera Post page now allows both "post to a folder" and "post to an FTP server".  Previously, it was one or the other.

  • The Windows Media setup window now allows you to specify an audio stream offset value with a range +/- 8 seconds.  If your Windows Media audio recording or webcasting is out of sync with the video, this will allow you to tweak it.

2.37

  • XCast ActiveX control updated to use GDI+ drawing if DirectX is unable to obtain video memory surfaces.  This should eliminate drawing anomalies on remote viewing systems with lower-end video cards.

  • The XVID DLLs have been updated to version 1.2.2 with additional memory safety features enabled

  • The Trim/Export function now employs a worker thread to prevent UI "not responding" messages; the Cancel button should now also function during the operation

2.36

  • Serivce/Console communication now supports up to 2048x1536 resolution cameras to be previewed.  Also, a GUI bottleneck in drawing console camera images has been fixed.

  • Time formatting codes may now include the # character after the % to eliminate leading zeros

  • Integration of the Hikvision DS-40xx SDK to allow the DS-4000 8-port card to be used.  Obtain the Hikvision DLL from the blueirissoftware.com support/3rd party page and place it in your Blue Iris program folder.  A Hikvision device option will then appear on the Video tab when you add a new camera.

  • A new advanced option on the Motion profile page to force continuous recording when specific profiles are active according to the Schedule

  • The remote viewing of the "all cameras" stream now favors a wider display, 3x2 cameras will be shown instead of 2x3 for example

2.35

  • A single-click of the tray icon will now restore the UI window (was previously double-click)

  • Separate HTTP and RTSP/video ports may now be specified on the IP network camera configuration window.  Please check that these are set appropriately if your cameras use ports other than HTTP for streaming.

  • Much faster startup/shutdown times for systems with multiple cameras.

  • Camera startup/shutdown/resets no longer block the main UI thread, providing for a more responsive UI.

  • When running as a service with a second instance open as a console, video is now updated at a rate of 3fps overall, split between all cameras.  If you select a specific camera or bring it to full-screen, that single camera will receive all 3fps of video updates.  De-select all cameras by clicking anywhere in the video window but outside of a specific camera's window in order to once again update all windows.

2.34

  • Web server code modified to allow up to 1000 clips to be listed at a time remotely

  • An effort has been made to prevent false motion detector triggering as the result of signal loss/restoration

  • BVR playback speed now more accurately reflects the position of the playback speed control slider

  • Several potential bugs affecting the use of the "run as service" option have been repaired

  • Support for ACTi MJPEG cameras (requires firmware update)

2.33

  • An alternate phone# may be entered on the Telephone Alert page to be used in the case of Watchdog Timer alert.

  • For each motion sensor profile, you may choose to NOT trigger alerts when the motion sensor is triggered.  Used with the Schedule page, this allows you to specify times during the day during which to record on motion but not send alerts.

  • Several new IP cameras added

2.32.05

  • Fix to allow Microsoft LifeCams to properly set their resolution

  • The camera limit has been changed from 25 to 64.   Please be aware that Blue Iris will not prevent you from attempting to exceed your system's resources.  You should not operate your system at 100% CPU or HDD utilization for any extended period of time to ensure proper operation and UI responsiveness.

2.32.04

  • Fix for Panasonic BB-HCM311/71 and Panasonic KX-HCM110 ADPCM audio decoding.  If there are other G.726/ADPCM cameras which also have audio-clarity issues in Blue Iris, please bring this to my attention, foscam@foscam.es

2.32.02

  • When the interface reappears after having been minimized, previously an old video frame may have been visible until a new frame is drawn

  • The motion detector may have been activated if the software was started during a period where the schedule should have de-activated it

2.32.01

  • The email alert JPEG attachment should now be guaranteed to contain a frame which caused the motion sensor to trigger.  Previously, Blue Iris used the current frame from the camera at the time of the actual email.

  • A new DDE command, "global" with item "signal" ... send "0" to set red traffic signal, "1" green and "2" yellow.

  • Several new IP cameras now supported

2.32.00

  • Tested and working with Windows 7

  • Several new IP cameras now supported

  • Removal of the "Run Blue Iris automatically when you login to Windows" option from the Startup options page.  This feature only worked with XP, or when UAC was disabled, which is not recommended.  The correct way to run Blue Iris at startup is to either use the Service option (advanced users), or to use the Windows Task Scheduler (Start/Administrative Tools) to create a task (do not use the Basic option) to automatically run Blue Iris with highest privileges at login, startup, or a specific time of the day.

  • On the Startup options page, a new option to "Prevent power management from turning off the display" has been added.  In 2.31.11, this behavior was added to the "prevent screensaver" option, which caused some confusion.

  • The "prevent suspend" option has been renamed to "Prevent power management from putting the PC to sleep"

  • When running as a service, the recording path and red camera borders are now correctly displayed in the console

2.31.11

  • The Zavio D510 MPEG4 support now properly selects μ-law 64 kbps audio decoding

  • Avermedia support has been tweaked

  • The "prevent suspend mode" and "prevent screensaver" system options may now work more reliably on newer Vista/7

2.31.10

  • Handling of status messages when running as a server has been vastly improved, and the stat window now has a Refresh button instead of the previous (and continuous) auto-refresh

  • Support for the Mobotix M22

  • If a file cannot be moved from New to Storage due to a sharing violation error, the move will now be retried.  Previously, the file may have been left unmoved and an error logged if the system was simultaneously attempting to generate a preview image.

  • "Image Format Errors" coming from JPEG request cameras have been suppressed; the request is simply automatically retried.

  • Selecting "Close application" from the System Tray's popup menu will now always close the application.  After version 2.31.09, it would first minimize the application, then close only when used again.

  • Minimize and Options menu items added to the System Tray popup menu.

2.31.09

  • Fixes to MPEG4/RTSP to allow G.711 uLaw audio to function

  • Lorex LNE3003, AirLive WL-2000CAM, Zavio F312a RTSP support with G.711 μLaw audio

  • Fix to allow Windows Media features to properly function in demo mode

  • The X close button will now do a minimize if you have the "minimize to system tray" option enabled.  To shut-down the app, use either Alt+F4 or right-click the icon in the system tray.

2.31.07

  • Support for Win2K may be restored with this version as I have removed use of the CLinkCtrl control

  • The property page dialogs now use an alternate (better) method for resizing and setting fonts

  • The bitrate setting for Windows Media webcasting and recording now uses kpbs instead of bps

  • Fonts are now drawn with Cleartype where applicable

  • Support for Digicom W100

  • Support for LevelOne WCS-2040, and LevelOne PTZ

  • Support for Aviosys IP9100a

  • I have been asked to provide more granularity and detail on this page, and I will try to provide this

2.31

  • The Browser button now opens an external browser rather than a built-in browser.  Some instability was noted in IE8 when handling JAVA applets.  Rather than allow this to impact Blue Iris, it made sense to move this out of the main application for now.  The ActiveX control works with IE7/8, and the JAVA applet works with Safari and Firefox.

  • A bug was fixed with the handling of a display change as with a remote desktop connection

  • You may now choose whether to include images "inline" or as attachments when configuring an email alert

  • The de-interlacing feature now allows you to choose a new setting, "stretch top half" which fixes video coming from certain Vivotek models which apparently stream 2 images in a single frame in this way

  • Audio from the DLink 950G is now supported when using the video-port (5000 by default)

  • By (extremely) popular demand, the remote viewing HTML pages have been modified to allow the video to stretch to fit the browser window.  In addition, the clip list selection box will also stretch to fit.

  • The XCast ActiveX control has been updated to version 1,0,0,26 to fix an initialization error.

  • The Advanced Direct Show configuration window now allows you to specify an analog video standard.

2.30

  • By default, if a camera does not respond when the application starts or when you manually reset it, Blue Iris shows the error message in the video window, and you must manually reset the camera in order to reattempt a connection.  A new option on the Software Options page allows you to instead log these errors and force Blue Iris to automatically retry the connection according to the camera's Watchdog configuration.

  • The camera properties Timers page has been renamed the Schedule page.

  • The camera properties Video page has been revised to be easier to understand and navigate.  When adding or editing a Network IP camera, use the new Configure button.

  • The vertical and horizontal flip check boxes have been moved from the Network IP setup window to the Video page where they are now available for use with USB, Firewire, and Analog cameras as well as Network IP cameras.

  • The network timeout feature has been moved from the Network IP setup window to the new Watchdog page.  This new page allows you to trigger alerts when the camera signal is lost, and to automatically reset the camera on a periodic basis.

2.29

  • The Email alert now inserts the JPEG images "inline" into an HTML formatted email instead of as an attachment.  This may work better for certain clients which do not automatically display picture attachments.

  • The Run as Win32 Service feature now works properly when in Demo mode

  • Vivotek MPEG4/RTSP support has been tweaked to prevent malformed XVID frames from being decoded/displayed

  • The Push to Windows Media Server feature now checks for writing status errors once each minute and will attempt to reconnect the stream as necessary

  • If you have more than one camera, there's a new Auto-cycle camera view in full-screen video mode option to perform a "patrol" function.  To activate this feature, enable the option on the Software Options page, then go into full-screen video mode by either using the icon at the top-right of the Cameras window, or right-clicking anywhere in the Cameras window and selecting the Full-screen video command.  Finally, a camera must be selected to start the patrol.  Each camera will be selected and shown as a full-screen window in sequence.  If all cameras are unselected, or you select a camera with its own desktop window, the patrol is discontinued.  Use the Esc key to exit full-screen video.

  • The XCast ActiveX control is now version 1.00.24.  This version will automatically begin playback of a selected clip without the need to also press the play button.

  • The Viewer's right-mouse-click Save Snapshot function defaults to the New clips folder, but you may select another destination.

  • The full-screen video mode state is memorized and restored when the software is restarted

  • The "Open as desktop window" state of a camera is memorized and restored; the check box option for this has been removed from the camera properties page

  • Right-click video option to hide/show disabled cameras

2.28

  • The XCast ActiveX control is now version 1.00.23.  A possible performance impediment was identified and fixed.

  • This version handles XVID encoding for clips and webcasting via direct use of the xvidcore.dll.  There are many advantages to this, including reduced overhead, and the more direct control over XVID encoding configuration, thereby reducing the potential for user generated errors due to mis-configuration.  XVID is also now the default codec used for clips and webcasting.  Previously, MJPEG was used for clips by default, but this codec uses a large amount of hard disk space; MP42 was used for webcasting by default, but allowed for only a single viewer and was dated technology.

  • The XCast ActiveX control is now version 1.00.22.  It now includes xvidcore.dll in place of MP42, and also communicates directly with the DLL for maximum performance.

  • NOTE that although xvidcore.dll is now redistributed, in order to open XVID AVI format files in Windows, you must still install the full XVID package from www.xvid.org.

2.27

  • With 2.27.05, if your IP camera is sending frames faster than Blue Iris is expecting them, a warning will be posted to the Stats page, as this condition may have a negative impact upon system performance.  Once this warning is posted, Blue Iris will impose "wait states" on the camera's streaming thread, which may lead to a full receive buffer, which as a result may cause the image or PTZ commands to appear delayed, and possibly out of sync with audio.  You should correct the condition by properly setting the framerate in your camera to match the Blue Iris setting if possible.

  • A bottleneck has been removed which may have prevented some IP cameras from achieving their full framerate potential.  However, you should still set the framerate in your camera to match the framerate that you set in Blue Iris.

2.26

  • Fixed camera property Import/Export buttons to import/export all camera data

  • Added support for ACTi 1402, 4200

  • Fixes to account for bugs in the ALinking MPEG4 streaming

  • The viewer's rate slider now increases logarithmically to allow for quicker playback speeds in BVR files

  • Each camera's Play Live Audio setting now persists through resets and software restarts if you are not using the global feature to automatically play audio from the selected camera

  • Toshiba 11a support has been updated

  • The unnecessary and confusing option to use a custom JPEG webcasting port has been removed.

  • The Windows Media Push webcasting option now allows you to specify a user and password if your WM server requires it

  • The Vivotek MPEG4/RTSP driver now supports video-only cameras, and also now supports G726 audio decoding

  • An updated iphone.htm allows users with iphones to click on the image to switch cameras and then click again to get back to the index image

  • A new software option allows you to automatically listen to audio on the currently selected camera in a multiple-camera system

  • The "auto restore window" option on the Motion page now correctly only restores the window on triggering, not just any motion

  • Protecting/un-protecting clips no longer closes the clip viewer

  • It is no longer possible to delete protected clips; you must first un-protect them

  • The demo version now allows multiple cameras

2.25

  • A modified cell.htm page for optimal iPhone viewing has been added, iphone.htm  Thanks to Dwayne the Cam It! forum administrator and member jamiepyoung.  Previously, if Blue Iris detected an iPhone, he was taken to "jpegpull.htm" instead of "default.htm."

  • An attempt to increase speed optimization after moving to a new compiler VS2008 in version 2.21.

  • Support for BSTI PTZ commands

  • Support for the DLink DCS-3410 MPEG4 camera

  • Support for the ABS MegaCam via RTSP

  • Fix to allow PTZ commands to cameras with usernames but blank passwords

  • Fix for DSC-2120 using the port 554 RTSP option

  • Fix for the Toshiba IK-WB02A request path

  • Happy New Year!

2.24

  • PTZ controls added to the JAVA remote pages

  • A new DDE command 'trigger' can be used to externally trigger the motion sensor.  The sensor will remain triggered as long as a new 'trigger' command arrives before the motion sensor's "break time."

  • The camera PTZ page now allows you to reverse the orientation of the up/down and/or left/right controls for cameras mounted upside-down or mirrored.

  • Support for many new IP cameras, and added audio support for others

2.23

  • When using the Record "Every x min for y sec" option, Blue Iris now will align the recording times if the period evenly divides a day.  For example, if you select to record every 15 minutes, recordings will occur on the hour, and :15, :30 and :45 minutes past the hour.  Previously, the first recording would have occurred 15 minutes after camera initialization.

  • The Record snapshot "one image every x min" feature is also aligned if possible.

  • If you have more than 1 fixed hard drive volume, you may have to re-enter your license code; my apologies for this inconvenience.  This fixes a bug where removable hard drives were being used for a systems metrics calculation.

  • Support for many new IP cameras

2.22

  • Support for many new IP cameras

  • HTML formatting fixes for the default web pages so that they properly display on a wider collection of browsers

  • Bug fix: viewing the index image (all cameras) online while it was being resized (due to enabling/disabling cameras) would result in a crash

  • The ActiveX control has been updated to version 1,0,0,21.  Its digital signature has been extended 2 years (now expiring 10/2010), and there is a new optional parameter bHideUI, which when set to "TRUE" will hide the camera/file title and PTZ toolbar.

  • An attempt is made by the web server to identify mobile device connections and forward them to the appropriate default page; iPhones using Safari to jpegpull.htm, others to cell.htm.

  • Fix for streaming from some cameras (including Y-Cam) in 320x240 resolution

  • You may resize posted images to any arbitrary size.  Leave the Size box at (default) in order to use the same size as the images captured by the camera.

  • The Text overlay dialog now includes selection boxes for standard date/time formatting codes.

  • The Snapshot tool in the Viewer now allows you to pull a JPEG image out of a movie, which may be more convenient than using the clipboard and pasting the image into Paint or a Word document.

2.21

  • The FPS (frames per second) readout on the camera's status page now uses timing information from the most recent 60 frames instead of simply dividing total frames by total time.  The result is a more instantaneous and therefore more meaningful statistic.

  • The system "tray" icon will animate to show a 4-directional arrow when motion is detected, and will show an eye when someone is remotely viewing video

  • Remotely viewing clips will maintain the "connected" status for an IP address on the Index tab of the Stats window

  • Support for the Genius IP camera

  • Bug fix to allow text/graphic overlays to be re-imported using the Import button on the camera properties page

  • There are now options to completely automate the update process, found on the Options page.  Updates are now downloaded in a worker thread, and progress is shown in the status bar at the bottom of the window.

  • This version has been compiled using the latest development tools and SDKs available from Microsoft in an effort to maximize security and availability.

  • The Windows Media components now are distributed in the full install package to eliminate the need to maintain two updates.

  • The software update process has become more automated; it is now a one-click procedure.

2.20

  • The camera Record page now has the option to break recordings at specific file sizes measured in tenths of a GB.  The default is 4.5GB, the approximate amount of data which can be written to a DVD-R.

  • Support for the Planet 510 and Vivotek 7138 cameras

  • Fix to better support the Vitamin Decoder control by preventing it from blocking the main UI

  • Fixes to better handle low-memory conditions in most cases

  • A new page will be added to the blueirissoftware.com in the Support section to link to required 3rd party software, including an updated XVID dll in an attempt to make it more reliable

  • Fix for using security-enabled UNC volumes (servers with paths beginning \\) as clip storage

  • Support for Pixora and Viliar cameras

  • The viewer's Trim/Export feature can now create WMV files instead of AVI files (full version only).

  • Clicking on the video window no longer stops a manual record; you must either use the Record icon or right click and select Stop from the popup menu.

  • Two new DDE commands "recstart" and "recstop" to use instead of the "record" command.  This allows you to assert the manual record state rather than to toggle it.

  • An Invert tool button has been added to the Motion Mask Edit window

  • The first five PTZ preset positions may now be selected via the ActiveX remote view

2.19

  • Cameras using the Vitamin Decoder and audio now correctly select between 8k and 16k audio sample frequency

  • A larger buffer is allocated to accommodate high MPJEG compression quality settings; previously a crash was possible with a quality setting of higher than 95

  • An option has been added to the Software Options page to force the use of GDI (Windows graphics) and system memory (RAM) instead of DirectX and video memory when rendering live camera images.  On certain systems, this may be required for compatibility with dual-monitors for example.

  • Support for the new 2MP Intellinet 550468 using the video port (possibly 8081 or 40001)

  • A 1 second pause before continuous recording begins in order to allow you to cycle the "traffic signal" icon without creating a file and to allow XVID to provide an image to avoid empty frames.

  • DLink 950/g support has been updated to allow newer versions of the firmware to use the "DLink 950/1110 video port" driver option, which has been found to be more stable than the "web port" option.

  • Support for the Ganz 785, 787, etc. video servers

  • For time zone correction in a text overlay, add the special sequence {+n} to the beginning of the string, where n is a number 1-23, and the sign is either + or -.  For example, a text overlay of {+3}%c will display the time 3 hours ahead of local time.

  • The camera Record page contains a new option for Continuous recording.  You may also specify an alternate recording frame rate if you wish to record at a lower frame rate.  IMPORTANT NOTE: you should revisit the Record for each camera to insure proper settings using the new options.

  • When you record video without audio at a frame rate of less than 2fps, the playback frame rate is now forced to 2fps.  The effect is a "time lapse" where video will playback faster than real time.

2.18

  • Windows Media webcasting has been modified to flush the write buffer after all users disconnect, making reconnection smoother and more reliable

  • Advanced users can specify a full or absolute path for a camera's record filename in order to record a specific camera's clips to a specific folder.

  • Two new DDE commands added, "record" and "snapshot" to allow control of these features from external applications.

  • Bug fix: if recording failed to start due to a path or disc error, it was possible to cause the application to hang.

  • Changes have been made to prevent network timeouts for IP cameras and to allow the system to better recover from these timeouts when they do occur.  The minimum auto-reset time has been increased to 20 seconds.

  • The Clip Viewer attempts always to retain keyboard focus while viewing clips.  This allows you to use the up/down arrows and Enter to move between clips.  Previously, some recording formats prevented this behavior.

  • By default, the Spacebar may be used to pause/play video in the viewer, and the left/right arrow keys may be used to step forward and backward.  If you are updating, and had previously set keyboard shortcuts, it may be necessary to manually add these new commands to the keyboard shortcut page.

  • You may now specify multiple recipients for the email alert--separate each recipient address with a semicolon (;).

  • For analog cameras and USB webcams, it is now possible to maintain separate Video Proc-Amp settings (the qualities of an incoming video signal, such as brightness, contrast, hue, saturation, gamma, and sharpness) for each of the motion profiles 1-7.  Using the camera's Timer page, this allows you to change these settings based on the time of day--at night you may wish to turn off color processing and increase contrast, for example.  On the camera's Video page, use the new Save button to make a snapshot of the current Proc-Amp settings for the selected profile.  Proc-Amp settings may be accessed via the Driver/Source button.

  • The maximum number of cameras has been increased to 25.  Please note that Blue Iris will not stop you from attempting to exceed the capabilities of your PC.  If your CPU runs at 100% utilization for an extended period of time, the user interface may become unresponsive and data may be lost or corrupted.  See the troubleshooting section for help with lowering your CPU utilization.

2.17

  • Bug fix: playback of XVID in AVI files

  • Support for 1600x1200 resolution on the Axis 223m

  • Support for the Vidotek VT7902 (VS2000) using 704x480 resolution

  • Double-clicking the mouse button in the camera window now performs a full-screen video function.  Double-click a camera window to open a single camera in full-screen mode.  Double-click in the black space surrounding a camera window to open the entire camera layout window in full-screen mode.  Double-click again or use the Esc key to exit the full-screen mode.

  • You may specify a "position#" for each camera.  This number will be used to order the camera windows without the interface.  Previously, this was done alphabetically by camera name.

  • You may specify the number of connection attempts for the phone alert.  For non-voice modems, or modems without call progress detection (detection of rings, busy, etc.) it makes sense to specify a single connection attempt.

  • Support for the AirLink 650W video and PTZ

  • Bug fix: double-clicking on empty clip list may result in a crash

  • Bug fix: MP42 would not save custom configuration

  • Increased buffer size for MJPEG cameras to allow for hi-res images as from the Axis 209MFD

  • Support for Y-cam Black MJPEG

  • Support for Sony SNC-M1 MJPEG

  • A new option for the post-processing of clips that have been archived via FTP.  You may choose to leave the files, store them, recycle them, or delete them.

2.16

  • Support for the DLink DCS-1110

  • Support for the Toshiba IK-WB11A

  • The email alert now works with ports other than 25 for SSL (a bug was fixed)

  • Connections to the Index stream (multiple camera view) now correctly illuminate the "eye" icon and appear on the Stats window

  • If you use the Vitamin Decoder for your DLink, 4XEM or Vivotek camera, please install the updated version 2.1 from http://blueirissoftware.com/VitaminDecoder21.exe.

  • Support for audio from the DLink DCS-2000, as well as any DLink camera that uses the Vitamin Decoder version 2.1.

  • Support for the Vitamin Decoder 2.1 Auto-Detect Server function which should allow any new DLink or Vivotek camera based on this technology to operate.  You will find a new IP camera device type "DLink Vitamin Decoder Auto-Detect" for this purpose.

  • Support for G.711 audio from the Axis 207w camera

  • Fix for DLink PTZ

  • Support for the Fitivision 100a camera

  • Support for the Zonet ZVC7630 with audio

  • Play live audio feed from a camera that's capturing audio.  To enable this feature, right-click on the camera window; additional user interface controls will be added shortly.

2.15

  • Support for the GT-NC-160 IP camera

  • Support for Y-Cam G.726 audio

  • The motion detector now uses the ratio of moving pixels to "unmasked" pixels (instead of total pixels) when computing a percentage of moving pixels

  • The motion detector "overlay motion map" now shows blue where there is motion, white where there is masked motion, but leaves the video signal otherwise (previously, this was blacked-out).

  • The motion detector edit-mask window now allows the user to draw rectangles rather than "paint" with a cursor.

  • The motion detector edit-mask window is larger, and periodically is updated with a live image

  • Cameras remember their "maximized" status when shown in top-level (desktop) windows

2.14

  • Revised DLink950/G HTTP support with an attempt at audio support

  • Inclusion of the previous cell.htm file, renamed cell1.htm which may have worked better with the IE mobile browser

  • DirectShow PTZ controls now work on the Blue Iris interface when running as a service

  • Support for the StarDot NetCams

  • Support for audio from the Panasonic BB-HCM511A, which transmits audio in 32kbps G.726 format in RTSP packets.

  • New SMTP email component which supports SSL/TLS (secure authentication) as required by some SMTP servers such as gmail.  The email test page now also sends the image attachment if the camera is running.  Email alerts now run in a separate thread so that the responsiveness of other alert types is not compromised.  You may now specify a scale value for images attached to email alerts.

  • New SMS text message alert.  This alert uses your outgoing email server to send a message to your cell phone carrier's SMS gateway address.  You may use this alert type separately or together with email alerts.

2.13

  • New cell.htm for mobile devices that supports multiple cameras including the Index.  Also, the image is automatically scaled by Blue Iris (not the browser) to the device's full browser window width.  The Opera browser appears to work well here.

  • Support for the Gadspot GS9211 video

  • Support for the Gadspot GS9603 video and PTZ

  • Support for the BSTI PD100 network camera

  • A "full screen" video mode which automatically maximizes the Blue Iris window and sets the cameras window to occupy the full screen.  Right-click on the video window to find this option.  You can right-click again or use the Escape key to return to normal.  As previously, if you want to enter "full screen" video mode for an individual camera, you can right-click the video window and select "Open in desktop window" and then right-click that window to Maximize it.

  • ASF-stream cameras like the Linksys WVC in MPEG4 mode now use a new reader object which should be easier on your system resources (virtual memory).

2.12

  • The web server has changed to handle varying host addresses (names for your computer) more compliantly.  It is no longer necessary to specify a single server name.  Also, Blue Iris provides a list of all of your LAN IP addresses for reference purposes, as you may have more than one if you have multiple network cards.  You should use IPCONFIG from the command prompt to view your networking settings.

  • New arguments to the /image/cam-short-name method for retrieving images from Blue Iris for use on mobile devices, etc.  Use "s" for scale, "q" for quality, "h" for height and "w" for width.  You need specify only one of scale (in percentage), height, or width.

  • New DDE commands.  Use topic="camera" and item=the camera's short-name.  Send one of "reset", "enable", or "disable" in the data field.

  • Support for the Airlink101 SkyIPCam 250W

  • Support for D-Link DCS-2120 RTSP video

  • Support for the Av-tech avi201/202 MPEG4 camera using a tunneled RTSP protocol

  • Support for the LinkSys WVC200's MJPEG mode and PTZ controls

  • Repairs made to Vivotek and NC1600 PTZ controls

2.11

  • Support for the Sony SNC-DF70N MPEG4 camera

  • Enhanced support for audio capture from devices such as the CamGuard USB TV! Pro.  On the camera's Audio tab, select "DirectShow camera."

  • When a camera is not enabled for webcasting, it will no longer appear on the list of cameras in the remote view.  In addition, any clips which have been recorded with the same "short name" as the non-webcasting camera will not appear in the list of clips for remote viewing.

  • On the camera alerts page, you may now specify a "disarm time" in seconds.  This will delay an alert in order to allow you time to disarm Blue Iris, for example to prevent an alert following entering your own home.

  • The "auto-restore window when motion is detected" feature has been moved to the Motion sensor page for each camera.

  • On the startup options page, you now have the option to override the default behavior of not displaying video during remote terminal sessions.

2.10

  • Support for the Y-Cam IP camera

  • IP camera device options for all Intellinet camera models

  • On the Record tab, you can now include dynamic-date components as part of a custom-folder for clips.  For example, adding %Y%m%d\ to the beginning of the path will create a new folder for each day.

  • It is now possible to create multiple cameras from the same DirectShow input pin or IP camera in order to "split" a single signal into multiple copies for different processing, such as different graphic overlays and FTP post websites.

  • If you logoff or shutdown before closing Blue Iris, Blue Iris will now properly close files and connections to avoid corrupt video files.

  • A new option on the Post page to "Preserve Time Order."  This option will always upload the latest image to become camname_000.jpg and rename all others in the queue so that they are always in newest-to-oldest order.  Performance warning: this option will invoke ringsize-1 number of FTP rename operations after each upload.

  • Image files that are overlaid on the video are no longer "locked" for writing and may be dynamically updated

  • Disabled cameras are now excluded from the All Cameras view remotely

  • Extremely large clip folders (those containing thousands of clips) are now handled much more efficiently by the clip list and associated threads.

  • After a network camera stops communicating, and then after 2 unsuccessful "network timeout auto-resets" a full camera-reset will be attempted.  Motion detection is now disabled for 10 seconds following a network auto-reset.

2.09

  • JAVA/JPEG remote viewing now works with the JVM 1.4 or newer, and specifically has been tested and is working with the Safari browser on the Mac.

  • In addition to JPEG video overlays, you may now use GIF, PNG and BMP file types.

  • Startup and Shutdown files are now correctly copied to the destination folder when you use the "post files to a folder" option on the camera's post page.

  • When using the Trim function, the new default filename retains the original filename (with an appended counter) as well as the file system's "date modified" and attributes values.

  • Support for the Edimax IC-1500 network camera.

  • Bug fix: editing the motion sensor mask when running as a service

  • New clips saved within sub-folders now also appear on the remote file view

  • The Web Server now distinguishes between LAN connections and Internet connections.  When a user on the LAN connects to the server, the Blue Iris LAN address is used on web pages instead of the external IP or hostname.  This fixes an issue where PCs on the LAN are incapable of properly resolving your router's external IP address.

  • After two unsuccessful network camera timeout/restarts, a full camera object reset is attempted.

  • Support for the Gadspot GS200 added.

  • A watchdog timer has been added to the Blue Iris Service application.  If the main application closes unexpectedly for any reason other than a service-stop request, it will be automatically restarted.

  • AVI or WMV videos open for writing (locked) will no longer appear in the list of clips during remote viewing since they cannot be opened for viewing.

  • You may choose to keep a text file log of all messages written to your Stats Window by checking a box on that window.  In addition, all remote-view camera connections are now written to the stats window, so if you are logging messages to your hard drive, you may now keep a permanent record of these connections as well.

  • The PTZ (Pan/Tilt/Zoom) properties page now allows you to select "DirectShow camera control" as a protocol.  You are now able to control the mechanical Pan and Tilt on USB cameras such as the Logitech Orbit.

  • A new Macros option page allows you to set text that will be substituted for %1, %2, ... %9 in text overlays.  There are several ways that external applications can change these macro values dynamically: (1) write to the registry values directly, (2) use DDE to poke the value to the server "BlueIris" with topic "macro" with item "1" through "9", or (3) set the macro to a text file path that is externally updated.

2.08

  • For email alerts, you may now specify the body text, which may include hyperlinks.

  • A new option on the camera's image Post page allows you to post regardless of whether the camera is active according to the recording & alert timer.

  • A camera's PTZ commands are now available from the context (right-click) menu, which is especially handy when you are viewing the camera in a desktop window.

  • PTZ commands may now be given keyboard shortcuts.

  • When a camera is being viewed in its own desktop window, it now operates more autonomously: the main interface icons no longer control the camera window; clicking on the camera window does not unselect the camera in the main window; keyboard shortcuts may now be used in a desktop camera window when one has the focus (you have clicked on it).

  • You may right-click a desktop camera window and select to "Keep window on top" so that it is not obscured by other windows.

  • When the camera's Timer is not enabled, motion profile 1 is used all day.

  • The JPEG Refresh page ("jpegpull") has been reworked in order to allow multiple camera access and to open and view clips

  • The JAVA/JPEG page and its Applet have been reworked to to allow you to open and view clips

  • The JAVA/JPEG and JPEG Refresh pages have been tested and are working on the Mozilla Firefox browser

  • In addition to the disk quotas you specify, Blue Iris also attempts to automatically enforce a rule of maintaining at least 1GB free on the hard drive in order to prevent failed recordings.

2.07

  • Now by default, the MP42 codec only compresses key frames.  This restores the behavior from earlier versions of Blue Iris, which may have been more stable on some configurations.  You may experiment with turning this off, allowing MP42 to do inter-frame compression and run more efficiently, by un-checking the new checkbox on the movie format page for the camera.  If you receive a system error, turn this option back on, or consider using another codec, MJPG or XVID.

  • Due to popular demand, the number of pre-trigger images that you may request has been increased to 50 on the camera properties Record page.  Please be aware that use of this feature consumes memory equal to 4 bytes for each image pixel, and will cause your CPU utilization to spike to 100% when recording begins as the software catches up with compressing and recording these images all at once.

  • The XVID library is now also used to decode video from the popular DLink 950/G.  If you are using one of these cameras, please install the XVID codec from xvid.org.  Blue Iris no longer references DIVX or 3ivx for any purpose.

  • XVID support appears to have become more stable with the use of direct library calls in the code in place of Video-for-Windows calls.  Very rare decoding glitches are still observed under stress conditions, however, and I will work with the XVID development team in an effort to solve this, as I believe this codec is ideal for this application to replace the older and unsupported MP42 codec.

  • Support for the Gadspot 4000 and 4600 IP cameras with MPEG4 streams.  Requirements are that XVID is installed (xvid.org) and the camera is using the newer firmware (no "new prediction" in the video stream).

  • The motion sensor now attempts to discriminate between real motion and "scene changes" (perhaps the camera has switched from day to night mode).

2.06

  • The motion sensor now supports seven profiles.  Each profile consists of a completely separate configuration for the motion sensor.  That is, each profile may have its own sensitivity and other settings.  The particular profile that is active at any given time is determined by settings on the camera's Propiedades de la cámara - Timer page.  This feature allows you to implement a different motion sensor configuration based on the time of day and the day of the week. 

  • It appears that Microsoft has applied patches to its implementation of Video for Windows on Vista, so the AVI file format is once again supported in Blue Iris for Vista users.  Before using AVI with Blue Iris on Vista, please make sure you have applied all of the latest updates and patches to Vista.

  • You now have much more control over the video compression used by the ActiveX control for webcasting.  New controls have been added to the Web Server options page to configure the video codec.  If you have the XVID codec installed on your system (available from www.xvid.org) you may use this in place of the default MP42 codec.  The XVID codec may be more stable for multi-viewer scenarios, whereas the MP42 codec will be limited to a single viewer at a time.

  • You now have much more control over the video compression used for recording clips.  You may choose to use XVID, MP42  or the default MJPG.  However, at this time, the only recommended codec for recording is MJPG due to issues with recording from multiple cameras simultaneously using either of the 2 other codecs (XVID occasionally creates corrupt frames, sometimes crashing the de-compressor when clips are replayed, and MP42, which sometimes crashes during compression of multiple streams).  It remains, however, that if you are recording a non-standard video size (such as 360x240 or 640x400, etc), MJPG may not be able to handle that.  XVID may, however, be a viable option if you are recording from a single camera, or may work better under XP than Vista, etc., so you should experiment with your particular configuration to determine which codec will work best for you.

  • When recording clips in either MP42 or XVID format, you may select the keyframe interval, which allows for inter-frame compression, greatly reducing the size of your recorded files.  For the previous MP42 behavior (every frame is a keyframe) use '0' as the keyframe setting.  Because inter-frame compression greatly reduces the amount of hard-disk space required to record video, I will continue to search for a better choice for compression to replace MP42 and XVID.

  • Disabled and un-initialized cameras no longer appear on the camera list on the web server's home page.

2.05

  • Support for the Intellinet 550260/550277 Speed Dome cameras

  • Emailed image attachments are now marked as content-type image/jpeg so that they will properly on more email clients

  • Support for the Toshiba Ik-15A/21A PTZ controls

  • Support for the NC800 network camera

  • A bug has been fixed which had caused Blue Iris to shutdown after a number of image posts.

  • Now by default, when you open a clip in the clip viewer, it will automatically begin to play.  You can turn this off, and also turn off the automatic looping feature from the Software Options page.

  • Additional features added to the default.htm page to cause the clip list to be refreshed manually, as well as automatically each 30 seconds.  Controls also have been added to this page to allow you to navigate a large list of clips by skipping ahead in the list a day at a time.

  • If a remote terminal session is detected, live video will not be drawn to the Blue Iris window to prevent the remote terminal session from becoming unresponsive.

  • Support for the Panasonic PTZ controls

  • Some USB webcams occasionally fail to initialize the first time; an automatic re-try has been implemented

  • The JAVA "push" code has been recompiled to be compatible with the latest Sun JAVA runtime.  If you use this webcasting method, please install the latest Sun JAVA runtime from sun.com.  The "jpegpush.htm" page now directly references the Sun object to insure compatibility on IE.  A "conditional comment" has been added to the jpegpush.htm page in order to use an APPLET tag on other browsers/platforms.

  • Support for GadSpot/NC 1200 and 1600 audio streams.  For other cameras, you now may manually specify the appropriate URL for the audio, and whether the data is 8 or 16 bit.  As of this release, only 8KHz PCM audio data is supported.

2.04

  • Support for the Toshiba PTZ commands

  • Support for the new DLink DCS-950 interface

  • You now have the option of not using temp files for FTP image posting and archiving.  Sites like photobucket.com do not allow the necessary remove/rename commands necessary to upload to a temp file.

  • A bug was fixed to allow the use of the MJPG codec at 100% quality.

  • The Web Server now distinguishes between admin and non-admin users when you enable authentication.  Only admin users may use the "snapshot" icon remotely.

  • Moving forward, more admin control will be added to the remote interface.  With this version, when you right-click on the video window, the stat window that previously opened now has a section for admin users to change the status of the Traffic Signal icon.

  • The PTZ controls on the remote interface now are disabled for cameras that don't support PTZ.

  • New behavior: the Traffic Signal toolbar button no longer affects webcasting.

2.03

  • Support for the Plustek, Aviosys, and new Swann IP cameras

  • Support for the Observer Veo Observer cameras has been added, including PTZ functionality

  • If you have a 4-port BT8x8 card, use of the "Blue Iris low-level BT8x8" driver has been deprecated, and may soon be unsupported completely.  Please instead use the universal BT8x8 driver available from btwincap.sourceforge.net.  This is a highly stable and easy-to-install solution for supporting the hundreds of BT8x8-based cards available on the market today.  Blue Iris now allows you to add multiple cameras using the same Conexant DirectShow driver, each with a different input selection.

  • You may now choose to use an MJPG codec instead of the MP42 codec for video recording.  It is recommended that you obtain the demo version of the Mainconcept Codec from http://www.mainconcept.com/site/.  This is a highly efficient codec for compressing standard video sizes.

2.02

  • Support for Intellinet's MPEG4 cameras, such as the 550253.  You must have an XVID codec installed, which is available from Intellinet.

  • Additional IP cameras listed for support

  • A new help page for troubleshooting Internet and other common support questions.

  • A new screen-capture technology is introduced using a freeware component by Unreal Streaming Technologies (http://www.umediaserver.net).  This component allows for full frame-size and high frame-rates.  It also renders the current cursor.  If you are upgrading from a previous 2.x version, you will find this component in your Blue Iris program folder, and you can register it by using Start/Run and entering REGSVR32 "c:\program files\Blue Iris\UScreenCapture.ax".  You may still choose to use the older technology, "DirectDraw Blit."

  • The AVI file format has been disabled as a recording format on Windows Vista.  You may still export to the AVI format from the BVR format by using the clip Trim feature (move the green and red triangles and right-click).

  • AVI files are automatically limited to 1GB (operating system limitation) while recording.

2.01

  • Numerous enhancements for Windows Vista compatibility.

  • A new stream entitled "All cameras" is available for remote viewing if you have more than 1 camera.

  • All passwords stored in the registry are no longer in plaintext--they are encoded to prevent casual discovery.  NOTE: if you have previously entered FTP upload, window restore  or web page passwords, you must re-enter them in order to properly encode them for this version.

  • The phone alert will now auto-redial each 30 seconds for a total of 10 tries before failing.

2.00.09

  • PTZ support for the Intellinet 550710 and Vivotek PZ6112/6122.

  • The XCast OCX has been updated to version 1.0.0.11.  If you are serving custom pages using this control, you may need to update those.  Changes have been made to allow Blue Iris and the control to work with more routers on port 80 (the standard HTTP port).

  • With a router you may now specify a different "public port" from your "local port" by including the "public port" in your server name on the web server configuration page.  For example, you may set your server name to something like "myip.dyndns.org:82" where 82 is your router's public port.

  • If you are using an IP camera which uses the VitaminDecoder OCX (DLink DCS-2000/2100 DCS-3220, TV-IP301W, 4XEM), it is recommended that you update that control to version 2.1.

2.00

  • An all-new user interface design

  • A Blue Iris DVR video file format registered on your system as extension ".bvr" with a Blue Iris logo icon.  This new format allows very fast simultaneous read/write access with file sizes limited only by your available hard drive space.  With this format, you may now open a clip in the viewer that is also open for recording.  Also gone is the 1GB limit that AVI files have.

  • Clip folders.  In addition to the previous Current (now known as New) and Archive (now known as Stored) folders, you may now organize your clips with subfolders.

  • Clip protection.  You may mark clips as read-only, preventing then from being automatically deleted.  You may also protect entire folders.

  • Web archival.  You may mark clips manually or automatically for archival to your website via FTP.

  • PTZ (pan-tilt-zoom) camera support.  Currently, the Axis 213/214 PTZ protocol is supported.  This protocol provides relative and absolute positioning and zooming as well as the use of preset names.  Others will be added as requested.

  • The image posting feature now allows you to scale the image to sizes appropriate for cell-phone viewing.

You may also review the version 1.x update list.