First check the image’s recorded camera, lens, and focal length, then check whether the lens is adapted or purely mechanical. A wrong profile, a missing Lensfun profile, and an adapted lens that is not enabled are different problems. After selecting a plausible profile, confirm which corrections darktable actually applied. If strong geometric correction repeats noisy pixels along the edges, compare a crop with the corrected full frame; enlarging the scale to hide black corners is not a universal fix.
Trace the profile selection
- In darktable 5.6’s Lens Correction module, note the correction method. “Lensfun database” uses Lensfun profiles; “embedded metadata” is available only when supported correction data is present in the RAW file. Do not infer the selected method from the preview alone.
- With Lensfun selected, compare the module’s camera and lens fields with the image’s Exif information. Also check the recorded focal length, and, where relevant, aperture and focus distance: the manual says these values can affect corrections. If a field is wrong, record which one before changing anything.
- If the camera or lens identity is wrong, distinguish an Exif identification problem from a profile-availability problem. The manual notes that a lens name may need adjustment through exiv2, and that the image may need to be re-imported after such a change because the name is read during import. Treat this as a step to investigate, not a guaranteed fix for every mismatch.
- If Exif identification is plausible but no suitable profile appears, search the lens menu and check Lensfun’s supported-lens list. For a lens from a different mount used with an adapter, the manual says Lensfun profiles for that arrangement must be enabled with
lensfun-add-adapter. A purely mechanical lens, or some third-party lenses, may need manual camera or lens selection. - Read the module’s “corrections done” message. It reports which available corrections were actually applied for that camera-and-lens combination. Use this report, rather than the presence of a profile name or a changed preview, to decide what the module accomplished.
Acceptance worksheet
The following is a hypothetical diagnostic example, not a measured darktable result. Use the columns to decide what to investigate next; the manual does not promise that a particular profile or setting will produce the example’s outcome.
| Observation in a hypothetical frame | What it suggests | Decision to record |
|---|---|---|
| Exif says body A and lens B, but the module identifies lens C | Possible identification mismatch; confirm the actual lens and any adapter | Investigate metadata identification before judging Lensfun coverage |
| Exif looks plausible, but the matching lens cannot be selected | Profile availability or mount compatibility may be the issue | Check supported lenses; for an adapted mount, check adapter-profile enablement |
| A lens is selected, but “corrections done” lists fewer items than expected | Selection does not mean every correction is available or applied | Record the reported items; assess only those corrections as active |
| The corrected preview shows repeated edge texture in a noisy sky | Consistent with visible border fill after a strong correction | Compare the full frame and a crop at the intended viewing size |
| A crop removes the repeated strip but trims a needed subject detail | The artifact and the composition cannot both be dismissed | Keep the detail and accept the edge, or reconsider how much correction is needed |
Limits and next steps
The manual says lens correction can remap geometry and fill missing border data by repeating border pixels; strong corrections can make this visible, especially in noisy images. Check the four edges and corners at the size where the image will be viewed. As an editorial comparison, view the corrected full frame alongside a crop that removes the visibly repeated area, and note whether important content is lost. This comparison is a suggested acceptance method, not a darktable feature or a claim that cropping restores missing image data.
The scale control can help avoid black corners, and darktable provides an automatic scale option. But removing black corners does not establish that border fill is invisible or that more of the original scene has been recovered. If an edge artifact is unacceptable, try a crop that preserves essential content or reduce the extent of the geometric correction and reassess. If the profile still seems wrong, return to Exif, mount compatibility, and the applied-corrections report rather than assuming scale will repair profile selection. A missing profile may remain unresolved if Lensfun has no match; the manual points to updating its data or exploring profile calibration as further avenues, not guaranteed outcomes.
Does a listed lens prove its profile is correct?
No. Check camera, lens, and relevant Exif parameters, then read “corrections done.”
Should I keep increasing scale until the corners look clean?
Not automatically. Scale addresses black corners; inspect whether edge fill is visible and whether a crop gives a better composition.
Do adapter and purely mechanical lenses need the same fix?
No. The manual specifically calls for enabling adapted-mount profiles with lensfun-add-adapter; purely mechanical lenses may require manual selection.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.