| Summary: | Prioritize user-added metadata over the ones in MakerNotes. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | pthfdr |
| Component: | Metadata-Exif | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.8.0 | |
| Sentry Crash Report: | |||
|
Description
pthfdr
2025-07-30 16:38:00 UTC
I don't see any errors in the 1.dng image; digiKam shows the focal length as 8.1mm. This matches all possible metadata fields, both Exif and the maker notes. In the 2.dng image, we can prioritize Exif.Photo.LensModel first, just like with Sony and Canon, for Pentax. Maik Git commit 258d32593707e4d684e30fc1991ca991b0e8c80f by Maik Qualmann. Committed on 31/07/2025 at 06:46. Pushed by mqualmann into branch 'master'. prioritize Exif.Photo.LensModel also for Ricoh/Pentax M +5 -1 core/libs/metadataengine/dmetadata/dmetadata_photo.cpp https://invent.kde.org/graphics/digikam/-/commit/258d32593707e4d684e30fc1991ca991b0e8c80f I don't see any problems with the focal length in the digiKam code. I suspect they have to reread the metadata from the image to the database if they subsequently changed the values with ExifTool. Maik (In reply to Maik Qualmann from comment #3) > I don't see any problems with the focal length in the digiKam code. I > suspect they have to reread the metadata from the image to the database if > they subsequently changed the values with ExifTool. > > Maik I have updated to 8.7.0, and the issue persists. Refer to the 2 screenshots I have added to the filebin link. I went to Settings->Configure digikam->Metadata, and unchecked "Use `exiftool` backend to read metadata from files". After that, I selected all the files in the folder, and selected Item->Reread metadata from file. The 35mm eqv focal length is missing, despite it being shown correctly in the right. Then, I re-enabled the `exiftool` backend and reread the metadata again (which makes the lens name disappear at random). Regarding the commit, as I have mentioned before, the behavior (read from XMP `Lens` and EXIF `LensModel`) should be the default and not limited to certain brands of cameras; the data from makernotes should be considered last (instead of first) and should only be used if not found anywhere else, as it is not uncommon to take photos using an adapted/"dumb" lens and fill in the missing metadata afterwards. No, you need to try with 8.8.0 appImage daily build available here: https://files.kde.org/digikam/ Best regards Gilles Caulier (In reply to caulier.gilles from comment #5) > No, you need to try with 8.8.0 appImage daily build available here: > > https://files.kde.org/digikam/ > > Best regards > > Gilles Caulier It seems that the edited lens names now show correctly. However the first issue shown in the screenshots still exists in the latest daily build. The 35mm specification isn't a bug; you need to ensure that this information is also written to the corresponding Exif field so that Exiv2 can evaluate it. The display in the ExifTool viewer is likely a dynamic calculation, which we cannot currently evaluate. You need to set the metadata field "Exif.Photo.FocalLengthIn35mmFilm" and/or "Xmp.exif.FocalLengthIn35mmFilm". Maik I checked again; there's no information about the 35mm focal length in image 1.dng. We already have a bug report regarding the calculation of the 35mm focal length, see Bug 367935 I'm therefore closing this bug now. Maik |