| Summary: | Some proposals about face management | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | H.H. <cyberbeat> |
| Component: | Faces-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | davito9w, metzpinguin, michael_miller |
| Priority: | NOR | ||
| Version First Reported In: | 7.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.7.0 | |
| Sentry Crash Report: | |||
| Attachments: | Faces treeview | ||
|
Description
H.H.
2021-03-08 21:46:20 UTC
- sometimes it makes sense to rescan the "unknown faces" section, because the engine could be more trained for some faces. But then, already rejected proposals are made again, which is very annoying. In principle, all existing points have already been reported through existing bug reports. Face recognition only works well with faces detected by digiKam. Picasa faces have a larger cutout and will not work. Are you really using digiKam-7.2.0? In the tags tree, the thumbnails are in the middle, aligned with the thumbnail size, nothing is moved. It looks good to me. Maik I use the fresh digikam-7.2.0rc appimage. The faces are all recognized by digikam itself. You are right, because the faces have different width, it looks like the names are placed differently, but the are aligned correct. Perhaps it would make sense to display a light grey background+border for the previews to give them equal width? Sorry, that I duplicated some of the reports, and did not split it, but it was so much. I will have a look at existing reports, to check that. Created attachment 136509 [details]
Faces treeview
another possibility: choose a rectangular part of the original image for the preview-treeview if possible (so making the crop a bit bigger), even with the risk, to capture more part of another face. - when I type a letter into the auto-complete field, it often lists names which do not begin with that letter before names, which begin with that letter, that makes no sense to me. Well, the search when typing the name is a "contains" search. What if they only know the last name or only part of the name. We did a search with "starts with" and users immediately rejected it as bad. I look at the representation of the face thumbnails again. The distance in the left area is unfortunately also dependent on the widget style and is larger with Fusion than with my native Breeze style. We could remove the "people" parent tag that creates this space. But then face tags can no longer be moved into the main tree using drag & drop. Just take a look... Maik A contains search seems ok for me, I only meant the order: when I type "T" the list is like: Christoph Martin Thies Tarek It should be more like Tarek Thies Christoph Martin Or better (like said before) adapted by some probabilities, which could be: - face recognition probability - probability, how likely a face appears together with another face (from some collection statistics) - probability, how likely a face appears in a time-span / year / series / folder Such things could really speed up the workflow much Closing due to no response Sorry, but why did you close it? I also searched for some of the points in bug reports, and did not find any matching. I upgraded to version 8.6.0 and most points are still valid: - improving sorting drop down lists. I like the bold feature for used tags in this run, but I still think, if the faces are "mixed randomly", this is not enough. At least the (easy to implement) sorting names which start with the given letters before names which only include the letters in the middle would give much improvement. I made further suggestions. - jumpy "unkown faces" selection (especially when detection/recognition in progress) - no switch between face-preview and full picture mode for the thumbnails (the preview mode is not sufficient, because the horizontal view only shows 2 picture-previews on my screen) - no "and" selection for "display pictures with person x and person y" - different tag-preview widths (the tag previews should be cropped somehow, perhaps an option for that) Positive: face detection/recognition improved much, but especially for recognition, there is much room for further improvement |