Summary: | Rename by date is based on 'date modified' not 'date created' : add helper text in GUI | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Art <marshallad> |
Component: | AdvancedRename-Import | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, marshallad, metzpinguin, miquel6 |
Priority: | NOR | ||
Version: | 2.6.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/digikam/e2b75ae311e417decf1b37c9fcb2a5f953c5b796 | Version Fixed In: | 5.4.0 |
Sentry Crash Report: | |||
Attachments: |
Digikam Download Screenshot
Digikam Name vs EXIF |
Description
Art
2012-06-14 22:10:14 UTC
Are you sure that the file creation date is different than the one you see in digiKam? As far as I can see from the code and my database, the correct file creation date is used. Have you downloaded the files from your camera and checked with the "normal" tools for detecting the file creation date? I had uninstalled digikam so have now reinstalled 2.8.0. The problem persists. It occurs consistently but not with every pair of raw + jpg images. > Are you sure that the file creation date is different than the one you see > in digiKam? I've attached a capture of the file download screen. The highlighted .cr2 file is named after the date in 'Camera File Properties'. Note that the creation date listed under 'Photograph Properties' is two seconds earlier. As shown in the next screenshot, the .jpg version of the same image is named according to the creation date in 'Photograph Properties'. > Have you downloaded the files from your camera and checked with the "normal" > tools for detecting the file creation date? I've looked at what my other software says about the .cr2 file and there is some variability. -Adobe Bridge says the Date Created is 06:08:12 02:19:38, Date Modified 06:08:12 02:19:40. -Windows 7 says Date Created is 06:08:12 02:19:40 and Date Modified is also 06:08:12 02:19:40 (but reports that the .jpg Date Created is 06:08:12 02:19:38 and .jpg Date Modified is 06:08:12 02:19:40). Breeze Browser, my usual downloading / sorting program, considers both the .cr2 and .jpg as Created on 06:08:12 02:19:38. From my point of view, it doesn't matter which is used, as long as they are identical for the .cr2 and .jpg versions of the same image. Created attachment 73263 [details]
Digikam Download Screenshot
Created attachment 73264 [details]
Digikam Name vs EXIF
Please have a look at 307253: Is the offered patch what you actually request? Art, This file still valid using last digiKam 4.2.0 ? Gilles Cauleir This file still vlid using last digiKam 5.0.0 ? Gilles Caulier Gilles, I'm facing the same problem in Ubuntu 16.04/Digikam 5.1.0. Steps to reproduce: 1. Image's EXIF date taken: 02/09/2015 13:13 2. Copied the image from the SD card to an external hard disk to made a backup 3. Then copied again from the external hard disk to the laptop's hard disk to import to digikam. The file's dates get changed: date accessed: 22/08/2016 11:23:18, and date modified 21/08/2016 17:10:51. The EXIF date is the same ;-) 4. Import -> Add images... 5. Select the image to import, rename to custom "[date]" (the same behaviour with "[date:ISO]", "[date:yyyyMMdd]", etc.) 6. The filename of the imported image is 20160821T171051.JPG (for NEF files the date is the same) The strange thing is that if i rename the imported file (F2) using the same format "[date]" I get the correct image name: 20150902T131352.JPG Regards Miquel DigiKam Import defaults uses the file creation date. For a exact date enable in camera setup the option: Use file metadata (makes connection slower). Maik Thanks Maik, and sorry for my late reply! That's true, but it would be helpful to add a hint in the import screen because it's confusing ;-) Miquel Git commit e2b75ae311e417decf1b37c9fcb2a5f953c5b796 by Maik Qualmann. Committed on 10/12/2016 at 19:25. Pushed by mqualmann into branch 'master'. add note to GUI if file metadata used or not Related: bug 362406 FIXED-IN: 5.4.0 M +3 -2 NEWS M +33 -1 utilities/importui/widgets/renamecustomizer.cpp M +1 -0 utilities/importui/widgets/renamecustomizer.h https://commits.kde.org/digikam/e2b75ae311e417decf1b37c9fcb2a5f953c5b796 |