The ZED SDK allows you to add depth, motion sensing and spatial AI to your application. Available as a standalone installer, it includes applications, tools and sample projects with source code.
This release of the ZED SDK is now a stable release of the major version 4. It brings significant stability and performance improvements. We're introducing a new generation of the Positional Tracking module for more precise and robust localization. A new version of SVO is also available, recording full sensor data and supporting custom user data for ease of use.
Sep 10, 2024
LOSSLESS modes performances and robustness to corruption while using less memory. SVO repair uses less memory. Resolved reading problems on Windows, as well as SVO real time mode. ZED SVO Editor had multiple issues solved (merge, cut).Jul 16, 2024
Camera::open() function can now fail to reflect the NEURAL depth status.zed_media_server_cli.service from the ZED Media Server.May 24, 2024
May 7, 2024
CAMERA_NOT_INITIALIZED errors occurred randomly.GNSS_RTK_FIX reporting errors that incorrectly displayed GNSS DATA NEED FIX.enableRecording function now returns an ERROR_CODE due to the absence of a hardware encoder on this platform. A software fallback will be introduced in a future release.Apr 3, 2024
PositionalTrackingParameters::mode = POSITIONAL_TRACKING_MODE::GEN2. It outputs more robust and precise trajectories compared to GEN1, leveraging IMU data at full frequency for better motion estimation. This version requires the new SVO2 data. A new warning ERROR_CODE::SENSORS_DATA_REQUIRED has been introduced to inform about missing high-frequency data when using the module. The state enum has been reworked for clarity on the module status; ODOMETRY_STATUS, SPATIAL_MEMORY_STATUS, and POSITIONAL_TRACKING_FUSION_STATUS are now available. It's accessible using the new struct PositionalTrackingStatus.Camera::ingestDataIntoSVO alongside a new struct SVOData.The data can then be retrieved when opening the file using Camera::retrieveSVOData. Each data stream is associated with a string key, the data points are associated with a timestamp to replay synchronously if needed. Camera::getSVODataKeys retrieves all custom data stream keys present in the current SVO2 file. This format is mandatory to use the new Positional Tracking Gen2 with IMU data for best accuracy. The older format can still be recorded by setting the environment variable ZED_SDK_SVO_VERSION to 1.NEURAL+ mode providing higher quality than Neural with sharper edges and more accurate depth, though requiring more computation.NEURAL mode accuracy and confidence. This new model is more accurate with no runtime difference. The confidence has been reworked for accurate edges and minimized flying pixels. It also improves confidence estimation in challenging areas such as sky, hard illuminations, very close objects, etc., to remove false depth measurements reliably. Neural modes from previous versions can be accessed on demand.MODULE enum, with defaults applying to all modules. Functions Camera::setRegionOfInterest and Camera::getRegionOfInterest can be used to set the ROI. Auto-detection mode can find the static part of the image automatically by moving the camera for some time. It can be enabled using Camera::startRegionOfInterestAutoDetection, with RegionOfInterestParameters for adjusting detection parameters.retrieveMeasure, the user-defined UNIT was not applied.fp16 execution without hardware support, leading to poor performance compared to fp32.resetPositionalTracking function.get_device_list function when no cameras were detected.For older releases and changelog, see the ZED SDK release archive.