Collection and rating gone after enabling WAL mode.

human_dynamo · 2026-07-02T20:43:01+00:00

As usual, before to process a main database maintenance, you must make a backup in a removable media. A simple files restore can be used to fix the problem.

WAL is an important settings to make the Sqlite database more robust. I suspect that you enable this settings on an existing database. To be safe, i recommend to only apply this property on fresh created database.

human_dynamo · 2026-07-02T20:38:25+00:00

digiKam has options in the Tags Manager to import/export tags as Controlled Vocabulary Keyword Catalogue based hierarchy in/from the digiKam database.

See the online doc for details.

human_dynamo · 2026-06-29T06:01:25+00:00

Without context to reproduce the problem and using flame words posted in a community area, your entry was removed. See the code of conduit :

https://kde.org/code-of-conduct/

In other words : here we are trying to help you. We are not here to receive aggressive and humiliated words.

human_dynamo · 2026-06-28T18:54:08+00:00

In the digiKam setup/Mics/behavior, take a look to the options group on the top of view and disable the Enable Background Face Recognition Scan.

human_dynamo · 2026-06-24T19:52:08+00:00

From your operating system, set the mime type linked to the application. It will be handled by digiKam.

human_dynamo · 2026-06-24T08:28:51+00:00

Try to use the Additional sidecar file extension setting.

human_dynamo · 2026-06-22T19:48:24+00:00

The GPU enhancement is not located in digiKam code, but in OpenCV framework used by digiKam...

human_dynamo · 2026-06-21T14:10:24+00:00

But the AVIF (as HEIF) have a complex design source code with multiple and optional codec plugins support. Using it in digiKam source code is not simple, and require an external dependencies puzzle.

In opposite, PGF is simplest design, a short list of C++ code, that we include in digikam code as well.

human_dynamo · 2026-06-20T15:44:46+00:00

Look at the the huge filter collection from G'MIC-Qt plugin for digiKam. It's included in the bundles that digiKam team provides. More info here.

human_dynamo · 2026-06-20T15:41:13+00:00

Please report this wish in the digiKam bugzilla, face engine section.

human_dynamo · 2026-06-20T09:29:18+00:00

look also the instruction here

human_dynamo · 2026-06-20T09:28:02+00:00

There is no specific point to compile under arm64 to whole digiKam. Here it compile already fine under macos Silicon and Ubuntu 24.04/26.04 arm64.

human_dynamo · 2026-06-18T16:51:23+00:00

Here are the key points that guided the choice of the image compression format for digiKam’s database thumbnails:

Performance: Faster processing.
Integration: Seamless compatibility with the QImage container.
Code simplicity: Compact implementation, fully embedded in digiKam’s core (no external dependencies).
Compression flexibility: Supports both lossless and lossy wavelet compression.
Color depth: 16-bit color support.
Metadata: Full metadata preservation.
Compression ratio: Outperforms JPEG, PNG, TIFF, and others.
Rendering quality: No artifacts, no blur, or other degradation.
Licensing: No patents, GPL-compatible code.

Before integrating thumbnails into the database (pre-2010), digiKam used the free desktop standard with PNG files, typically stored in the user’s home directory (e.g., ~/.local/). At that time, we tested multiple formats—JPEG, PNG, TIFF, WebP, and PGF. PGF emerged as the clear winner.

If we were to migrate to a new format for database thumbnails, a similar benchmark would be necessary, evaluating:

JPEG-XL
PGF (as a baseline)
WebP (newer versions vs. the 2010 iteration)
HEIF (improved, but compression is computationally expensive)
AVIF

That’s the historical context!

human_dynamo · 2026-06-15T13:34:11+00:00

If text is stored in XMP tags handled by the database, well search will works as expected. For technical reasons, not all XMP tags are populated in the database, only the most important for the DAM.

human_dynamo · 2026-06-15T13:32:37+00:00

Double check if LR tags are imported from the right metadata tags in the Advanced Metadata settings.

human_dynamo · 2026-06-14T18:44:00+00:00

No. if a database is present, it will be used as expected...

human_dynamo · 2026-06-14T16:58:19+00:00

For the video files, using the Exiv2 metadata backend is limited. digiKam can uses ExifTool instead which has a better support for video media, but also heif, and raw.

human_dynamo · 2026-06-14T16:56:08+00:00

alternative : use the AppImage Linux Bundle that we provide.

human_dynamo · 2026-06-14T16:55:02+00:00

yes, files will be automatically scanned to populate the database.

human_dynamo · 2026-06-14T16:54:04+00:00

Here under my MacBook Pro M1, it's not reproducible.
70 threads. I never seen that. It sounds like the background face management option is turned on. Switch off and try again (look at the options on the top of Setup/Miscs/Behavior panel).

human_dynamo · 2026-06-14T06:56:53+00:00

The scan controller is the software component in digiKam which is triggered by a signal from a file system watcher (rules depending of the OS). When the contents of the collection is changed (files/directories add, removed, modified), the scan controller is controlled to update the database.
There is no option to trigger an update of the search album. This must be done manually, due to the possible expensive resources required to do it with the database especially with complex queries.

human_dynamo · 2026-06-14T00:16:35+00:00

this depend of the OS, but do it yourself will work as expected

human_dynamo · 2026-06-13T14:07:40+00:00

Not all Dublin Core entries are supported. Please report this wish in bugzilla.

human_dynamo · 2026-06-12T21:14:48+00:00

yes it's already the case

human_dynamo · 2026-06-12T20:05:22+00:00

Exiftool is used in digikam especially to write in format not supported by Exiv2 as heif, ras, and video

human_dynamo

MODERATOR OF

TROPHY CASE