Created attachment 123230 [details] output of exiftool for one jpeg picture Within module automatic lens correction the camera manufacturer (Sony), the camera model (SLT-A77V) are discovered automatically, but the lens id is not. Otherwise the lens id seems to be stored within the jpeg picture - within Exif/MakerNote the lens id is correctly reported to point onto the Tamron SP AF 17-50mm Why is that (apparently known) lens id not automatically selected within automatic lens correction? Similarly the lens id seems to be unknown within picture properties, camera manufaturer and model are known, but lens is reported as "---". Sadly picture size of ~9MB is to big for an upload, reducing its size strips the exif/MakerNotes. Thus I've uploaded the output from exiftool to document that the lens id is known. Linux/KDE Plasma: 5.3.5-1 (tumbleweed)
If you use a standard package from your Linux, Lensfun library used in background is probably the last stable published 3 years ago. With the AppImage that we publish, we use the last code from LensFun where Lens catalog have been very improved. You can try the current 6.4.0 pre-release AppImage available here : https://files.kde.org/digikam/ Gilles Caulier
Thanks for your fast reply. I'm using the rolling OpenSuse release tumbleweed, thus it always includes (after some weeks) the most recent tools - for digikam it's the latest released version 6.3.0, for liblensfun it is 0.3.2. But I still believe that there might be a problem within digikam itself: If inspecting the exif metadata from within digikam, the correct lens id IS reported by digikam. But that knowledge seems to be lost within automatic lens correction or picture properties (see appended screenshots).
Created attachment 123261 [details] lensid as reported within digikam
Created attachment 123262 [details] lens id unknown within lens correction
Created attachment 123263 [details] digikam version information
Lens auto-detection is performed by Lensfun, not digiKam. Your version 0.3.2, is older than 2 years at least. This explain your disfunction. Using AppImage bundle where current implementation of Lensfun is used must fix your problem. Gilles Caulier
Exactly, lensfun is still here at 0.3.2 on openSUSE Tumbleweed. But you can update the camera and lens database with "lensfun-update-data". Maybe it helps already. Can you please send me a test image on my e-mail? It is difficult to find a image on the web exactly with the lens and complete metadata. Maik
In the meantime I've tried the following: 1. recompiled most recent lensfun and forced digikam to use the changed library. Sadly digikam crashes, probabely I have to recompile digikam, too. 2. use appimage for digikam 6.3.0. Then all my Tamron lenses are reported as Tamron lenses within lens correction, but always wrong ones. 3. I've sent Maik an jpeg sample for experiments. As I wrote, exiftool 11.50 always reports the correct Tamron lens. But it might not use lensfun.
Git commit fce3ba49cc02bc825e2e1869e6efb5d6ab0b6782 by Maik Qualmann. Committed on 17/10/2019 at 16:55. Pushed by mqualmann into branch 'master'. ignore wrong value from Exif.Photo.LensModel FIXED-IN: 6.4.0 M +2 -1 NEWS M +8 -5 core/libs/metadataengine/dmetadata/dmetadata_photo.cpp https://invent.kde.org/kde/digikam/commit/fce3ba49cc02bc825e2e1869e6efb5d6ab0b6782