Summary: | Date time original does not always update correctly on maintenance read from image files. | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | jm7 <jm7> |
Component: | Maintenance-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version: | 7.4.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | 7.5.0 | |
Sentry Crash Report: |
Description
jm7@acm.org
2021-09-05 16:32:51 UTC
We have discussed this topic endlessly. With many images of users, which were edited by many different programs and contained the most abundant date metadata. digiKam does not blindly rely on Exif.DateTimeOriginal, it carries out a ranking. Exif.DateTimeOriginal also has a higher priority. Upload a picture that you think digiKam does not determine the correct creation date, then we'll see. Maik Incidentally, here Bug 416994 is a possible cause, if you use sidecar files, is preferred over the mapping of XMP metadata by Exiv2 other date metadata. Maik One more word on Flickr. We just pass a title, description and tags to the API. digiKam does not send dates to Flickr. This means that Flickr itself extracts the date from the image metadata. If it is wrong, it is already wrong in your image and therefore it is clear that digiKam recognizes the same date as Flickr. Maik Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |