`FrameDurationLimits` not reported in metadata
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by reading IpaBase::applyFrameDurations() and IpaBase::applyControls() to trace how FrameDurationLimits reaches metadata and whether clearing libcameraMetadata_ affects it. Check the relevant metadata tests or add a focused regression test; done when the expected frame duration limits are present in metadata after controls are applied.
Written by the indexing model from the issue text.
Description
Looking at IpaBase::applyFrameDurations(), it should ensure that FrameDurationLimits is reported in metadata, but that does not seem to be the case.
Maybe because IpaBase::applyControls() clears libcameraMetadata_?
- Dominant language
- C++
- Stars
- 490
- Forks
- 200
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/libcamera
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
raspberrypi/libcamera#367 · 1 comment ·
All issues in raspberrypi/libcamera
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day