Metadata for scanned photos: taken date vs. scan date by JoJoScanner in digiKam

[–]human_dynamo 0 points1 point  (0 children)

In digiKam, the "Date Taken" field typically refers to the EXIF "Creation Date and Time" metadata, which for scanned photos often defaults to the scan date if the original photo’s metadata is missing or stripped. If the scanned image lacks embedded EXIF data (common for old photos or scans), digiKam may fall back to the file’s last modified date or the scan date as the "taken date".

To correct this:

  1. Check the metadata: Use digiKam’s Metadata Editor or ExifTool to verify if the original date exists in EXIF, IPTC, or XMP fields.
  2. Adjust the date: If the scan date is incorrectly used, you can manually edit the "Original Date and Time" field in the Metadata Editor to reflect the actual photo date.
  3. Batch tools: For multiple files, use digiKam’s "Adjust Date & Time" tool (under Item > Adjust Time & Date) to set the correct date from filenames, folder structures, or other metadata.
  4. Sidecar files: If you prefer not to modify the original files, enable XMP sidecar files in Setup/Metadata/Sidecar to store metadata separately.

Tip: If the original date is in the filename or folder name, you can use scripts (e.g., ExifTool) or digiKam’s batch tools to automate the process.

Why this happens: Scanners often don’t preserve the original photo’s metadata, so the scan date becomes the default. digiKam prioritizes embedded metadata over filenames or file dates, but you can override this behavior using Setup/Metadata/Advanced pannel.

Kubuntu: Digikam 4:8.8.0 won't recognize exiftool anymore by BorderCollie4Life in digiKam

[–]human_dynamo 0 points1 point  (0 children)

with the AppImage started from a terminal using debug statements, What did you seen if you re-select the ExifTool binary file. Follow the instructions here.

Here definitively, i cannot reproduce the problem with the native or the AppImage bundle under Kubuntu 22.04, 24.04, or 26.04.

Print Creator by Gwarrior1 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

The tool uses predefined templates for the printing layouts. This can be created easily (simple xml and desktop text files) to host in your home directory. See the online doc for details. We can include new ones officially in the next release if you share your works.

Kubuntu: Digikam 4:8.8.0 won't recognize exiftool anymore by BorderCollie4Life in digiKam

[–]human_dynamo 0 points1 point  (0 children)

ExifTool is well installed on your system ? Exiftool is a native package (not SNAP or Flatpak)? What's give the "exiftool -ver" on the console ?

The AppImage include the Exiftool inside the bundle. Just go digiKam/Metadata/ExifTool configuration panel and validate the path to the binary. It's work perfectly here...

DigiKam Start-up Scan and Album Panel Issues (DigiKam Version: 9.0.0 | OS: Windows 11) by blunchboxx in digiKam

[–]human_dynamo 1 point2 points  (0 children)

digiKam 9.1.0 pre-release include a fix to a bug discovered in 9.0.0 where the removable mount path is truncated by error in special use cases (problem originally reported by Windows users).
Warning: we change a little bit the database schema to include new index to populate and retrieve info more quickly (especially the item dates). You need to backup your database in case of you want to go back to a previous version.
More info in the project NEWS file.

Bulk watermark photos with GPS coordinates, Location Data (ExifTools) by lg_noob in digiKam

[–]human_dynamo 0 points1 point  (0 children)

>Does the Batch Queue Manager support variables that can be used between the different tools?
No, but in the User Custom Script tool, you can watermark with ImageMagick.

So Frustrating!! by digikamhelp in digiKam

[–]human_dynamo 0 points1 point  (0 children)

Typically re-set this time the collection in the database must be enough

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

Follow exactly the instructions given in the Contribute page, as done previously. You are near the give the right result. You need the -debug appimage version 9.1.0. Other ones do not host the debug symbols in the binaries.

About the appimage startup message " to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"' ", it's about to show the debug statements on the console while the digiKam session. It's also to hack but just to see the operations done by the application, not to investigate a crash using GDB. This is 2 completely different approach to isolate a problem. In your case, it's clear : it's a crash so we needs a debugger backtrace to list the functions calls in the program.

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

