Summary: | A single face is detected twice | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Milan Knížek <knizek> |
Component: | Faces-Detection | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 2.0.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.5.0 | |
Attachments: | Multiple detection of a single face |
Description
Milan Knížek
2011-01-08 21:10:22 UTC
Created attachment 55746 [details]
Multiple detection of a single face
We do have overlap detection, only though when one face is already set and a new one is added. For faces added in one run, there is overlap detection in libface IIRC. These do overlap, but not so much. The problem: Which face is the right one? Impossible to know! If the lower frame, probably fooled by the moustache, is added first, we'll have made a mistake. I get your point, Marcel. Then it is a question, what is easier from the user's viewpoint: (a) digiKam keeps both detected faces (though overlapped) and the user manually removes one of them as a false positive or (b) digiKam chooses the best fit and in case it is the wrong one, the user moves the frame to better fit the face. I would probably opt for the latter solution, since there are chances that digiKam did the right thing and user does not have to interact at all. I need to check if we can get "scoring" information from libface. For the normal detection, there is no such information; but maybe from the verification state. Milan, it still valid using digiKam 2.4 ? Gilles Caulier Thanks for pushing to re-test, the bug does not appear anymore with today's GIT (on the same test album). (It still existed in 2.3.) |