ZED_Depth_Viewer v4.2.3 - Corrupted data?

nfntn · January 14, 2025, 4:01pm

Hi,

I am trying to replay SVOs through the depth viewer. The SVO were obtained with v4.2.3 and the tools are running on v4.2.3.

I can easily visualize the images through the ZED_Explorer but I have no success with the ZED_Depth_Viewer.

It logs some error while opening my SVO files and the data seems corrupted:

in bool ImageHandler::initialize(sl::Mat&) : Err [999]: unknown error.
in bool ImageHandler::initialize(sl::Mat&) : Err [400]: invalid resource handle.
in bool ImageHandler::initialize(sl::Mat&) : Err [400]: invalid resource handle.
in bool ImageHandler::initialize(sl::Mat&) : Err [400]: invalid resource handle.
in bool ImageHandler::initialize(sl::Mat&) : Err [999]: unknown error.
in bool ImageHandler::initialize(sl::Mat&) : Err [400]: invalid resource handle.
in bool ImageHandler::initialize(sl::Mat&) : Err [400]: invalid resource handle.
in bool ImageHandler::initialize(sl::Mat&) : Err [400]: invalid resource handle.

Any idea on what could be the reason? We are running the tools through a nvidia-enabled docker image.

Best,
Noé

nfntn · January 14, 2025, 5:46pm

Digging a bit more into that. It seems to be an issue with the Depth Viewer, not the SVOs. Whether on 4.2 or 4.1, whether using a SVO or a live camera feed, the depth viewer is encountering the issue.

adujardin · January 15, 2025, 10:17am

This looks like a CUDA issue, if you’re using docker make sure all GPU features are enabled, like display acceleration, hardware decoding, etc (GitHub - stereolabs/zed-docker: Docker images for the ZED SDK).
You can test simpler configurations like a CUDA sample or a ZED SDK tutorial (without display) to narrow down the problematic part

nfntn · January 15, 2025, 1:41pm

Thanks for your answer. The docker image I am using is already GPU enabled with all NVIDIA drivers capabilities. It also mounts the standard files required for X forwarding.

Thanks for reminding me about the Dockerfile samples. I’ll give a try to run the tools through the official image and report back.

I see there are no gl Image for 4.2. Could you please confirm whether the devel image is compatible with the tools?

nfntn · January 15, 2025, 2:16pm

Also, to clarify, I can work with the cameras using the SDK with my docker image. The only executable that is failing is the ZED_Depth_viewer

nfntn · January 15, 2025, 2:21pm

The tools do not seem to be built into the recent devel docker images. They can’t be found under /usr/local/zed

nfntn · January 15, 2025, 10:06pm

For future users, setting Performance Mode in Nvidia Profile fixed the issue.

Myzhar · January 16, 2025, 12:14pm

This means that the AI models installed on your device are broken.
I recommend you run this command to clear them:
ZED_Diagnostic -aic

nfntn · January 16, 2025, 3:02pm

For future debugging, how could I reach this conclusion? Does the depth viewer interact differently with the models compared to the SDK?

The depth model was also working fine through the SDK.
I couldn’t display the images in the depth viewer, while they properly displayed in the explorer.

Myzhar · January 16, 2025, 5:39pm

No, normally if you face issues by using the NEURAL depth mode in ZED Depth Viewer you should expect to experience the same problem with other applications using the same depth mode.

In any case, your problem seems to be not related to depth mode, but to image rectification. Indeed, ZED Explorer, which does not display rectified images, worked correctly.
Did you perform some kind of manual calibration?

TZECHIN6 · July 6, 2026, 5:18pm

Hi, I am having exact same issue. Might I know how do you fix your problem?

I am running ubuntu 24 with CUDA 13.0. The depth model is reinstalled after running the ZED_Diagnostic -aic. And also set the Nvidia profile to max_perf, but nothing has changed.