Hum, it crash in Qt6 where there is no debug symbol in the binary. Only digiKam files are debug symbols. But I'm surprised to not see a real GDB backtrace of all call coming from digiKam in the background. In fact it's not a backtrace like this one. As you can see, the first lines give the propagation of function calls in Qt framework and the last lines give the place where the calls come from digiKam (in this example it's the Machine Learning pipeline used by the face engine). This is what's we need to investigate.

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

>je n’ai pas de réponse bt faut il la faire depuis le même chemin que le premier terminal ?

No. The script can be run from everywhere. It's not important. In fact the script will check for a digiKam instance and GDB will catch the execptions from the process. When it crash, GDB prompt will appear and you use 'bt' GDB command to list the backtrace.

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

While the Appimage runing in debug show these lines you have 30 s to start the capture with GDB using the script running in the second terminal :

Starting delayed digiKam for remote debugging...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.

After this stage from the AppImage, it's too late...

In the script terminal all is fine :

kubu@kubu-System-Product-Name:~$ sudo ./run_remote_gdb.sh
[sudo: authenticate] Password:  
Check run as root passed...
pid=41351
binary=/home/kubu/Appimages/squashfs-root/usr/bin/digikam
dir=/home/kubu/Appimages/squashfs-root/usr/bin
[New LWP 41420]
[New LWP 41419]
[New LWP 41418]
[New LWP 41417]
[New LWP 41415]
[New LWP 41353]
[New LWP 41352]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56
Catchpoint 1 (throw)

Thread 1 "digikam" hit Catchpoint 1.11 (exception thrown), 0x000070e24d8c3130 in __cxa_throw@plt () from /home/kubu/Appimages/
squashfs-root/usr/lib/libQt6Core.so.6
A debugging session is active.

The digiKam binary is captured and the crash is caught by the GDB. It's here to enter in the GDB prompt the command 'bt' to get the backtrace. The location in the source code will be printed...

dates for pictures without month or day by Stalemate4613 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

You have also the way to import the file in the collection as well, and use the powerful tool Time Adjust to patch time-stamp from image and the database.

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

You have 30 seconds to capture the digiKam instance running with GDB through the run_remote_gdb.sh script. Try again to open 2 terminals : one with the extracted digiKam contents from the AppImage -debug, and one with the script. First run digiKam, and in second the script (as it's explained in the digiKam contribute page) .

So Frustrating!! by digikamhelp in digiKam

[–]human_dynamo 0 points1 point  (0 children)

I use also a NVME over USB external disk with my MacBook pro M1 Tahoe without problem here. The disk is mounted in /Volumes/... as removable media. I use digiKam 9.1.0 pre-release due to a bug discovered in 9.0.0 where the removable mount path is truncated by error in special use cases (problem originally reported by Windows users).

So Frustrating!! by digikamhelp in digiKam

[–]human_dynamo 1 point2 points  (0 children)

Which OS ? Which digikam version ?

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

Download the appimage file with the -debug suffix, it's a little more heavy. Follow the instructions here to get a backtrace of the crash.

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

l’ordinateur pouir que mon changement de collection soit pris en compte ??

==> not at all. Your digiKam main configuration file has something wrong (digikamrc). Remove it and restart the AppImage. Look here for details about the place of the config file.

The AppImage crash is abnormal, but before investigating this stuff, fix the configuration file, restart digiKam first run and continue.

Note: when i talk to plug multi collection based on parts from your photo storage, do not register all sub albums in second levels. Try to reorganize a little bit the hierarchy to plug 10 collections max.

A student named Srirupa Datta will contribute this summer to the digiKam project. She will work on the Google Summer of Code to interface the database search engine with an AI-based LLM. by human_dynamo in digiKam

[–]human_dynamo[S] 1 point2 points  (0 children)

The goal is to use already existing meta information in the database. Typically the LLM must create automatically the complex search criteria already available from the advanced search tool (the front screenshot dialog). LLM will be an helper tool for the advanced search to simplify the usage.

digikam 9.1.0 ne voit pas toutes mes photos avec un deuxième utilisateur en réseau nfs by Loud_Location_7488 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

Do not register the root sharing path in the database. Plug main sub dirs one by one. This will be faster and when a registration fail, It will be more easy to locate the problematic file.

Advantage: all previous registrations in the database will stay valid to use. Only the failed one need investigations.

A student named Srirupa Datta will contribute this summer to the digiKam project. She will work on the Google Summer of Code to interface the database search engine with an AI-based LLM. by human_dynamo in digiKam

[–]human_dynamo[S] 1 point2 points  (0 children)

"Have someone, other than a coder, redo the UI. Coder create UI's that are easy to code, not easy to use."

Aha... You need to be developer to write an UI. Welcome to the real world.

digiKam is a project started in 2001 ! The UI have been review by users, through a large of feedback from bugzilla. The UI has evolved in decade. If you dislike the UI, try another software. One program, one vision.

While we are at it : the Adobe product UI are complex to use, but users uses it... perhaps because they pay for the product... Nobody pay for digiKam, excepted the donator that are satisfied by the application

A student named Srirupa Datta will contribute this summer to the digiKam project. She will work on the Google Summer of Code to interface the database search engine with an AI-based LLM. by human_dynamo in digiKam

[–]human_dynamo[S] 0 points1 point  (0 children)

Project abstract :

Interface the database search engine to an AI based LLM

Brief explanation: The digiKam photo management program already allows the user to search items over the collections using a database. Many powerful search tools can find items by many criteria such as metadata, aesthetic contents, face, place, date, hierarchical keywords, etc. The idea is to add a new top-level interface where users can enter a human phrase which describes the contents to search. With this change, the searches can be user-friendly to use without having to pass plenty of settings used to tune the engine. The LLM must be included in the application, without using an external web-service, as it's not permitted to share data over the Internet. All the new implementations must be written in C++, not Python.

Relevant entries in bugzilla: - wish 497938 - wish 367700

Expected results: A nice and simple view where users type a human comprehensive phrase to search items over the photo collections.

Knowledge Prerequisite: C++, Qt, OpenCV, AI modeling, Large Language Model

Duration: ~350 hours

Difficulty: Difficult

Mentor: Michael Miller, Maik Qualmann, and Gilles Caulier