@lich-mk YES. VEYE series do not have param save function.

@vpr Hi, please take a look at this post about the test principle of time delay. http://forum.veye.cc/topic/22/i-want-to-synchronize-the-two-cameras-in-sync-mode/9?_=1619401819344 Our veye series modules include isp function, which involves whole frame caching in some places, so there will be a little extra delay than raw sensor's camera. In my experience, the screen-to-screen latency test results are indeed more than 100ms.

@veye_xumm Completely turning off denoise fixes the issue. This frame was captured on lowest default denoise levels. Thanks.

@123456 应该是由于没有给模组的poweron引脚拉高造成的。 先执行一下camera_i2c_config，然后再拍照即可。

@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.

@nathan-sinclair We are very sorry that due to COVID-19, we have not been in regular office for some time recently. Based on your description, I think it is most likely due to the lack of power supply capacity of the FFC cable of the pi ZERO. Please try it with a separate 5V power supply. Looking forward to your results.

@veye_xumm thank you very much!

@nathan-sinclair Okay, you're great!

@veye_xumm I was just looking at the i2c program. Call this resolved.

@autot said in 树梅派VEYE-MIPI-IMX462设置不同曝光时间得到图像没变化: 在VEYE-MIPI-IMX462的datasheet中没有提到曝光可调，是不是意味着这个 VEYE-MIPI-IMX46模块的曝光不可调 可调的。 mshutter配置这两个参数应该会有不同。但是可能agc的调节（也就是增益自动调节），把亮度调到类似，让你没有注意到其差异。 你可以把agc配置为0，然后再分别配置mshutter，对比图像的差异。

@serene said in VEYE-MIPI vs. CS-MIPI: Hi, what's the difference between VEYE-MIPI series vs. CS-MIPI series? The two series use different isp schemes. We have used different sensors for each of the two series. In general, the CS series supports more parameters and is richer. the VEYE series supports fewer parameters.

@veye_xumm Can't save? Oh... It's really disappointing. Anyway... Okay. Thank you. I'll close this agenda.

On the Tinker Edge T board, we get video from the camera using the command: gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)YUY2, width=(int)1920, height=(int)1080,framerate=(fraction)30/1" ! glimagesink But when trying to get the h264 stream using the command: gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)YUY2, width=(int)1920, height=(int)1080,framerate=(fraction)30/1" ! videoconvert ! x264enc ! h264parse ! rtph264pay config-interval=1 pt=96 ! rtph264depay ! rtspclientsink protocols=tcp location=rtsp://0.0.0.0:8554/live/h264 latency=1000 An error is thrown: [image: 1645528098443-photo_2022-02-22_14-07-48.jpg] How to get h264 stream?

@wqh 这个我也不是很懂，但是我们文档4.2.1章节的 Gstreamer 嵌入到 OpenCV 部分，肯定是一种实现方法，有很多客户都是这么做的。

@jdx-jdx 通过-b来指明不同的i2c bus. 请参考下面链接的 4.3.1部分 http://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2/zh#.E8.A7.86.E9.A2.91.E6.8E.A7.E5.88.B6.E8.BD.AF.E4.BB.B6.E5.8C.85.E7.9A.84.E4.BD.BF.E7.94.A8

@veye_xumm Okay. Anyway Thank you.