@barbanevosa Please refer to part8: https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson/

@barbanevosa The issue occurs because the camera sensor outputs a resolution of 3088 × 2064, but the receiving side (V4L2 buffers) aligns each line to a stride of 3136 bytes for memory alignment. When OpenCV is used directly with cv2.CAP_V4L2, it applies the width setting (3088) both to the sensor and to the buffer interpretation. Since the actual buffer has padding (3136 vs. 3088), OpenCV misinterprets the data layout, which results in visible image artifacts (stripes). We recommend using a GStreamer pipeline to handle the stride and alignment internally, so that OpenCV receives a clean image with the correct resolution.

@barbanevosa Hi, I am not very familiar with opencv, here is the command for your reference. http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#Stream_to_OpenCV Also, I think this link below will be helpful to you. https://qengineering.eu/install-gstreamer-1.18-on-raspberry-pi-4.html

@barbanevosa We are very sorry that due to COVID-19, we have not been in regular office for some time recently. A long time has passed, have you made any new progress? According to your description, I think you should enable the lagency camera function on the bullseye system. But it seems that the system is missing the mmal library for logging. But strangely enough, libdmipicam.so is actually just a part of veye_raspipreview wrapped into a dynamic library, and the runtime environment requirements for both should be the same.