| Summary: | Face Matching | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Dec <digikam> |
| Component: | Faces-Recognition | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | caulier.gilles, digikam, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.0.0 | |
| Sentry Crash Report: | |||
|
Description
Dec
2023-03-04 23:07:28 UTC
to clarify, it is NOT the face RECOGNITion that is t6he problem (if anything it is too 'good': it is the name (Tag) matching that is dysfunctional Things to note for face recognition to work well: At least 5 meaningful faces should have been tagged by one person. Only faces whose face rectangles were also found and created by digiKam are recognized. Faces drawn manually or faces detected by other programs (Picasa or similar) are recognized poorly or not at all. Maik you do not seem to understand what i say or the actual ISSUE as i additionally clarified. face RECOGNITION is NOT the problem: that works exceptionally well it is the TAGGING that is PERVERSE! when you tag a face, it actually 'hides' all the same faces, and ONLY shows OTHER faces: it takes forever to actually find the SAME face again. the matching of the SAME face takes forever (after you have already tagged MULTIPLE!) - when in fact it should be amazingly easy and fast. in fact i have simply given up! it simply takes too long for something that should be very fast. it makes it like 'hide n seek' just perverse. it deliberately makes it as difficult as possible to find other same matches. it is like the algorithm is actually accidentality reversed the results I really can't imagine where the problem is at the moment. No other faces are hidden when a face is tagged. Please create a screencast of the problem, without it we can't help. Maik Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |