Version 4.6.3 System Version 4.6.3 includes the following components: Avigilon VIEW Version 4.6.3 R-Series Version 4.6.3 Rialto Version 4.6.3 ICVR-HD Version 3.7.1 ICVR-SD Version 2.6.3 System Requirements for Avigilon VIEW Windows XP Professional (Service Pack 3) Windows 7 Windows 8 Minimum: CPU - 2 GHz, Core2 Duo 2 GB system memory 100 GB free disk space Recommended: CPU - 2.4 GHz, Quad Core 4 GB system memory 400 GB free disk space
IP Camera Compatibility Requirements (attaching an IP camera to a Rialto I4 or an R-Series IP Blade) 1. H.264 compression (High, Main or Baseline Profiles) a. MJPEG and MPEG4 video streams are NOT supported 2. RTSP streaming protocol 3. One of the following resolutions: 1920 x 1080 1920 x 1072 1280 x 1024 1280 x 720 800 x 600 or lower Notes for first time users 1. When logging in to Avigilon View for the first time use the following credentials: Username: supervisor Password: supervisor 2. A user does not need to be a system administrator to run Avigilon VIEW. However, to install Avigilon VIEW, the user must be a system administrator. 3. Arecont multi-head IP 1080P/720P cameras are not supported for attachment to a Rialto I4 or R- Series device. In addition, all other Arecont models have not been verified for attachment to Avigilon devices. New Features introduced in System Version 4.6.3 1. Consolidation of FLIR and non-flir images There is now only one firmware image for FLIR (thermal) and non-flir modes. Previously, a separate firmware image was required for configuring a device to FLIR mode. This change applies to single channel encoders (2.6.3), IP and Analog Rialtos (4.6.3) and R-Series devices (4.6.3). 2. Additional Resolution Supported for IP Camera Attachment 1920 x 1072 is now supported Defects Resolved in System Version 4.6.3 1. VIEW allowed invalid Domain Name System (DNS) configuration settings. 2. Web UI - Auto-complete is disabled on all Web UI forms increased security. 3. Web UI Directories are not exposed through the Web interface increased security. 4. Rialto & R-Series Occasionally when a Rialto was connected to Avigilon Control Center, object bounding boxes were not displayed on the video.
5. VIEW If a leading 0 was used in an IP address octet (e.g. 192.168.086.101), when attaching a camera stream to an IP Rialto or R-Series blade, the attachment would fail. 6. R-Series The Network Attached Storage (NAS) device s time and date were not always correctly updated. 7. R-Series When replacing/swapping blades on a fully populated R-series (4 blades), the device would reboot and after the restart completed, the user would not be able to configure Common R-Series Settings. 8. IP Rialto and R-Series IP Blades ACTi IP camera video streams can now be attached to these devices 9. IP Rialto and R-Series IP Blades ACTi IP PTZ cameras can now be controlled (e.g. presets, zoom, etc.) by IP Rialto devices 10. Rialto & R-Series Occasionally when a Rialto was connected to Lenel s OnGuard System, video was not displayed. 11. Rialto & R-Series Audio talk down was not working with Genetec Security Center 5.2 SR6 New Features introduced in System Version 4.6.0 1. Additional Resolutions Supported for IP Camera Attachment Any resolution below 800 x 600 is now supported. 2. IP Camera Attachment: Three 720P (1280 x 720) Resolution Devices - Three 720P cameras can now be attached (simultaneously) to an IP Rialto or R-Series IP blade. 3. Extended Live View Opens Automatically Extended Live View will now open automatically if VIEW was closed with Extended Live View enabled Defects Resolved in System Version 4.6.0 1. VIEW had noticeably slower response times (in comparison to previous versions) when opening Live Video streams and editing rules. 2. ICVR SD, HD & Rialto When video retention was set to > 24 days, only 15 minutes of video was actually retained. 3. Rialto would occasionally generate alarms that were time stamped weeks into the future. 4. VIEW When backing up device settings to a file, VIEW would generate a warning message about changing device time. 5. ICVR HD & Rialto When an error occurred during transmission of an alarm clip to the cloud (Avigilon mobile events), a second attempt at transmission would not include the video clip. The event s video clip was therefore not available for playback.
6. IP Rialto & R-Series IP Blades Software upgrade introduced to reduce drops of attached camera streams to the IP Rialto devices. 7. IP Rialto & R-Series IP Blades When connecting an Avigilon PTZ IP camera to a Rialto device, VIEW control would result in erratic PTZ behavior. New Features introduced in System Version 4.5.0 1. Additional Resolutions Supported for IP Camera Attachment See list above identifying all resolutions supported as of version 4.5.0 (updated with system version 4.6.0). 2. IP PTZ Camera Control IP PTZ cameras can now be attached and controlled by Rialto I4 and R-Series IP blade devices. Two protocols are supported: (1) ONVIF and (2) Axis VAPIX. 3. Improved Video Streaming Video streaming across high latency / low bandwidth WANs has been improved. Previous video smearing should rarely occur. 4. Separate Alarm Inputs for HD Cameras Each of the 2 HD camera alarm inputs can now be used independent of the state of the other. Rule configuration options are: alarm input 1, alarm input 2 or Any. 5. RTSP Authentication on HD Cameras and Rialto Username and password authentication can now be configured for access to Real Time Streaming Protocol (RTSP) sessions on HD cameras, Rialto, and R-Series devices 6. Operator Force Login Privilege A supervisor can enable operator privilege to force login to a device that has reached the maximum connections allowed. This applies to SD, HD, Rialto and R- series devices. 7. Improved Video Analytics Processing Video analytics have been enhanced as follows: a. Improved detection in low contrast environments b. Enhanced overall sensitivity c. Automatic detection of day/night transition for icvr devices d. New algorithm for splitting close objects into separate objects improving detection of large objects Defects Resolved in System Version 4.5.0 1. RIALTO - Setting the Input Video Standard to PAL, did not set scaling/size to PAL mode. 2. RIALTO I4 - Rialto IP devices were dropping the video stream when attached to FLIR camera models FC-313-S and FC-324-S.
3. RIALTO - Occasionally, audio talk down would fail to work outside a firewall. Audio talk down would work on a LAN, but fail to work through a WAN. 4. ICVR HD Cameras and RIALTO Alarm clips originating from these devices could not be played by HTML5 browsers. Internet Explorer 10 and 11 and Firefox could not play alarm clips from HD cameras and Rialtos. 5. RIALTO I4 Rialto IP devices were rebooting when connected to a FLIR model F612 camera. 6. ICVR HD Cameras and RIALTO In high latency scenarios (e.g. satellite), the stream from HD cameras and Rialto devices would frequently drop and reconnect. 7. ICVR HD Cameras and RIALTO In high latency scenarios (> ~300ms), the stream from HD cameras and Rialto devices would often appear smeared. 8. VIEW An established camera disappeared from the VIEW camera tree and would only return after the PC was rebooted. 9. ICVR HD Cameras and RIALTO Quickly pressing the TALK button (in VIEW) multiple times, disabled audio talk down. 10. ICVR HD Cameras with Motorized Lens Motorized zoom control was reversed. The Zoom Out button would zoom in and vice versa. 11. RIALTO R-Series Occasionally an R-Series would not execute functions such as format HD, reboot, firmware upgrade, etc. 12. RIALTO Audio Talk down would fail when configured for HTTPS but worked with HTTP. 13. VIEW Did not always display the correct resolution for cameras attached to a Rialto I4. Resolution displayed on the Storage and Compression page was sometimes incorrect. 14. VIEW All folders disappeared (very rare) from the camera tree. Cameras remained in the tree. 15. VIEW Cameras dropped out of folders in the camera tree (very rare). Folders appeared empty and cameras were listed outside of the folder. 16. VIEW After initiating a video search in VIEW, a message was displayed indicating Out of Memory and no search results were listed. 17. VIEW In the Alarms list, the duration field contained 0, for all Device disconnected alarms. The field should contain the number of minutes and seconds that the device was disconnected. Functionality NOT enabled in R-Series and Rialto (as of version 4.6.3) 1. Monitored Object Missing rules 2. Archiving
Known Issues 1. Attaching an IP camera stream (to an IP Rialto or R Series IP blade) with dimensions that are not a multiple of four, will result in a continuous reboot cycle on the Rialto device. For example, attaching an 800 x 450 stream will initiate the problem. Resolution to this defect is currently in development. 2. Versions of VIEW, older than v4.3.0, can inadvertently disable all video channels and alarm notifications on Analog Rialto devices (RA4s) running firmware version 4.3.0 or greater. In this scenario, alarms on the Rialto devices will not be reported. Therefore it is critical to upgrade all workstations to VIEW version 4.4.1+, prior to upgrading the Rialto devices. If there are RA4 devices that have been disabled using View Version 4.2 re-enable the channels using these steps: a. Upgrade workstations to VIEW 4.4.1+ b. In View navigate to the Manage page c. Locate the Rialto A4 devices, double click on one of the cameras bringing up settings d. Navigate to the Encoder tab and check Enabled for each of the cameras. e. Press the OK button The RA4 cameras will now appear in the camera tree and report alarms. 3. Alarms that generate an email and provide an HTTPS link for the video clip, will not play with Internet Explorer and Windows Media Player. To work around this problem, either install QuickTime or switch to HTTP protocol. 4. When using the Teach By Example (TBE) function, alarms may be listed where the confidence level is below the threshold sensitivity configured in the associated rule. In this scenario, the listed confidence is incorrect. The alarm is valid the confidence level is not displayed correctly. 5. R-Series IP Blade and Rialto I4 If the unit is power cycled less than 5 minutes after a stream has been attached, all stream configuration information (for all streams on the device) is lost. Wait at least 5 minutes prior to removing power after attaching an IP camera. 6. When an R-Series is upgraded, VIEW reports that the process is complete, but a few additional minutes are required to finish the upgrade. The R-Series should not be power cycled until all upgraded R-Series blades are displayed as reconnected in VIEW s camera tree.
Web-browser access to Avigilon (VideoIQ) cameras and appliances Web-browser access to cameras and appliances, currently supports IE 8 through IE 11. Other browsers may work however certain notes apply: Google Chrome Chrome appears to support the Windows Media Player plug-in without any modifications. Firefox Firefox does not natively support ActiveX. An extension is available that provides basic support for ActiveX however this support is not sufficient for Windows Media Player. It is recommended that this extension be uninstalled to prevent it from being used. A plug-in for live streaming is available from VLC (VideoLan). This plug-in will not decode or render detection boxes even when enabled by the Preferences setting. Safari on MAC The VLC plug-in for live streaming is also available for Safari. The limitation on detection boxes applies here as well.