Performance Issue: FPS does not increase despite lowering/compressing video resolution on Raspberry Pi 5 + IMX296

Offen
  • Stimmt etwas nicht?
#367 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
42/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cpp, raspberry-pi

Rechercherichtung

Start by reading the IMX296 sensor driver and its supported sensor modes, then trace how rpicam-vid requests frame rate and image dimensions. Check whether the driver supports cropped sensor readout at the requested 1024×128 size and 240 FPS. Done means identifying whether the requested rate is supported and documenting the relevant configuration or limitation; the issue names no source files or tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Description

I am currently building a high-speed camera project using a Raspberry Pi 5 and the Raspberry Pi Global Shutter Camera (IMX296).

My goal is to achieve a higher frame rate (FPS). However, even though I have tried to lower and compress the video resolution using rpicam-vid, the actual FPS remains stagnant and does not increase as expected.

Environment

Hardware: Raspberry Pi 5, Raspberry Pi Global Shutter Camera (IMX296)
OS / Kernel: Raspberry Pi OS (Bookworm)
Software / Tool: rpicam-vid

What I've Tried

I attempted to lower the resolution using the --width and --height arguments in rpicam-vid (for example, dropping it down from the native 1456x1088).
While the output video file size decreases and the resolution changes, the running FPS does not go up. It seems to be capped at the default sensor frame rate.

Question
  1. Does the IMX296 sensor support windowing/cropping (ROI) or specific sensor modes to achieve higher FPS at lower resolutions on the Raspberry Pi 5?
  2. Are there specific rpicam-vid arguments (such as --viewfinder-width/--viewfinder-height or explicit --framerate / --level settings) required to properly unlock higher frame rates?

Any guidance or suggestions from the community or the developers would be greatly appreciated!

盧謙毓, 週二 下午5:19

Description

I am currently building a high-speed camera project using a Raspberry Pi 5 and the Raspberry Pi Global Shutter Camera (IMX296).

My goal is to achieve a higher frame rate (FPS). However, even though I have tried to lower and compress the video resolution using rpicam-vid, the actual FPS remains stagnant and does not increase as expected.

Environment

Hardware: Raspberry Pi 5, Raspberry Pi Global Shutter Camera (IMX296)
OS / Kernel: Raspberry Pi OS (Bookworm)
Software / Tool: rpicam-vid

What I've Tried

I attempted to run the following command to record uncompressed high-speed video directly into a ramdisk:
bash
rpicam-vid --frames 480 --framerate 240 --width 1024 --height 128 --codec yuv420 --denoise cdn_off -n -o /mnt/ramdisk/test.yuv
Observed Behavior:
Although the output resolution successfully changes to 1024x128 and the yuv420 file is saved to /mnt/ramdisk/, the actual frame rate does not reach the requested 240 FPS. It seems to be capped at the sensor's standard hardware/driver limit.

Question
  1. Does the IMX296 sensor driver support a high-speed mode or sensor crop/windowing (ROI) that can unlock higher FPS (like 240 FPS) at lower heights (e.g., 128px) on the Raspberry Pi 5?
  2. Are there any specific configurations needed in /boot/firmware/config.txt or additional rpicam-vid switches required to achieve this?

Any guidance or suggestions from the community or the developers would be greatly appreciated!

Vorherrschende Sprache
C++
Sterne
491
Forks
199
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus raspberrypi/libcamera

Alle Issues in raspberrypi/libcamera

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.