Bug 378098 - update meta data from selected images (generated outside digikam) does not work anymore
Summary: update meta data from selected images (generated outside digikam) does not wo...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Date (show other bugs)
Version: 5.5.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 11:05 UTC by georg.lipps
Modified: 2017-08-26 21:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description georg.lipps 2017-03-26 11:05:13 UTC
Still very happy with digikam and its continuing progess.

I have a workflow generating HDR images outside digikam. These new images contain exif-data (camera, time, etc.) obtained from the underlying LDR images (copied though exiftool).
When they "freshly" appear in digikam they have the digikam date from the time point when then HDR was generated. This is not 100% correct. Anyway up to version 5.4 I could correct this by updating meta date through reread meta data from picture.

Doing this operation with 5.5 does not update the metadata anymore. The whole section Foto Eigenschaften (image properties) is missing.

By the way, in the older version 4.x I remember there was the possibility to copy EXIF data from one picture to another. I did not this possibility in 5.5, is it gone?

Greetings,

Georg
Comment 1 Maik Qualmann 2017-03-26 17:13:44 UTC
Git commit 76060c16c14dabfb4aa7a5ac956c5292aff810bf by Maik Qualmann.
Committed on 15/03/2017 at 19:55.
Pushed by mqualmann into branch 'master'.

fix MetadataSynchronizer and non working lazy sync in digiKam-5.5.0

M  +1    -1    utilities/maintenance/maintenancedata.cpp

https://commits.kde.org/digikam/76060c16c14dabfb4aa7a5ac956c5292aff810bf
Comment 2 Maik Qualmann 2017-08-26 21:25:55 UTC
*** Bug 384059 has been marked as a duplicate of this bug. ***