
Inspect Hugin's remembered lens information when a newly added photograph gets different lens values from those expected from EXIF. The documented lookup can apply stored calibration at import. Correcting that database and correcting an already loaded project's settings are separate operations: a database change does not automatically refresh existing project values.
Key Takeaways
- Imported lens values can come from remembered calibration, not EXIF alone.
- A manual database entry can outweigh automatically saved information.
- Verify both a fresh import and the existing project separately.
Record the disagreement before resetting anything
Identify the camera, lens and capture settings, then compare the imported field of view, projection and relevant correction values with the source information. A displayed difference is a reason to investigate provenance, not proof that the file's EXIF was rewritten.
Keep an unchanged project copy. Do not erase the calibration database merely because one field looks unexpected. Other projects may depend on valid entries.
The lens-profile diagnosis describes a different application's identity lookup. Its controls cannot establish which saved state Hugin imported.
Separate active settings from future lookup
The Hugin FAQ's import explanation says the database retains lens projection, crop, field of view, distortion and photometric information. It is consulted when images are added, so an earlier incorrect calibration can influence a new project.
For the existing project, inspect the image's settings and the applicable Reset options in the Photos context menu. Re-establish credible values before generating or trusting control points. A reset is not a substitute for knowing the correct projection and capture assumptions.
When a verified calibration should govern subsequent use, the documented Lens > Save lens to database route records it manually. The FAQ says manually saved information receives greater weight than automatic history. This is a calibration decision, not an invitation to store guessed values as authoritative.
Compare fresh and existing project state
Use a new project to add a representative source after making an intentional database correction. Compare the imported values with the intended calibration. Do not expect an image already present in another project to update just because its database entry changed.
Revisit that earlier project's explicit settings separately. Record which state was corrected so another editor does not mistake a successful fresh import for repair of every archived PTO.
For spatial color shading, use the flat-field reference distinction to keep a suitable optical reference separate from a plausible-looking smooth image. That Lightroom procedure is not Hugin's database command.
Verify the photographic result
Recalculate the intended geometry and inspect a proof against recorded lines and overlap features. A credible imported focal length does not alone prove the distortion fit is correct.
If the values remain surprising, preserve the disagreement and consult version-appropriate support before removing shared state. This is a proposed provenance check, not a database repair performed here. Accept the result when both future imports and the relevant existing project have independently reviewed settings.
Related tasks
- What Should I Check When darktable 5.6 Selects the Wrong Lens Profile or Repeats Noisy Pixels at the Borders?
- Use Lightroom Flat-Field Correction with the Right Calibration Frame
Sources and scope
- Hugin FAQ — focal length differs after adding an image: Lens database stores geometry/photometrics, is read when images are added, manual saved calibration has higher weight than automatic history, and changed database values do not update existing projects.
Official Hugin manual sections were actually opened and read on October 23, 2026 (Asia/Shanghai). Commands, comparisons and acceptance checks are proposed rather than performed. Historical FAQ descriptions are not claims about every installed release; verify the interface and source version before changing a project.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.