NEW SOFTWARE RELEASE ==================== Application: AXIS Video Motion Detection (VMD) Release date: 2018-10-29 Release type: Production Software version: 4.3.2 Preceding Release: 4.2.5 Onvif support: Motion Alarm Event Motion Region Configuration -------------------------------------------------------------------------------- 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 Instructions ==================== In the product's web interface, go to the Applications menu. Remove any old versions of the AXIS VMD ACAP running, then upload and start the new one. Note: 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. New Features in 4.3.2 since 4.2.5 ================================= F01: Adds support for Onvif Profile T configuration of Motion Region Configuration Dependencies ============ Properties.API.HTTP.Version=3 Properties.EmbeddedDevelopment.Version=2.13 Required 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 cameras 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.