Bug 499114 - Wrong camera creation date
Summary: Wrong camera creation date
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 8.6.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-25 00:56 UTC by fuerallesg
Modified: 2025-04-11 18:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fuerallesg 2025-01-25 00:56:17 UTC
SUMMARY
At the automatic import images get tagged with the creation date of the file instead of the camera creation date

STEPS TO REPRODUCE
1. Add new images to an active album folder
2. Reload Metadata of the file to fix this

OBSERVED RESULT
Metadata shows the file creation date after the automatic/first import

EXPECTED RESULT
Metdadata shows the camera image creation date as the camera create date

SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2025-01-25 03:41:51 UTC
Enable the option to get image metadata while importing items:

https://docs.digikam.org/en/setup_application/camera_settings.html#customize-the-behavior

Gilles Caulier
Comment 2 Maik Qualmann 2025-01-25 06:59:05 UTC
For image files the metadata creation date is definitely used, in the import view this depends on the setting from Comment 1. For video files it has been fixed for digiKam-8.6.0, see Bug 499074.

Maik
Comment 3 Maik Qualmann 2025-01-25 07:26:16 UTC
I suspect that you don't mean the import tool at all, but the creation of a collection during the first scan.
It has already been reported that metadata is not read correctly here. However, we cannot reproduce it.
Make sure that the collection is not opened in other programs, otherwise it will not be available for digiKam to read (locked). Add digiKam and ExifTool in the digiKam directory as an exception to your antivirus program.

Maik
Comment 4 fuerallesg 2025-01-25 11:41:23 UTC
Sorry for the missing information. You are right and I am not using the import tool. It happens when I add new images to my NAS and digikam detects new images. Also, I have to note that the camera creation date is not just the file creation date, but also the date digiKam detected the file (at the time of the automatic collection scan). I just noticed this.

I haven't opened the files in any other program except Explorer for some time, but I wouldn't expect this to be an access problem.

If the problem only occurs on Windows. I might have an idea what might be causing the locking problem. It may be related to the fact that some images are read correctly (~500 out of 5000):

Since my update to Windows 11, I always get the following message when trying to grant access: "Your internet security settings prevented one or more files from being opened. Do you want to open these files anyway?" when I want to open more than 16 files on my NAS share. This hasn't happened on my Windows 10 system before. I will try to get another Win 11 computer with an older version of Win 11 to see if this happens there too. If not, I will check the digiKam behaviour on that system. 

Mik
Comment 5 fuerallesg 2025-01-26 16:49:39 UTC
I tested it with a different Win 11 computer without any problem. Thus, I tried it with a copied folder and lastly with the same folder as before on the original computer. Now, there was no issue at all. I will try to observe it and give an update as soon as I have any new information. It might be an issue with access rights/timeouts as you mentioned.

Mik
Comment 6 caulier.gilles 2025-04-11 18:13:35 UTC
Hi,

The 8.7.0 pre-release Windows installer from today have been rebuilt from
scratch with Qt 6.8.3, KDE 6.12, OpenCV 4.11 + CUDA support, Exiv2 0.28.5, ExifTool 13.27, ffmpeg 7, all image codecs updated to last version (jxl, avif, heif, aom, etc.).

Please try with this version to see if your problem still reproducible...

https://files.kde.org/digikam/

Thanks in advance
Best regards

Gilles Caulier