Summary: | Albumfilter on Unknown faces does not work | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Marcel <maeseee> |
Component: | Faces-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | bugs.kde.org, caulier.gilles, maeseee, metzpinguin, michael_miller, stuporglue, W.Blankertz |
Priority: | NOR | ||
Version First Reported In: | 8.7.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Marcel
2020-09-04 14:05:09 UTC
The "Unknown", "Unconfirmed" or "Ignored" tags are "virtual" tags and are not actually added to the images like the normal tags. Therefore the filter does not work. You should activate the people view in the left sidebar and you can display all "Unknown" faces there. Maik Thank you for your answer, Maik. I know about this "Unknown" tag in people view. My problem is, that there are more than 10'000 unknown faces in my library. In previous versions of Digikam, the faces were organized in albums. Now it is just a huge set of faces and there is no way to look for new faces in a certain album. Ignoring all faces is no option. With each new version or parameter change of the face detection algorithm, new faces are found anyway. Filtering for this virtual tags would solve my specific problem. I'm not sure if it is so simple to implement. You could assign the tag "Unknown" to all 10,000 images in the People View. However, then (if active) this tag would also be written in the images, ie "people/unknown". That is the reason that the face engine does not do this automatically and these tags are only "virtual", but they can be assigned. But there is sure to be a way that we can add it to the filter. When there is more time again, I'll take a look. We are currently busy testing and stabilizing the students' new implementations that were programmed under the GSoC2020. Also note that digiKam-7.2.0 is a Beta 1. Maik Hi Marcel and happy new year, Can you check if digiKam 7.5.0 pre-release bundle available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Hi Gilles Thank you. I also wish you a happy new year. I checked the behavior again with a new version. Unfortunately it is still pretty much the same as when I reported it. I See that it is not that easy to solve as the filter must be applied to a virtual filter and not to one in the picture it self ( see comment from Maik). Anyway, I see it as a but as the filter option "unknown" is shown. One quick fix would be to hide that option but I definitely would like to see the filtered images. I tried to fix it by my own but did not succeed and in the resent months I was short in time. I changed my job and got a new child. Maik, i think this entry still valid with 8.0.0. Right ? Gilles Yes, the problem still exists. I want to add that it would be very nice to have a filter for Unconfirmed, Unknown and Ignored faces, as this allows more flexibility such as using the Timeline and Map interface with only these unidentified faces. If it is technically impossible to implement filtering on unidentified faces, then these entries should be removed/hidden from the filter interface. Currently filtering on unidentified faces is a clearly offered option, but it just won't work. Hi, The digiKam 8.7.0 pre-release for Windows have been rebuild from scratch today with many improvements and updates especially with the face management workflow. Please test with this version to see if the problem is reproducible. Link to download: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier Hoop, my last comment still valid for Linux of course... Hi Gilles I just tested this error with the newest pre-release version of 8.7.0. Unfortunately the error stills exists as described above and it is very simple to reproduce. Hope this helps. Thank you for your continues effort in this project. Marcel Thanks Marcel. Michael Miller is working on this topic for the next 8.7.0, so i would to have a zero point on the topic. Best Gilles Caulier Hi Michael, I move this entry to the Face Workflow section, as it's probably a dysfunction to fix in your current development branch. Best Gilles *** Bug 506255 has been marked as a duplicate of this bug. *** |