I am a software engineer of the VEYE team and will try my best to help you.
I was thinking that since you took it from a dual board down to a single board that you may be able to reduce the board size and break it out into 2 again to fit everything.
Yes, we have the ability. However, the decision to make a new version of model is more of a commercial consideration. We are now more focused on developing new sensor and new products.
I will seriously discuss your suggestion with my colleagues in the company.
Thank you for your approval and feedback.
@consti10 said in Improve DE-coding on snapdragon devices:
turning off the HW decoder for h264 on android doesn't really make sense.
Maybe changing the poc type could fix this issue, too ?
I'm not sure about that.
- When connected via USB (original cable) there can be artifacts (I suspect packet loss via usb or some driver bug)
You are right. This camera will have a probability of packet loss. The higher the cpu performance of the host, the less packet loss.
This problem is still being studied and solved.
- POC type as described above.
@lubertroft
hi,
http://wiki.veye.cc/index.php/CS-MIPI-SC132_version_log
yuyv is supported in this version .
Because it is CS series, of course cs_mipi_i2c.sh is the corresponding script.
http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#yuvseq
@tokabe
Hi,
On i.MX8m Platform, our roadmap is based on SOM board. For now, we have finished MYIR i.MX8m board and AVNET Maaxboard(mini) board.
http://wiki.veye.cc/index.php/NXP_i.MX_Application_Note_Index
The coral.ai board from google is in progress.
So the linux version we use now depends on the system version that comes with the SOM board.
We have a V5.y version driver on raspiberry PI, maybe this will help you.
http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi
Of course, we will transplant all product drivers, including CS-MIP-IMX307, to i.MX8m. This work is also in progress.
@esjeeybi
About how to compile our drivers on rpi:
http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#Source_code_cross_compilation
You can get/set FPS, Gain, Brightness, Contrast via:
http://wiki.veye.cc/index.php/CS-MIPI-X_i2c
@ess
Hi, thank you, it is indeed typo.
jetson supports trigger mode, which I have done research on and it has worked. The plan is to organize it and release it along with our new machine vision product line. Estimated 15 days or so.
@ess
Our company discussed and decided to bring this forward. It is expected that the version will be available to you within 10 days.
@photon-94 Since you are using 327S instead of 327E，please use dtb file in VEYE-MIPI-CAM2M dir.
@jsw 你好，我们这边的4k屏幕没有此问题。
我猜测是nvoverlaysink 这个plugin跟你的显示屏的兼容性问题。 建议你到英伟达的论坛咨询一下。
@kuo 这个是树莓派的一种机制。其实并没有识别，cpu端通过mmal库，访问到gpu端，gpu端访问的camera。所以整体都是在应用层。
(1)我試著使用 git clone https://github.com/veyeimaging/raspberrypi.git 提供的 ./veye_raspipreview -t -1 指令去preview
不過沒有出現畫面，我裝的driver是veyecam2m，請問要做甚麼調整?
这个是lagcy模式，需要uninstall驱动，打开lagcy camera支持才行。
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
part2
(2)請問我能直接使用libcamera來preview嗎?
libcamera本质上是一个isp的框架，我们的相机本身带了isp功能。所以不需要，现在也不支持libcamera。
(3)我用gstreamer和vlc來preview在30FPS的情況下畫面會卡頓是正常的嗎?您那邊畫面是順暢的嗎?
这个主要原因是大量的使用cpu做软件的内存拷贝导致的。 还是建议你用lagcy mode。
@kuo
这个相机只有两种帧率 25和30，通过i2c脚本修改NTSC和PAL模式修改。
所以改gstreamer中的参数是无效的。
延迟的话，vlc默认是有比较大的缓存的。
gstreamer的缓存方面我就不太了解。
你想要的延迟范围是多少？
@robot 你好，最早出货的一批，可能在手触摸电源芯片附近，导致电源异常进而影响954芯片的工作。
你拍个照片给我吧。
另外订单信息可以私信发给我，如果是有问题的我们可以想办法修一下。
@sebaszz said in VEYE-MIPI-327S gstreamer issue:
./veye_raspivid -b 4000000 -t 0 -o - | gst-launch-1.0 -v fdsrc ! h264parse ! rtph264pay
config-interval=1 pt=96 ! gdppay ! tcpserversink host=192.168.0.208 port=7000
Please use rpi ip addr in this cmd too.