`FrameDurationLimits` not reported in metadata

Open
#362 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
backend

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/libcamera

All issues in raspberrypi/libcamera

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.