NEW SOFTWARE RELEASE ==================== Application: AXIS Video Motion Detection (VMD) Release date: 2018-02-23 Release type: Production Software version: 4.2.1 Preceding Release: 4.2.0 ONVIF support: Motion Alarm Event -------------------------------------------------------------------------------- Contact Information =================== Please contact Axis Communications for product information, updates and support at www.axis.com -------------------------------------------------------------------------------- Compatible Products =================== See complete list of compatible products at www.axis.com Installation Instructions ========================= In the product's web interface, go to the Applications menu and install the corresponding application package. Start the application. For more instructions see the product's User Manual at www.axis.com Preferred browsers for the configuration web page are latest version of Google Chrome and Firefox. Upgrade from VMD 2 and 3 ======================== AXIS Video Motion Detection 4 does not replace AXIS Video Motion Detection 2 or 3 when installed. Unless AXIS Video Motion Detection 2 and 3 are removed manually, all applications will be available in the camera. Fixes in 4.2.1 since 4.2.0 ========================== F01: Added support for collection of usage data. F02: The API version stepped to 1.3 to reflect updated capabilities API. Fixes in 4.2.0 since 4.1.8 ========================== F01: Fixed an issue in which the application in rare cases could get unresponsive and impose a high CPU load on Ambarella S2L and Artpec 6 based products. F02: Made the MotionAlarm event the same as defined in ONVIF Imaging Spec 17.06. F03: Added an API for retrieving application configuration capabilities. The API version stepped to 1.2. F04: Miscellaneous GUI and usability improvements. Fixes in 4.1.8 since 4.1.6 ========================== F01: Added data-overview=1 to the client video parameters Note: 4.1.7 missing due to error in release procedure. Fixes in 4.1.6 since 4.1.5 ========================== F01: Fixed memory leak in cgi. F02: Support for Q8741 and Q8742 products. Fixes in 4.1.5 since 4.1.4 ========================== F01: Improved shutdown procedure. Fixes in 4.1.4 since 4.1.3 ========================== F01: A severe memory leak introduced in VMD 4.1.3 has been corrected. Fixes in 4.1.3 since 4.1.2 ========================== F01: The termination of the application sometimes caused a sigabort if it was done too soon after the application was started. Fixes in 4.1.2 since 4.1.1 ========================== F01: The application was sometimes not respawned in case of system failures. F02: Allow 20 points in include and exclude areas, since this was supported in 4.0.0 New Features in 4.1.0 since 4.0.2 ================================= F01: Added possibility to connect a VMD profile to a PTZ-preset. F02: Improved browser support. New Features in 4.0.0 since 3.2.1 ================================= F01: Better handling of moving background, which will decrease false alarms. F02: Does not restart application during configuration. F03: Auto-saves all changes of include and exclude areas. F04: Includes ONVIF-support. F05: Possible to test connected action rules by sending a test alarm event. F06: Possible to have different settings using profiles. F07: Possible to connect action rules to a certain profile or to an aggregated ANY trigger. F08: Improved performance for multi-channel products. Dependencies ============ Properties.API.HTTP.Version=3 Properties.EmbeddedDevelopment.Version=2.12 Required Firmware Version 6.40 or later Recommended Firmware Version 7.10 or later Known Bugs/Limitations ====================== L01: Objects moving straight towards the camera take longer time to be detected. L02: It is not possible to create an action rule connected to the VMD 3 trigger if both VMD 3 and VMD 4 both are running. Since both applications can produce this trigger. L03: In a Pan/Tilt/Zoom product the analytics engine is restarted with each change of preset position. Therefore, it is recommended to wait at least 10 seconds before changing preset position. L04: Enabling visual confirmation may introduce video latency and due to increased CPU-load may affect analytic behavior negatively. L05: The application is performance demanding and thus it is highly recommended to ensure that the camera is not exstensively loaded, especially when running other analytic applications at the same time. L06: It is not recommended to run AXIS Video Motion Detection at the same time as the cameras built-in motion detection or other Analytic ACAPs. This may impact behavior and performance of this application. L07: If the camera's capture mode is changed during setup, the camera must be restarted for visual confirmation to work correctly. L08: Visual confirmation in the configuration page requires that the browser can connect an rtsp-stream over websockets. This requires that the network / proxy settings does not stop this connection. Support for an rtsp-stream over websockets requires an updated browser. L09: Some products will trigger on objects behind privacy masks. To avoid this, exclude areas need to be added. L10: The "xinternal" event is an internal event used within the application. L11: Include/exclude areas that are behind other areas are selected by clicking the corresponding eye-icon. Application Developer Information ================================= See VAPIX AXIS Video Motion Detection API available from Axis Partner Pages www.axis.com/partner.