@seka
I'm not very familiar with python. But in my opinion, jpeg is compressed data, which can't be subset by simple sampling, is it?

@xsw
很好。
硬件是被动的，软件是主动的。
摄像头不能去操作主板的内存，是靠主板上的软件来操作摄像头，把数据放到内存。
树莓派是上我们提供的两种应用模式，都可以由软件获取到摄像头输出的数据。
请参考详细的文档和代码。

@veye_xumm 哦，好的，那可能是采购给我的型号弄错了，我用327的dtb再试一下，谢谢了

@dan_lionking
You are welcome.

@watchever
I think what you mentioned is mshutter. Yes, of course.
mshutter :
If you use manual mode, the exposure time will be independent of the ambient brightness.

@watchever
For yuv ，
http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#yuvseq

And I'm sorry , can not provide you such python code now.

@watchever
You are right.

@watchever
Yes. VEYE series does not support exposure time longer than 1 second.
CS series support this feature.

Thanks xumm I have add rpi3-gpiovirtbuf initialize routine in the libdmipicam.so library, so don't need to run this binary alone and it works.
Thanks

@fabricio-borges
hi，
I think this is normal, the VEYE series of cameras do not have the ability to save parameters. Therefore, each power outage causes the parameters to return to their default values.

@watchever
yes,you are right.

@veye_xumm 明白了，谢谢！！

@veye_xumm OK, thanks. Solved it by adding vc.ril.hvs component before h264 encoder and doing some fancy overlays by libcairo.

@seka
hi, VEYE-MIPI-IMX462 do not support YUV 10BIT/12BIT.

@veye_xumm Ok, thanks.

@alexz3-0

@alexz3-0 said in 327S work on Raspberry pi CM4 module:

Failed: don't know how to set GPIO for this board!

针对这个现象，请执行：

cat /proc/cpuinfo | grep Revision | awk '{print substr($NF,length($NF)-5,6)}'

给我一下打印信息。

根据7.5.2，CM4平台上面，./camera_i2c_config命令是不需要加参数的。
此外，通用根据7.5.2，camera1的i2cbus是10，所以你的命令应该是：

./veye_mipi_i2c.sh -r -f devid -b 10

@dan_lionking
Right. That's the result.

@seka
Thank you for sharing.

@veye_xumm Thank you Xu, downloaded the new file and now it is working like a treat!

已与瑞泰沟通驱动移植事宜。