```
thomasluk@cps-notebook-3

:

/usr/local/zed/tools

$ ./ZED_Depth_Viewer

[2026-07-06 18:01:24 UTC][ZED][INFO] Logging level INFO

[2026-07-06 18:01:25 UTC][ZED][INFO] Using USB input… Switched to default resolution HD720

[2026-07-06 18:01:26 UTC][ZED][INFO] [Init] Camera successfully opened.

[2026-07-06 18:01:26 UTC][ZED][INFO] [Init] Camera FW version: 1523

[2026-07-06 18:01:26 UTC][ZED][INFO] [Init] Video mode: HD720@30

[2026-07-06 18:01:26 UTC][ZED][INFO] [Init] Serial Number: S/N xxxxxxx

[2026-07-06 18:01:26 UTC][ZED][INFO] [Init] Depth mode selected: NEURAL. Ensure this mode matches your application’s performance and accuracy requirements. See Depth Modes | StereoLabs for help.

in void InputThreadModul::close() : Err [400]: invalid resource handle.
```

TZECHIN6 · July 8, 2026, 9:50am

Update

Used the pre-built docker image, and the result remain same. Error still existed and no depth image can be viewed using ZED Depth Viewer. This error also happened if I configure the processing setting in the GUI, e.g. setting the max depth value.

Command to run

docker pull stereolabs/zed:5.4-gl-devel-cuda12.8-ubuntu24.04

docker run -it --rm --runtime nvidia --gpus all --privileged -e DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v /dev:/dev -v /usr/local/zed/resources:/usr/local/zed/resources stereolabs/zed:5.4-gl-devel-cuda12.8-ubuntu24.04

```
./tools/ZED_Depth_Viewer
```

Console log

root@fb7e1950dcb1:/usr/local/zed# ./tools/ZED_Depth_Viewer
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
[2026-07-08 09:44:17 UTC][ZED][INFO] Logging level INFO
[2026-07-08 09:44:18 UTC][ZED][INFO] Using USB input... Switched to default resolution HD720
[2026-07-08 09:44:18 UTC][ZED][INFO] [Init]  Camera successfully opened.
[2026-07-08 09:44:18 UTC][ZED][INFO] [Init]  Camera FW version: 1523
[2026-07-08 09:44:18 UTC][ZED][INFO] [Init]  Video mode: HD720@30
[2026-07-08 09:44:18 UTC][ZED][INFO] [Init]  Serial Number: S/N 16517409
[2026-07-08 09:44:18 UTC][ZED][INFO] [Init]  Depth mode selected: NEURAL. Ensure this mode matches your application's performance and accuracy requirements. See https://www.stereolabs.com/docs/depth-sensing/depth-modes for help.
[2026-07-08 09:44:19 UTC][ZED][WARNING] [Init]  Self-calibration was skipped due to low texture or occlusion in the scene. Tracking accuracy may be affected.
in void InputThreadModul::close() : Err [400]: invalid resource handle.
[2026-07-08 09:44:24 UTC][ZED][INFO] Logging level INFO
[2026-07-08 09:44:24 UTC][ZED][INFO] Using USB input... Switched to default resolution HD720
[2026-07-08 09:44:25 UTC][ZED][INFO] [Init]  Camera successfully opened.
[2026-07-08 09:44:25 UTC][ZED][INFO] [Init]  Camera FW version: 1523
[2026-07-08 09:44:25 UTC][ZED][INFO] [Init]  Video mode: HD720@30
[2026-07-08 09:44:25 UTC][ZED][INFO] [Init]  Serial Number: S/N 16517409
[2026-07-08 09:44:25 UTC][ZED][INFO] [Init]  Depth mode selected: NEURAL. Ensure this mode matches your application's performance and accuracy requirements. See https://www.stereolabs.com/docs/depth-sensing/depth-modes for help.
[2026-07-08 09:44:25 UTC][ZED][WARNING] [Init]  Self-calibration was skipped due to low texture or occlusion in the scene. Tracking accuracy may be affected.
^C
root@fb7e1950dcb1:/usr/local/zed# exit