Depth_minimum_distance being capped to 3.0m in ZED SDK

Software
,
1

I have a pair of ZED X Ones GS wide with a baseline of 1.5m

image
image615×364 15.9 KB

Based on this, the minimum depth would be a bit over 3m and I want to set it to 4m as I don’t really care about depth up close to the cameras.

Currently the ZED SDK enforces a hard cap on the value of init_parameters.depth_minimum_distance to 3 meters. This would make sense on X, X mini and 2i but seems restrictive for X Ones with higher baselines. When I try to set it to 4.0m, I get the following warning:

[2025-03-18 00:03:15 UTC][ZED][WARNING] [Init]  Requested depth_minimum_distance: 4METER is too far, clamped to 3.0000002METER.

The API also mentions the same hard cap here.

Is there a particular reason for this? Can it be bypassed? Or is there no benefit to changing it to 4m from the compute perspective.

The Maximum Distance is also capped in the ZED_Depth_Viewer to 50.0m. Can we expect a fix at any point to with the limit updated to 200m+?

2

Hello @auc7us, welcome on StereoLabs forum !

Thank you for contacting us. You are correct that we currently do not allow setting depth_minimum_distance above 3m due to stereo camera use cases.
We understand your need to adjust the minimum and maximum depth distances to accommodate a higher baseline with monocular cameras. While this feature is not available at the moment, it is on our roadmap. We are working on enhancing the SDK and our tools for monocular setups. In the meantime, we recommend using the maximum values for these parameters and applying a post-filter depth adjustment tailored to your application.

Best regards,