Upper limit for the CSI-2 receiver is 1.5Gbps per lane.
Then there's a bottleneck at the CSI->ISP-FE interface of max. 2 pixels per cycle. At the standard 200MHz clock rate, that's equivalent to a total bitrate of 4Gbps (for RAW10) or 4.8Gbps (for RAW12), or somewhere in the region of 45fps. It may be possible to overclock the RP1 chip to 300MHz, which would lift this restriction.
However, 4K@60fps is way in excess of Raspberry Pi 5's H.264 encoding capability. With carefully-chosen H.264 options or by using MJPEG, 4K@25fps is marginal, with some risk of dropped frames. 4K@15fps or 1080@60fps should be reliable on a lightly-loaded system.
Then there's a bottleneck at the CSI->ISP-FE interface of max. 2 pixels per cycle. At the standard 200MHz clock rate, that's equivalent to a total bitrate of 4Gbps (for RAW10) or 4.8Gbps (for RAW12), or somewhere in the region of 45fps. It may be possible to overclock the RP1 chip to 300MHz, which would lift this restriction.
However, 4K@60fps is way in excess of Raspberry Pi 5's H.264 encoding capability. With carefully-chosen H.264 options or by using MJPEG, 4K@25fps is marginal, with some risk of dropped frames. 4K@15fps or 1080@60fps should be reliable on a lightly-loaded system.
Statistics: Posted by njh — Fri Aug 01, 2025 3:39 pm