Change log of version 2.2.10.29

Upgrade information from installations earlier then 2.2.10.26

Based on the project experiences over the last decade, the internal runtime database of vimaccOA (named “vimacc Config”) has been general re-engineered for better runtime performance and system stability – also results in an overall improvement of the redundancy features of vimaccOA.

Reworking the IPC protocols of the “vimacc Config” harms, first time ever, the compatible with earlier versions of vimaccOA - NOT the compatible with any version of WinCC OA.

Cause of this any upgrade of distributed vimaccOA installations, from versions earlier then 2.2.10.26, needs additional plannings to keep operations without any general downtime.

Please contact the WinCC OA VIDEO experts you trust for further information and support (keyword “vimacc ConfigNG”).

New Features (compared to 2.2.7.9)

  • Config Segmentation to reduce network load

  • allows to definition of dedicated subscription to specific Config values, e.g. to bring only the really required information to a ConfigSlave/ConfigProxy node connected by limited data connections (like LTE or satellite)

  • Video Export: added support for (unencrypted) export to AVI, MKV & mpeg4

  • Adding support for transmission of “Configuration Presets” (scenarios) and sequences from WinCC OA VIDEO to vimaccOA (for usage in vimaccOA Workstation).

  • DIST support for vimaccOA DisplayServer & Workstation

  • vimaccOA DisplayServer & Workstation:

  • support for custom dialog names in grid layouts (e.g. additional naming “alarmd” of video dialog “VD1”)

  • support of display all configured camera streams, instead of only stream 1 (needs parameter “General/ShowAllLiveStreams” in AccVimaccGui.conf)

Changelog (compared to 2.2.7.9)

  • VideoOAEWO

    • Adding natively sequences support, with command “showSequence”, incl. support for PTZ presets

  • VideoOACtrl

    • Axis HID devices (JoyStick, JogDial, KeyPad): adding support for hardware revision V2

  • VideoManager

    • optimize state handling for video exports

    • Adding support for new export commands, for “transcoding” (export into AVI, MKV & mpeg4).

    • clear all host states to pending during startup phase of vimaccOA

  • vimacc-Core

    • ConfigNG: reworking of the vimaccOA runtime database – see upgrade warning above

    • Database for Features & License, improvements for replication, i.e. used for Config-Slaves nodes

  • SystemMonitor several improvements

    • for better system health monitoring, e.g. performance indicators (like cpu usage, memory load, etc.)

    • fixing wrong RAM usage with high load on disk drivers under linux, which claims most memory as write/read cache

    • fixing of neverending "PENDING" state in case of RC1/RC2

    • fixing state detection of DisplayServer / Workstations

  • UI rework of vimacc Workstation & DisplayServer for better 4k support.

  • Improvement of digest authentication in HTTP client (e.g. used for control connections to cameras). Adding support for RFC2617 for compatibility with RFC2069.

  • Bosch integration: fis for hanging “no rtp” states

  • Bosch integration: improve “signal lost” events, for streaming channels >1

  • VPT/ENEO protocol implementation: fixing address byte mapping

  • Several improvements in the RTSP client implementation for better compatibility to video sources.

  • Adding new loglevel “info” for all vimaccOA processes.

  • Fixing handling of wrong devices state nodes when streaming proxy is used.

  • Fixing incompatible states for DisplayServers for empty dialogs, which results in wrong values in WinCC OA VIDEO.

  • Adding internal performance counters including logging config latency indicators to CSV for remote support.

  • Adding command “switchrelais” for VAPIX devices, as used for any IO-Devices in vimaccOA

  • Playback Player: adding AboutDialog

  • Fixing several soft-leaks [QTBUG-88248]

  • Improvements for requesting playback frames, while sliding on the timeline.

  • Adding optional timeline precaching in AccVimaccServer, to improve playback performance in bigger systems.

  • Fixing leaks in AccVimaccInterface

  • Fixing crashes of AccVimaccInterfaceProxy

  • Fixing crashes of AccVimaccServer

  • Fixing crahes in vimaccOA DisplayServer & Workstation, if a requested grid layout does not exists.

  • Fix of setups issues, resulting in “need to repair” of VCRedists, experienced after installation of vimaccOA.

  • ONVIF implementation: fixing namespace issues, which results in not working ONVIF commands, e.g. for PTZ

  • RTSP-Server

    • disable auto merging of timelines, when requesting playback for a camera with several streams.

    • configurable by AccVimaccRTSPServer.conf:

      “PlaybackOptions/MergePriorities=none”

    • Improvements for RTSP playback commands (as defined in RFC) and adding advanced support for URL parameters, like:

      • setting of initial playback position

      • setting time range for playback

      • define mergefilters, etc.

    • Fixing playback issues, in case of redundant recording for streams.

  • AccVimaccInterface

    • improve support for multinetwork and multi VLAN installations (conf file parameters "IpInterfaceOperatorNet" & "IpInterfaceDeviceNet")

  • Fixing wrong “STATISTICS::DECODER: session stream time diff” messages in logfiles of AccVimaccInterface.

  • vimaccOA Workstation

    • fixing playback issues with blue pictures, while playback several streams with different timelines

  • vimaccOA DisplayServer & Workstation

    • added the new "showoverlaytext" command for setting video dialog overlay in vimaccWorkstation

      Syntax: "cmd=showoverlaytext;contextid=<text>;dest=<destinationID>;videodlg=<number>;text=<text>[;fontsize=<pt-size>][;textcolor=<QColor-name>][;backgroundcolor=<QColor-name>][;xpos=<x-percent>|left|center|right][;ypos=<y-percent>|top|center|bottom][;timeout=<ms>][;overlayid=<id>]".

    • Adding support to vimaccOA HTTP-Server for virtual data folders, read from a standard TAR or a “VMTT” (a tuned tar format for OpenStreetMap compliant Geo-Map tiles). Taking this into accounts, it’s possible to host own OSM-TileServer locally.