A Pi0 cannot handle high-resolution and high-framerate when using libcamera. I have a v1 camera module (fisheye) connected to my Pi0 and 1280x960 (square picture/video) and a Gbit USB ethernet, streaming only.
30 fps leads to a lot of framedrops, simply unusable. With lower fps less framedrops but around 75% CPUlload, but I don't like that, I want smooth video and so I switched to legacy video stack. Then easy/smooth 30fps video, 6.3% CPUload from the videostreaming process. I use only ffmpeg to get h264 stream from GPU/VC4 and put it as rtsp stream to a mediamtx instance on 64-bit OS Pi4. From there I connect a browser getting it as WebRTC. Very smooth, runs 24/7 (if I again time time to create a insects proof enclosure and re-solder (again) a 10Mbps SPI ethernet module. I put the Pi0 in a drawer considering dead, but it turned out to be its (good? brand) SD-card. What do I hate those things more and more. Worked in a SD-card reader, but not in the Pi0. I use latest 6.6.47 kernel and latest rpicam-apps, not the lite variant of the apps, they lack various re-formatting protocols.
30 fps leads to a lot of framedrops, simply unusable. With lower fps less framedrops but around 75% CPUlload, but I don't like that, I want smooth video and so I switched to legacy video stack. Then easy/smooth 30fps video, 6.3% CPUload from the videostreaming process. I use only ffmpeg to get h264 stream from GPU/VC4 and put it as rtsp stream to a mediamtx instance on 64-bit OS Pi4. From there I connect a browser getting it as WebRTC. Very smooth, runs 24/7 (if I again time time to create a insects proof enclosure and re-solder (again) a 10Mbps SPI ethernet module. I put the Pi0 in a drawer considering dead, but it turned out to be its (good? brand) SD-card. What do I hate those things more and more. Worked in a SD-card reader, but not in the Pi0. I use latest 6.6.47 kernel and latest rpicam-apps, not the lite variant of the apps, they lack various re-formatting protocols.
Statistics: Posted by redvli — Thu Sep 19, 2024 6:06 am