| Summary: | Import Pictures dialog doesn't use file metadata (EXIF etc.) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | TD <testdroid> |
| Component: | Import-PostProcessing | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.3.0 | |
| Sentry Crash Report: | |||
| Attachments: | digiKam 8.2.0 dialog | ||
|
Description
TD
2023-12-03 17:30:51 UTC
In order to have metadata in the import tool, you have to activate the loading of metadata under Behavior in the digiKam camera settings (makes the connection slower). But that would only be for the view in the import tool. After downloading, digiKam always uses the metadata since digiKam-8.0.0. Maik Another note about the metadata in your example. The entry "Exif.Image.DateTimeOriginal" is often not present in images. Use "Exif.Photo.DateTimeOriginal" instead. Maik (In reply to Maik Qualmann from comment #1) > In order to have metadata in the import tool, you have to activate the > loading of metadata under Behavior in the digiKam camera settings (makes the > connection slower). But that would only be for the view in the import tool. > After downloading, digiKam always uses the metadata since digiKam-8.0.0. > > Maik Enabling or disabling this option doesn't seem to affect the import pictures dialog. The "device information" dialog says that the driver for "embedded cameras" doesn't use libgphoto2. (In reply to Maik Qualmann from comment #2) > Another note about the metadata in your example. The entry > "Exif.Image.DateTimeOriginal" is often not present in images. Use > "Exif.Photo.DateTimeOriginal" instead. > > Maik Thank you, this did the "magic" :-) One little additional question regarding the DateTime formatting / modification:
[meta:Exif.Photo.DateTimeOriginal]{replace:"_","",i} still results in the standard yyyy_MM_dd hh_mm_ss.ext. How do I remove the underscore without building a long custom expression using range?
Yes, it's hard for Windows users or users of Windows file systems to guess. The date string usually consists of colons as separators. Colons are forbidden characters for Windows, so they are automatically converted to underscores. So instead of replacing "_", you have to replace ":". Maik |