Bug 497791 - Unwanted face recognition function in preview mode when face management is disabled.
Summary: Unwanted face recognition function in preview mode when face management is di...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Workflow (show other bugs)
Version: 8.6.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-22 18:57 UTC by maderios
Modified: 2024-12-23 20:26 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maderios 2024-12-22 18:57:33 UTC
This is a wish for all those never use face recognition like me:
I disabled all about "face recognition" i could but, when  I want to preview full raw NEF image (human head) by  clicking thumbnail, this annoying message appears with a square "who is this?" 
It happens only with NEF files. 
This message didn't appear in the past. I think it should be only optional.

Digikam git version
Arch Linux system
Comment 1 Maik Qualmann 2024-12-22 19:10:55 UTC
If you have disabled the download of face models and there is no model data in "~/.local/share/digikam/facesengine", digiKam cannot detected faces. Could it be that these faces are part of the metadata of your images/sidecars? Current smartphones or cameras also include face detection and may already mark the faces in the images. Displaying these face rectangles is a desired behavior because they are part of the metadata of images.

Maik
Comment 2 maderios 2024-12-23 16:38:18 UTC
I don't know where these faces rectangles come from. It concerns only two NEF files. Issue doesn't happen with my  other NEF images with faces. I got rid of these rectangles by removing sidecars then, I could not reproduce issue by adding same tags/sidecars. I checked camera detection face: it is not activated on my camera (NikonD750). The good news is that the problem doesn't come from Digikam.