Hmm that might be why, I will have a crack with media-ctl when my new board arrives with a non broken csi port D: (too strong fingers while troubleshooting this)videoconvert is a software stage, so will take a fair amount of CPU. I wouldn't be surprised if "htop" didn't report one CPU core maxed out. You don't say which version of the Pi you're using.I am trying to use libcamsrc with my module 3 camera but unfortunately - the library sucks ass. When using the library it drops 40 odd frames at 2304 x 1296. libcam-hello works fine at full 50.
Is there a way to get gstreamer to work with libcam-hello? Or better yet, what am I doing wrong with libcamsrc :
gst-launch-1.0 libcamerasrc ! video/x-raw,width=2304,height=1296,framerate=50/1 ! videoconvert ! autovideosink
There should be no need to use it though as you can use kmssink and set the format to RGB or I420 if you're booted to the console. waylandsink is likely the most efficient video sink if running with the GUI.Unicam will only give you raw Bayer images, with no exposure, gain, or white balance control.I can't get unicam to work either with module 3, for some reason it claims the device is always in use. If neither of the above, how can I use unicam? seems pointless if I can't interact with it.
Always in use, or the pipeline is invalid? You have to use the Media Controller API to configure the pipeline of underlying nodes.
Statistics: Posted by d0gman — Sun Oct 06, 2024 5:12 am