Facial recognition isn't working

[Michael Miller]

Hi Robert,
You have to tag a face or two for each name.  digiKam will use these faces to find similar ones and present them as suggestions.  It’s up to you to approve to reject the suggestions.

Cheers,
Mike

On Apr 13, 2025, at 7:01 PM, robert lindsay <robert.lindsay at gmail.com> wrote:

Ok i did check both items and saw a new recognition.db file created. I did NOT have any faces tagged with names. I thought that was what this was all for

On Sat, Apr 12, 2025, 7:04 PM Michael Miller <michael_miller at msn.com<mailto:michael_miller at msn.com>> wrote:
Hi Robert,
It looks like the face database isn’t trained.  I see digiKam detected over 4700 faces, but it couldn’t match those faces to a name.  This is typically because the face database isn’t trained.

Did you go to Tools->Maintenance->Detect and Recognize Faces and check rebuild all training data.

Also, you do have some of the faces tagged with names, yes?

Cheers,
Mike

On Apr 12, 2025, at 6:03 PM, robert lindsay <robert.lindsay at gmail.com<mailto:robert.lindsay at gmail.com>> wrote:

forgive me for the delay in replying. I thought I sent this out thursday, but apparently not. I deleted recognition.db. reran everything, still no joy. Attached is the log file

On Sun, Apr 6, 2025 at 10:21 PM Michael Miller <michael_miller at msn.com<mailto:michael_miller at msn.com>> wrote:
Hi Robert,
The problem is the face DB is failing the upgrade step.  The easiest option is close digiKam, and then find a database file called recognition.db and delete it.  If you go to Settings->Database you should see the directory name that contains recognition.db. When you restart digiKam, it should create an empty recognition.db in the correct format.  Then in digiKam go to Tools->Maintenance->Detect and Recognize Faces, and rebuild all training data.

You shouldn’t lose any face data be deleting the recognition.db because all the data will be rebuilt from digikam4.db.

Cheers,
Mike

On Apr 6, 2025, at 7:45 PM, robert lindsay <robert.lindsay at gmail.com<mailto:robert.lindsay at gmail.com>> wrote:

weirdly what you suggested didnt work, but this is what did
export QT_LOGGING_RULES='digikam.*=true'




On Sun, Apr 6, 2025 at 8:10 AM Michael Miller <michael_miller at msn.com<mailto:michael_miller at msn.com>> wrote:
Hi Robert,
Unfortunately, that didn’t work quite right.  Can you please re-run the steps, but this time please type this line by hand
export QT_LOGGING_RULES=“digikam"=true”

The quotes got translated to something “prettier”, but aren’t recognized by digiKam.  You can see it in the line
qt.core.logging: Ignoring malformed logging rule: '“digikam*=true”'

It didn’t give me all the debug information I needed.

Also, these lines are concerning:
QObject::connect: Cannot queue arguments of type 'MLPipelinePackageNotify::Ptr'
(Make sure 'MLPipelinePackageNotify::Ptr' is registered using qRegisterMetaType().)
digikam.metaengine: ExifTool is not available to load metadata...

The first two lines don’t appear in my MacOS or Linux runs.  Gilles or Maik, do you have any ideas?

The ExifTool line is concerning if you have use ExifTool enabled for reading/writing metadata.

Cheers,
Mike

On Apr 5, 2025, at 11:09 PM, robert lindsay <robert.lindsay at gmail.com<mailto:robert.lindsay at gmail.com>> wrote:

the log was only 4k so I'll justpaste it

2025-04-05 17:48:48.811 digikam[29682:24188837] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
digikam.metaengine: ExifTool process cannot be started ( "/usr/local/bin/exiftool" )
qt.qpa.fonts: Populating font family aliases took 94 ms. Replace uses of missing font family "Sans Serif" with one that exists to avoid this cost.
kf.config.core: Watching absolute paths is not supported "/Applications/digiKam.org/digikam.app/Contents/Resources/digikam/colorschemes/darkroom.colors<http://digikam.app/Contents/Resources/digikam/colorschemes/darkroom.colors>"
kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
kf.windowsystem: Could not find any platform plugin
QObject::connect: Cannot queue arguments of type 'MLPipelinePackageNotify::Ptr'
(Make sure 'MLPipelinePackageNotify::Ptr' is registered using qRegisterMetaType().)
qt.core.logging: Ignoring malformed logging rule: '“digikam*=true”'
2025-04-05 18:03:18.637 digikam[29937:24201045] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
digikam.metaengine: ExifTool process cannot be started ( "/usr/local/bin/exiftool" )
qt.qpa.fonts: Populating font family aliases took 86 ms. Replace uses of missing font family "Sans Serif" with one that exists to avoid this cost.
kf.config.core: Watching absolute paths is not supported "/Applications/digiKam.org/digikam.app/Contents/Resources/digikam/colorschemes/darkroom.colors<http://digikam.app/Contents/Resources/digikam/colorschemes/darkroom.colors>"
kf.xmlgui: Unhandled container to remove :  Digikam::DigikamApp
kf.windowsystem: Could not find any platform plugin
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QObject::connect: Cannot queue arguments of type 'MLPipelinePackageNotify::Ptr'
(Make sure 'MLPipelinePackageNotify::Ptr' is registered using qRegisterMetaType().)
digikam.metaengine: ExifTool is not available to load metadata...


On Sat, Apr 5, 2025 at 2:53 PM Michael Miller <michael_miller at msn.com<mailto:michael_miller at msn.com>> wrote:
Hi Robert,
Can you send us a debug log? To generate a debug log file on a Mac, follow these steps:


  1.  Open Terminal
  2.  In Terminal, type this line: export QT_LOGGING_RULES=“digikam*=true”
  3.  In Terminal, launch digiKam with this command (all on the same line): /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam<http://digikam.app/Contents/MacOS/digikam> >> ~/Downloads/digikam.log 2>&1
  4.  Run a face scan like normal
  5.  Exit digiKam
  6.  Open your Downloads folder in finder
  7.  Find the digikam.log file, and right-click on it and select “Compress"

Send us the compressed log file and we’ll take a look.

Cheers,
Mike

On Apr 5, 2025, at 2:28 PM, robert lindsay <robert.lindsay at gmail.com<mailto:robert.lindsay at gmail.com>> wrote:

When i start the search on a small subset of my pics (roughly 1000) I get the message it's starting the scan. After 20 minutes it still says its at 0% then eventually it just ends, no faces are found no option to tag. I'm on a intel processor BTW

On Sat, Apr 5, 2025, 12:44 PM Michael Miller <michael_miller at msn.com<mailto:michael_miller at msn.com>> wrote:
Hi Robert,
Can you please give us more information? What exactly do you mean by it isn't working? Is it not detecting faces in images? Is not matching unknown faces to tagged faces? Is face recognition enabled in the download screen?

Face recognition works great on MacOS Sonoma. I'm a Mac guy, too, and I wrote it using an M1 MacBook Pro running Sonoma.

Cheers,
Mike



Sent from my T-Mobile 5G Device



-------- Original message --------
From: robert lindsay <robert.lindsay at gmail.com<mailto:robert.lindsay at gmail.com>>
Date: 4/5/25 11:43 AM (GMT-05:00)
To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users at kde.org<mailto:digikam-users at kde.org>>
Subject: Facial recognition isn't working

Digram 8.6 on mac Sonoma





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20250414/d17a5364/attachment-0001.htm>