Ok got it. I confirm output format is I420 and array order is correct. Thanks for your help

@hezudao
不客气~

@veye_xumm 由于时间太久了,客户没有进一步的反馈,我会把这个帖子标记为已解决.

@watchever
Hi, it is the ISP limit which VEYE-MIPI-IMX462 used.

@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

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

@dan_lionking
Right. That's the result.

@seka
Thank you for sharing.