Issues using zedsrc and zeddemux with DeepStream SDK

I am using the following setup:

  • Camera: ZED X Mini

  • Jetson: Jetson NX 16GB (zed Mini Carrier Board)

  • ZED SDK: 5.0

  • DeepStream SDK: 7.1

I am trying to use the ZED SDK’s zedsrc and zeddemux elements with DeepStream. I need both the left and right images, so I implemented a pipeline using zeddemux.

However, I frequently encounter the following error:

gst_buffer_unmap: assertion 'GST_IS_BUFFER (buffer)' failed

In addition, memory usage keeps increasing until an OOM occurs.

When I added a queue between zedsrc and zeddemux, the frequency of the error reduced but did not disappear completely. As a workaround, I implemented the pipeline using videocrop instead of zeddemux.

Could you please advise the correct way to use zedsrc and zeddemux in a DeepStream SDK or GStreamer pipeline without causing errors or memory leaks?

Thank you in advance for your help.

Hi @kwonok

What’s the pipeline that you use?
Without details, it’s not possible to identify the cause of the issue.

Thank you for your response.
Here are the details of my current pipeline configuration.

I am using the DeepStream Python SDK (7.1) to integrate the ZED SDK(5.0)’s zedsrc and zeddemux elements.

deepstream_python_apps

The pipeline structure is as follows:

zedsrc 
  stream-type=2 
  camera-fps=30 
  camera-resolution=1 
  opencv-calibration-file=opencv.yml
    → queue 
    → zeddemux name=demux 
      → demux.src_left → queue 
      → demux.src_aux → queue
    → streammux
    → pgie
    → sink

Please let me know if you would like me to provide more detailed information, such as the full pipeline configuration or logs, to help with troubleshooting.

Is this calibration file valid?
Does the stream work without this option?

Have you tested the same pipeline with GStreamer to check that the stream can start?

Q1. Is this calibration file valid?
Yes, the calibration file is valid and properly formatted.

Q2. Does the stream work without this option?
Yes, I have tested the stream without specifying the calibration file, and it works as expected.

Q3. Have you tested the same pipeline with GStreamer to check that the stream can start?
Yes, I have tested the same pipeline directly with GStreamer, and the stream starts successfully.

Try to provide the absolute path to the calibration file.