@veye_xumm 好的，谢谢

@lujiawen
应该是系统版本的问题，请看一下part2
http://wiki.veye.cc/index.php/VEYE_MIPI_290/327_for_Raspberry_Pi/zh#.E5.85.B3.E4.BA.8EpiOS.E7.89.88.E6.9C.AC---Bullseye

@bladez
This question has been asked for a long time and the status has not been updated. I will mark the status as solved, so you can follow up again if needed, or just open the question.

@laawert Hi, sorry, I'm not doing any work in this area right now.

@thestaticturtle
Thank you for the valuable advice.
I took a brief look at the code of the raspindi project you mentioned, and this is basically a simplification and modification of the raspivid base. The calls to NDIlib are added. Of course, this is a c++ program.
Based on our veye_raspivid, I think it is feasible to do some porting work.
But our software engineers are very busy now, so it will take some time to arrange this.

Translated with www.DeepL.com/Translator (free version)

@petrusoroaga
-b parameter is effective.
The default value is 17Mbps which is pretty big value for 1080p@30fps stream.

state->bitrate = 17000000;

The H.264 encoder of the chip will be encod the video below this value. If your scene is not complex, the actual bit rate of the encoding may be much smaller than this.

I'll tell you a test method. You can -b1000000, configure to 1Mbps, you can see the obvious difference in file size.

@veye_xumm
Hello, thanks for the reply,

I will do as you say, refer to the code of this script to port the register configuration method to the driver layer.

Best regards,

Paco

@fire Yes, raspivid and raspistill works too on Ubuntu.

@veye_xumm 好的非常感谢，这个是编译动态库 用于python代码调用时使用的。就是那个SDK使用方法