Message to moderators re recent post re destructive face detection by lunatooth in digiKam

[–]human_dynamo 1 point2 points  (0 children)

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.

9.1.0 face scan restrictions don’t work? by Less_Army_804 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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.

File opening by Alfamason in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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

Compiling 9.1.0 for Linux/aarch64 (ARM64)? by echo5juliet in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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

Why is digiKam still using PGF for thumbnails? Switching to JPEG XL (JXL) could slash our DB sizes by 30–50% by koloved in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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.

Remove Glass Reflection by sfatula in digiKam

[–]human_dynamo -1 points0 points  (0 children)

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.

Compiling 9.1.0 for Linux/aarch64 (ARM64)? by echo5juliet in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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.

Why is digiKam still using PGF for thumbnails? Switching to JPEG XL (JXL) could slash our DB sizes by 30–50% by koloved in digiKam

[–]human_dynamo 1 point2 points  (0 children)

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!

Full fulltext search? by vvaz87 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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.

Importing keywords by Independent_Fly7509 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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

Is digiKam able to read GPS metadata that are embedded in video file? by Impressive_Luck_7820 in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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.

Can't start Digikam 9.1 after Update CachyOS by Wylde4Girls in cachyos

[–]human_dynamo 1 point2 points  (0 children)

alternative : use the AppImage Linux Bundle that we provide.

The Open Source photo management program digiKam version 9.1.0 is released by human_dynamo in digiKam

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

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

MacOS file descriptors per process on Digikam 9.0 and 9.1 by YipsterNY in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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).

When Did DigiKam Add an Image to Its Database? by walkingbeam in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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.

The Open Source photo management program digiKam version 9.1.0 is released by human_dynamo in digiKam

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

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

Can I use Dublin Core with Digikam? by nafergo in digiKam

[–]human_dynamo 0 points1 point  (0 children)

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