Capture_metadata() Blocking on CM5 While Working on CM4 #1227
Unanswered
trysightdev
asked this question in
Q&A
Replies: 1 comment
-
Hi, I'm assuming this is the same question as on the camera forum, where I've answered. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm experiencing an issue with Picamera2 on my Raspberry Pi CM5. The same code works perfectly on my CM4, but on the CM5 board, the call to capture_metadata() appears to block my code. As a result, the variables that depend on its return value are never initialized correctly and no frames are being received.
Below is the snippet of code causing the problem:
I have verified the following:
The camera is configured and recording properly before this call.
The hardware (CM5) and the library work correctly in isolation – for example, running the metadata.py example from the Picamera2 library prints the metadata as expected.
I even set up a different test project with a Flask server that uses the same capture_metadata() call, and it works fine on CM5.
Environment Details
Operating System:
Picamera2 Version:
0.3.24
Libcamera Version:
libcamera build: v0.4.0+53-29156679
Additional Context
My Question
Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions