vimacc OA - Release Notes

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”).

Additional information regarding feature “Stream cloning”

The feature of “Stream cloning” (introduced in 2.2.10.30) needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

New Features (compared to 2.2.10.36)

• none

Changelog (compared to 2.2.10.36)

Video-EWO:

• Fixing memory leak in stream decryption, resulting in high memory usage over time (mostly seen by often changing stream connections, like using sequences).
• Deactivating any ffmpeg messages to stdout, stderr (which are flooding PVSS logs).

vimacc-Core

• Update of QT libraries to 5.15.12, issued by memory leaks in the event handling of the framework, effecting mostly AccVimaccInterface.
• o Fixing memory leak in stream decryption, resulting in high memory usage over time (mostly seen by often changing stream connections, like using sequences) in AccVimaccWorkstation and AccVimaccDisplay.

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”).

Additional information regarding feature “Stream cloning”

The feature of “Stream cloning” (introduced in 2.2.10.30) needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

New Features (compared to 2.2.10.35)

• none

Changelog (compared to 2.2.10.35)

VideoManager & Ctrl-Libraries:

• Fixing issues with GridLayout changes in Scenarios.
• Fix state handling. When an interface process restarts, no more data point changes are received.
• Fixing camera state handling, when recording servers is unavailable.
• Fixing state handling. Mark all objects to be synced if full update requested.
• Correction to handle Deletion of DIST Cameras correctly, so that they disappear correctly in vimacc Workstation.
• Fixing crash when deleting VideoObjects.

vimacc-Core

• Fixing several issues in AccVimaccInterface for the provisioning of playback timelines (used in WinCC OA VIDEO through the VideoManager).

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”).

Additional information regarding feature “Stream cloning”

The feature of “Stream cloning” (introduced in 2.2.10.30) needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

New Features (compared to 2.2.10.33)

• none

Changelog (compared to 2.2.10.33)

VideoManager & Ctrl-Libraries:

• Fixing issues with hiding members from base class in VO_Scenario and VO_Sequence.

• Fix handling with object.device.name, regarding the used Display names in vimacc Workstation.

• Fixing several stability and performance issues regarding the Display-DIST functionality.

vimacc-Core

• Fixing some protocol issues with several ONVIF Devices, cause by different WSDL-Version.
• Update of OpenSSL to 1.1.1v
• Correction of version info for FFMPEG to 4.2.9 in vimacc About-Dialogs. FFMPEG-Version was updated in release 2.2.10.33.
• Bosch implementation in AccVimaccInterface: FIXED stuck communication, potential crashes & ASSERT messages in log.
• AccVimaccInterface: Fixing several crashes, when many device connections getting broken and having several retries.
• Session handling: Fixing several issues with internal timers, which results in leaked objects, causing high CPU load in AccVimaccInterface.
• Fixing issues in AccVimaccInterface for the provisioning of playback timelines (used in WinCC OA VIDEO through the VideoManager), reseting state when connection to AccVimaccServer is closed. Otherwise, session was not re-established and timeline info was no longer updated.
• AccVimaccCommander: implemented support for disabling feature checks via OTP (One-Time-Password) useful during remote support
  1. Run AccVimaccCommander on the customer computer outside the Accellence AD domain and double click on the Accellence logo in the top right corner to open the SUPUS dialog.
  2. Run AccVimaccCommander on any computer that is member of the Accellence AD domain, double click on the Accellence logo in the top right corner, enter the SUPUS Challenge Code shown on the customer computer.
  3. On the customer computer, enter the SUPUS Response Code shown on the Accellence computer in order to disable the feature checks.

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”).

Additional information regarding feature “Stream cloning”

The feature of “Stream cloning” (introduced in 2.2.10.30) needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

New Features (compared to 2.2.10.33)

• none

Changelog (compared to 2.2.10.33)

vimacc-Core

