# Frame tear for zed x mini camera

**URL:** <https://community.stereolabs.com/t/frame-tear-for-zed-x-mini-camera/9743>\
**Category:** ZED X\
**Created:** [August 25, 2025, 9:28am UTC](https://community.stereolabs.com/t/frame-tear-for-zed-x-mini-camera/9743 "2025-08-25T09:28:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukechen](https://community.stereolabs.com/user_avatar/community.stereolabs.com/lukechen/32/4797_2.png) [@lukechen](https://community.stereolabs.com/u/lukechen)\
**Post date:** [August 25, 2025, 9:28am UTC](https://community.stereolabs.com/t/frame-tear-for-zed-x-mini-camera/9743/1 "2025-08-25T09:28:57Z")

</div>

Hi engineering team! I am using zed x mini camera with zed link duo on jetson orin nano. I used the python API to grab images and publish them into compressed images in ros2, which I later collected to be a rosbag and run Kalibr on it. However, the kalibr warns about “multiple april grids detected”, which turns out to be frame tearing for the images in the rosbag. Here is an example:

 ![frame_tear_zedxm](https://community.stereolabs.com/uploads/default/original/2X/0/01315135f8cda10feb1b00051d4a032f950c2511.png)

I am wondering what could be wrong here? Can I avoid this through some setting? Note that I the image is collected in a docker running ros on the host machine, and I am using SVGA. Here is the config file I used for launching the camera:

camera\_id: 0  
enable\_fps\_tracking: false  
enable\_left\_rgb: true  
enable\_right\_rgb: true  
enable\_depth: true  
resolution: SVGA  
fps: 30  
depth\_mode: NEURAL  
depth\_min: 0.2  
depth\_max: 10.0  
coordinate\_units: METER  
coordinate\_system: IMAGE  
enable\_right\_side\_measure: true  
enable\_image\_enhancement: true  
enable\_fill\_mode: true  
streaming\_mode: jpeg  
jpeg\_quality: 90  
video\_codec\_preset: balanced  
pix\_fmt: null  
imu\_rate: 100  
imu\_reference: current  
saturation: -1  
sharpness: -1  
gamma: -1  
denoising: -1  
whitebalance\_temperature: -1  
whitebalance\_auto: true  
auto\_exposure\_gain: true  
exposure\_time: -1  
exposure\_compensation: -1  
analog\_gain: -1  
digital\_gain: -1  
led\_status: -1

Appreciate your help!

---

<div class="post-metadata">

**Author:** ![mattrouss](https://community.stereolabs.com/user_avatar/community.stereolabs.com/mattrouss/32/2452_2.png) [@mattrouss](https://community.stereolabs.com/u/mattrouss)\
**Post date:** [August 25, 2025, 4:46pm UTC](https://community.stereolabs.com/t/frame-tear-for-zed-x-mini-camera/9743/2 "2025-08-25T16:46:14Z")

</div>

Hi @lukechen,

Welcome to the forums! 👋

Duplicating the response from the email thread, we would prefer responding on the forum just in case someone else has the same issue 🙂

Thank you for reporting this, this is not expected. I would highly recommend using the offical ROS 2 wrapper: [https://github.com/stereolabs/zed-ros2-wrapper](https://github.com/stereolabs/zed-ros2-wrapper) which has its implementation extensively tested and validated by our team.

Can you run the ZED\_Diagnostic tool and share the resulting JSON file? This will help confirm your setup and software versions.

---

<div class="post-metadata">

**Author:** ![lukechen](https://community.stereolabs.com/user_avatar/community.stereolabs.com/lukechen/32/4797_2.png) [@lukechen](https://community.stereolabs.com/u/lukechen)\
**Post date:** [August 27, 2025, 4:20pm UTC](https://community.stereolabs.com/t/frame-tear-for-zed-x-mini-camera/9743/3 "2025-08-27T16:20:55Z")

</div>

Thanks for the reply. I found the issue was in our code base, where we used a volatile image buffer that can be overwritten by ZED SDK. After fixing the bug, the problem is no longer there. Thanks for your help!

For future reference, ZED SDK returns a copy to the image it captured, which might be overwritten later. You should copy that image first.
