Release Notes for IDS peak 2.3


These release notes describe the changes in IDS peak 2.3. This release introduces the autofocus control for the uEye LE USB 3.1 AF Rev. 1.2 as well as performance improvements in the IDS peak IPL and the U3V Transport Layer. The host-based decimation and a dialog for simplified event control of cameras in the IDS peak Cockpit are also new.

IDS peak 2.3

New and changed functions

IDS peak Cockpit

The focus dialog in the IDS peak Cockpit was reworked and functions for controlling the active focus of the uEye LE USB 3.1 AF Rev. 1.2 were added. Additionally, you can now also set the ROI for autofocus directly in the focus dialog.

“Focus" dialog
“Focus" dialog

A new dialog for controlling camera events such as "ExposureStart" or "ExposureEnd" is available. Using this dialog, you can easily enable or disable the desired events. You can also generate a test and view the events that have occurred directly in the dialog below.

“Events” dialog
“Events” dialog

In the "Position and Size" dialog, you can now enable host-based decimation in addition to sensor or FPGA decimation (model-dependent). This function of the IDS peak IPL library is available for all camera models. For models with sensor or FPGA decimation ("region0"), model-specific decimation can be combined with host decimation.

“Position and size” dialog
“Position and size” dialog

You can now also set and control the color saturation in the "Color" dialog. This is also a function of the IDS peak IPL and is performed on the host side.

“Color" dialog
“Color" dialog

Additionally, a function has been integrated in the camera manager to reinstall the driver for IDS USB3 Vision cameras when they are connected to the transport layer of another manufacturer.

IDS peak comfortC

  • New functions have been added to control the active focus of the uEye LE USB 3.1 AF Rev. 1.2 as well as the autofocus of the uEye XC USB 3.
  • New functions to query and set the user-defined name of a camera: peak_Camera_UserDefinedName_Set and peak_Camera_UserDefinedName_Get. The user-defined names are managed via the DeviceUserID node for uEye+ cameras (GV and U3 models). For uEye cameras (UI models), the self-defined name is managed via the DeviceUserIDuEye node.
  • New function peak_Camera_ID_FromUserDefinedName to open a camera by its self-defined name.
  • Functions for controlling color saturation have been added to the host-based color correction via the IDS peak IPL: peak_IPL_ColorCorrection_Saturation_Get, peak_IPL_ColorCorrection_Saturation_Set, and peak_IPL_ColorCorrection_Saturation_GetRange.

IDS peak IPL

  • Within the color correction, functions for color saturation have been added.
  • Functions for host-based decimation have been added.
  • A sharpness implementation has been introduced that can be used to measure the sharpness of images.
  • The multi-threading support of the library has been extended to use it e.g. for sharpness measurement.
  • A new method has been introduced to read the timestamp (Image::Timestamp).
  • Performance improvements for debayering and color correction in 10- and 12-bit formats.

IDS peak AFL

The new IDS peak AFL library provides host-based automatic functions for IDS cameras such as the active focus control functions for the uEye LE USB 3.1 AF Rev. 1.2.

U3V Transport Layer

  • The performance under Linux has been significantly improved.
  • Two new modes have been added to the StreamBufferHandlingMode of the U3V Transport Layer. The first mode has the advantage that an image is not immediately discarded if the application memory is not available, but that the camera's internal memory (depending on the model) is active as a buffer. The second mode addresses experts as it allows to run an application with only a single image buffer.
  • New nodes have been added to StreamControl to control the mode of USB transfer requests.

uEye Transport Layer

It is now possible to query the timestamps of the uEye cameras (UI models) via the IDS peak comfortSDK or IDS peak genericSDK.

General improvements

  • Support for strongly-named assemblies in IDS peak.
    In the .NET framework, strong-named assemblies offer a number of advantages. Using a strong-named assembly creates a unique identity for the assembly and can avoid conflicts.

Known issues

  • If network adapters are added, removed, activated or deactivated after opening the IDS peak Cockpit, the changes are only visible after restarting the IDS peak Cockpit. Alternatively, you can manually update the list in the camera manager by clicking on the update button in the upper left corner.
  • LabVIEW does not support template functions as they are used for FindNode() for example (IDS peak genericSDK). As a workaround, all possible templates of FindNode, FindInvalidatedNode, FindInvalidatingNode, FindSelectedNode and FindSelectingNode are provided as separate functions in addition to the normal generic function.
  • If network adapters are added, removed, activated or deactivated after opening the IDS Vision Cockpit, the changes are only visible after restarting the IDS Vision Cockpit.
  • If multiple cameras are open in tiled view in IDS Vision Cockpit, no scroll bar is displayed at the bottom.


  • The IDS Vision Cockpit has been discontinued and is therefore no longer recommended for new applications. In this version, it will be distributed for the last time.
  • With the introduction of the IDS peak comfortC API, users of the IDS Software Suite can quickly and easily switch to IDS peak without having to learn a new programming methodology (e.g. GenICam). For this reason, the IDS sherpa migration guide is not being updated anymore. We recommend the use of the IDS peak comfortC API, which is part of IDS peak from version 2.0 on.

Status: 2022-12-14