• Fixing some protocol issues with several ONVIF Devices, cause by different WSDL-Version.
• Update of OpenSSL to 1.1.1v
• Correction of version info for FFMPEG to 4.2.9 in vimacc About-Dialogs. FFMPEG-Version was updated in release 2.2.10.33.
• Bosch implementation in AccVimaccInterface: FIXED stuck communication, potential crashes & ASSERT messages in log.
• AccVimaccInterface: Fixing several crashes, when many device connections getting broken and having several retries.
• Session handling: Fixing several issues with internal timers, which results in leaked objects, causing high CPU load in AccVimaccInterface.
• Fixing issues in AccVimaccInterface for the provisioning of playback timelines (used in WinCC OA VIDEO through the VideoManager), reseting state when connection to AccVimaccServer is closed. Otherwise, session was not re-established and timeline info was no longer updated.
• AccVimaccCommander: implemented support for disabling feature checks via OTP (One-Time-Password) useful during remote support
  1. Run AccVimaccCommander on the customer computer outside the Accellence AD domain and double click on the Accellence logo in the top right corner to open the SUPUS dialog.
  2. Run AccVimaccCommander on any computer that is member of the Accellence AD domain, double click on the Accellence logo in the top right corner, enter the SUPUS Challenge Code shown on the customer computer.
  3. On the customer computer, enter the SUPUS Response Code shown on the Accellence computer in order to disable the feature checks.

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”).

Additional information regarding feature “Stream cloning”

The feature of “Stream cloning” (introduced in 2.2.10.30) needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

Changelog (compared to 2.2.10.30)

VideoOA EWO

• Fixed "leaking FrameBuffers" and "Flooding main thread with FrameBuffers" in vimaccAPI, which occures when using the RTSP streaming feature of the VideoEWO.
• Fixing digital zoom with mouse wheel for video panel items.

VideoManager

• Fixing some minor issues with Scenario and Sequences of type “VMS.
• Adding support for defaultRecording params, needed for orphaned ring adjustments.
• Adding support for general device events under "<DEVICE>/events" like AccVimaccWorkstation or ONVIF-Events. Supports only event values triggered after connection of the VideoManager. Deleted values in the vimacc Config are getting kept on the WinCC OA datapoint.
• Adding support for ONVIF-Event activation, using the additional parameters "pullpointsubscription" or "eventsubscription".

vimacc-Core:

• Linux-Setups: Changing the install parameters of vimaccOA services, to improve start up handling. With old settings it happens, that the active Config Master degrades and the system switches in undefined behavior.
  • From: After=network.target
  • To:
    • After=network-online.target
    • Wants=network-online.target
• Fixing unimproved handling of background images in vimacc Workstation and vimacc Display, which impact to the decoding performance. Background images could be reenabled now in projects, where they has been disabled caused by this issue.
• Update of FFMPEG to version 4.2.9
• Fixed special handling in case of full decoder queue if RTP marker bit is not set on IDR FU-A End packet as observed with Bosch VIP X1 XF IVA encoder (fw ver. 28500572). Otherwise, no more data was passed to the decoder, effectively freezing the image.
• Fixing an issue of the RTSP session handling, where SETUP response might not have been processed because of premature state change.
• Fixing an issue of the RTSP session handling, where the selection of predefined trackID or codec name did not work.
• Some general improvements of the internal memory handling.

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”).

Additional information regarding new feature “Stream cloning”

The new feature of “Stream cloning” needs an update of the internal feature lists in vimaccOA. Please contact support for further guidance for activation of this feature.

New Features (compared to 2.2.10.29)

Introducing new feature of "Stream cloning", to be used on 2nd or 3rd video stream of a camera, to clone another stream of the same camera, internally in WinCC OA VIDEO.

Use case is for example, circumstances where it's better to receive only one stream from the source, but it's also needed to record it in two different ways.

LINUX: SecurityWizard Console-Mode (-c), no needs any longer for xhost-Mapping to root user. This is the default now in linux setups, which makes deployments to these systems much easier.

Changelog (compared to 2.2.10.29)

• VideoOA EWO

Fixed "leaking FrameBuffers" and "Flooding main thread with FrameBuffers" in vimaccAPI, which occures when using the RTSP streaming feature of the VideoEWO.

