Change log of version 2.2.14.12

Changelog for 2.2.14, since 2.2.14.11

  • [2041] AccVimaccInterface: Fixed a deadlock that could freeze the application when an ONVIF camera was shut down while background ONVIF requests were still initializing. In this situation, pending requests were not cancelled reliably, causing the main thread to wait indefinitely. The issue was more likely to occur during frequent camera start/stop cycles, such as with on-demand streaming.

Changelog for 2.2.14, since 2.2.14.10

Minor updates were added to increase stability and ensure version allignment.

Changelog for 2.2.14, since 2.2.14.9

[2010] Updated SQLite DB to v3.50.4

Changelog for 2.2.14, since 2.2.14.8

  • [2003] AccVimaccPlaybackProxy: Added compatibility with vimaccOA.
  • [2006] AccVimaccDumDb:
    • Fixed license injection failures caused by temporary file errors ("QFSFileEngine::open: No filename specified" log messages.) - which causing issues during nightly scans by Windows Defender.
    • Fixed potential crash.
  • [2007] AccVimaccDumpDb: Fixed warning log message "QCoreApplication::postEvent: Unexpected null receiver".

Changelog for 2.2.14, since 2.2.14.7

  • [1864] General refinements to the codebase for improved product support.
  • [1948] AccVimaccWorkstation/Video clients: Fixed H.265 playback: H.265 GOPs were decoded twice. Besides high CPU consumption, this caused slightly choppy playback.
  • [1949] AccVimaccWorkstation/Video clients: Fixed H.264/H.265 playback: Choppy playback with B-frames is now resolved for closed GOPs.
  • [1953] AccVimaccWorkstation: Fixed a crash that occurred when suspending streams in video dialogs outside the selected video grid layout. This issue was introduced in version 2.2.14.4.
  • [1954] AccVimaccInterface: Fixed a crash in ONVIF when pull-point subscription was enabled, occurring after the 'CreatePullPointSubscription' request failed for any reason.
  • [1998] Added support for AXIS VAPIX ClearView lens cleaning.

    Supported syntax for camera's command/request node in vimaccConfig:

    • "cmd=clean;info" — retrieve ClearView service info as JSON. For older devices, this info is static and may be inaccurate.
    • "cmd=clean" — trigger the first/default cleaning service.
    • "cmd=clean[;type=][;duration=<seconds>]" — optionally specify service type and duration; see "info" output for available types.
    • "cmd=clean;status" — retrieve ClearView status as JSON. Not applicable to devices using the legacy PTZ/auxiliary API.
  • [1962] Adding required parameters to Debian packages for official Docker support.
  • [1958] AccVimaccWorkstation: Fixed virtual PTZ with hardware joystick if Layout/useDefaultLayout=true setting in AccVimaccWorkstation.conf.
  • [1963] AccVimaccWorkstation: Added functionality to suspend stream decoding when a vimacc Workstation connects to the Display Server for remote control.

Changelog for 2.2.14, since 2.2.14.6

  • [1881] Optimized the Export Dialog window handling to ensure better support for displays with low resolutions, such as those with a height of 768 pixels.
  • [1883] The "Multiperson-Login" checkbox in the Login dialog is now always displayed but will only be enabled when applicable. Previously, the checkbox was hidden unless a user other than 'vimacc' was authenticated.
  • [1889] Several stability improvements for the "Stream Cloning" feature.
  • [1895] WS: Fix: Ensure a pending video stream connection is closed when clearing a video dialog.
  • [1864] General refinements to the codebase for improved product support.
  • [1902] AccVimaccInterface: Fix: Resolved an issue where WS/video clients failed to decode video after a network interruption (e.g., interrupt logo or blue screen). This was caused by automatic SDP generation for BOSCH cameras when SPS/PPS was received in-band before the SDP via RTSP.
  • [1906] SSL: Enhancement: Enabled setting of Server Name Indication (SNI) to address issues where some servers reject SSL connections during the handshake if SNI is not provided.
  • [1907] WS: Fix Qt warning occurring on live stream connect if no DNNPlugin installed.

    Warning: QObject::connect(AccVimaccStreaming::FrameFlowOperator, AccVimaccPlayerToolbox::VideoWidget): invalid nullptr parameter
  • [1910] AccVimaccHttpServerVca:

    • fixed error with expired EBUES license
    • returning JSON data in case of error
  • [1887] Demo licenses updated for Q1/2025.
  • [1888] The default SSL certificate for the vimacc HTTP server has been renewed.
  • [1864] General refinements to the codebase for improved product support.

Changelog for 2.2.14, since 2.2.14.5

  • [1864] General refinements to the codebase for improved product support.
  • [1865] Fixing crash of AccVimaccWorkstation on user logout, if user feature "Navigation/Tabs/Protections" enabled and the video grid containing at least one playback.

    Versions affected: 2.2.10.34-2.2.10.40, 2.2.13.1-2.2.13.8, 2.2.14.1-2.2.14.5

  • [1866] Fix of ONVIF implementation regarding dispatching of events, that have no tt:Source tag. This effects for example the LIDAR devices of "Blickfeld".
  • [1868] Fixing an issue where dongle encrypted streams hat not been decrypted correctly in Workstation/Display, in case of a restart of the AccVimaccInterface.
  • [1864] General refinements to the codebase for improved product support.
  • [1867] Improved startup performance of vimacc Workstation by reducing code complexity from unused feature implementations.
  • [1871] Resolved an issue with the "Layout Sensitive Bandwidth Management" feature where switching streams displayed the full camera name, including its path, instead of a truncated name. This occurred despite the VideoPanelOptions/useTruncatedStreamNames=true setting in AccVimaccWorkstation.conf.
  • [1872] Updated the setup process to support reading values for the command-line parameters "-IntfCount" and "-ServerCount" from the registry:

    • HKEY_LOCAL_MACHINE\SOFTWARE\Accellence\vimacc\General\InterfaceCount (String)
    • HKEY_LOCAL_MACHINE\SOFTWARE\Accellence\vimacc\General\ServerCount (String)

    When using these command-line parameters, their values are automatically stored in the registry for future use (e.g. when installing an update).