30 fps at full resolution 2304x1296 is impossible. luckfox rv1106g3

[Sekilsgs2]

Why is frame reading performance from the camera so poor? Using Rockit, I can easily read at 30 fps with the SC3336 camera's maximum resolution of 2304x1296, but this is impossible with OpenCV-Mobile. Why not use the chip's built-in hardware to output images at the required resolution, frame rate, and format (VI, VPSS) instead of V4L2?

[dosubot]

Hi @Sekilsgs2! I'm Dosu and I’m helping the opencv-mobile team.

The main reason you can't achieve 30 fps at 2304x1296 with OpenCV-Mobile on the Luckfox RV1106G3 is that OpenCV-Mobile primarily uses the V4L2 backend for camera access, which doesn't leverage the chip's hardware-accelerated interfaces (like VI/VPSS) that Rockit uses. V4L2 is generic and portable but often can't match the performance of hardware-specific solutions, especially at high resolutions and frame rates. Rockit achieves better results because it directly uses the chip's built-in hardware for optimized data transfer and processing, while OpenCV-Mobile's V4L2 path is limited by software overhead and less efficient buffer handling [source 1][source 2].

There is ongoing work in OpenCV-Mobile to add hardware-accelerated backends (like capture_cvi and Rockchip AIQ integration), but support is incomplete and may not be stable or fully optimized for all boards yet [source 3][source 4]. If you need maximum camera performance, using vendor-specific libraries or a hybrid workflow (e.g., capture with Rockit or a hardware SDK, then process with OpenCV) is currently the most reliable approach.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}