• VideoManager
  • Support for Parameter "ws_nonpresentstate", which allows to display cameras in the vimacc Workstation as "nonpresent", when the corresponding interface processes are offline (default "error").
  • Fixing scenarios for "VMS client", to generate the ID in vimacc without the ".link" part of the WinCC OA Datapoint.
  • Fixing scenarios for “VMS client”, to adopt them correct also if the lists only contain one entry.

Introducing new stream parameter "clone", to be used on 2nd or 3rd video stream of a camera, to clone another stream of the same camera, internally in WinCC OA VIDEO. Use case is for example, circumstances where it's better to receive only one stream from the source, but it's also needed to record it in two different ways.

Fixing Display-Dist support to create the cameras in vimaccOA without the dist name as prefix.

• vimacc-Core:
  • Adding functionality to use vimacc streams as source for streaming instances, e.g. to duplicate video streams in the vimacc interface, e.g. for use cases where it's better to receive only one stream from source, but it's also neede to record in two different ways.
  • SecurityWizard Console-Mode (-c), no needs any longer for xhost-Mapping to root user. This is also used in the linux setups.

Fixing mislead internal handling of controller definitions, which results in bad behavior during determination of the preffered controller for any instances.

This could result in the situation, that also with only one configured controller, no instance is requesting the mutex to get up and running.

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.

VideoOAEwo

VideoManager

• Fixing handling for camera recording state, when recording is disconnected.
• Improved maintenance mode handling for Camera and Encoder, to avoid error states for devices in maintenance mode.
• Fixing issues with stream from Bosch cameras, cause of wrong payload type.
• Fixing "unknown encryption state" on Linux.
• Fixing improper state for disabled StreamingProxys.
• Fixing missing stream infos for cameras with several streams, when using StreamingProxy.
• Adding support to provide host monitoring data like CPU-Utilisation, RAM-Usage & Partition-Usage.

HidCtrl

• Improved handling of Joystick events for PTZ Movement (Axis T8311).
• Several stability improvements.

vimacc Core

• Adding advanced host monitoring, based on CPU-Utilisation, RAM-Usage & Partition-Usage. This feature is configurable by the "AccVimaccSystemMonitor.conf".
• Fixing leaking socket instances, which could cause plenty of misbehaviors like left AccVimaccDisplayServer processes behind.
• Optimization in http protocol implementation of streaming interface, reducing subsequent authentication requests.
• Fixing handling of wrong states for camera streams.
• Several improvements in RTSP protocol implementation to advance compatibility.
• Fixing wrong states for DisplayServer, if dialogs are empty.
• Fixing failing "no VSYNC" detection for Bosch encoders with more then one input.
• Fixing wrong error states for Bosch devices.

VideoOAEwo

• Adding support for frameDecoderTick-Events, for alive monitoring of video decoding in VideoWidget.

VideoManager

• Fixing to only use one recording as target, while configuration of failover-recording with equal hosts.
• Adding support for Maintenance-Mode.
• Adding support for new host-Logic in vimacc for the stream info, instead of using the controller.

vimacc-Core

• Under Linux Adding "max open files" limit to 100000 to avoid "too many open files" errors. Add LimitNOFILE=100000 entry to AccVimaccService*.service.
• Fixing to install admin tools, add AccVimaccSign to all options.
• FIXED "cmd=show" config request command ignored the "overridecolor" parameter.
  • Example: Show "Autobahn 1" live stream on panel 1 with override color frame ("blue" by default)
  • ActiveDeviceList/ws_workstation_0001/command/request = cmd=show;source=cam_demostreams_autobahn1_0001;videodlg=VD1;overridecolor=true

• Adding support to push login credentials to AccVimaccPlayback by command line.

  This is usable, when vimacc is running integrated into a central management system, with extended Export handling and PasswordStore-Manegement, e.g. in Traffic Control Centers

  • - where the Credentials for the exports are management by the GDPR-Manager and any export is done to a central NAS
  • - the operators are not allowed to know the credentials for the export, but should review them, as long as they are placed within the central system. For this the operators has play buttons on the export list, which starts the ExportPlayer, with right credentials from the Passwort-Store.
• Fixing leaking socket instances, which cause misbehaviors, like left behind AccVimaccWorkstation instances (visible in TaskManager only)