| Summary: | Manage face area position as persistent data in database accordingly with image manipulations | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Axel Krebs <axel.krebs> |
| Component: | Database-Faces | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | bugskdeorg.20.dimon3000, caulier.gilles, mario.frank, mike, spam-receiver |
| Priority: | NOR | ||
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
Marcel, Face area positions are not already stored as persistent in database ? Gilles Yes, it is always the tag (the person) and the area on the photo (In reply to Marcel Wiesweg from comment #2) > Yes, it is always the tag (the person) and the area on the photo Marcel is right. The face area is persistent in database. For every face, there is an entry with image id, face tag id and the tag region/autodetected face as absolute coordinates (x,y, width and heigth) to the specific image. Is this still valid? What behaviour is exactly expected? Mario, Imagine a photo with a face already registered as face tag. Open the image, and crop it. The face area is changed. The expected behavior is to recompute face area accordingly with manipulations. The can be a perspective adjustment, a flip, a rotation, a crop, etc. And this must be true also with BQM tools. So this can be a complex patch to do. Gilles Hello. Any estimates on this? Hi, Currently, all internal test tools for FaceEngine need to be ported as real unit-tests. After this stage, it will be more easy to check broken or missing features. I already ported all MetaEngine as unit-tests. This take few weeks of work and permit to identify and fix serious problems. The same must be done for FaceEngine. In all cases, i want to complete FaceEngine unit-tests before 6.0.0 final release. Best Gilles Caulier (In reply to caulier.gilles from comment #6) > Hi, > > Currently, all internal test tools for FaceEngine need to be ported as real > unit-tests. After this stage, it will be more easy to check broken or > missing features. > > I already ported all MetaEngine as unit-tests. This take few weeks of work > and permit to identify and fix serious problems. The same must be done for > FaceEngine. > > In all cases, i want to complete FaceEngine unit-tests before 6.0.0 final > release. > > Best > > Gilles Caulier Have the test tools been separated from productive code? What's he status of the face recognition & management feature? Maik, I suppose that entry depend of other bug 286529 where the face area must be updated in metadata if transform tools are processed on images. Right ? Gilles Maik, did you seen my last comment ? *** This bug has been marked as a duplicate of bug 286529 *** |
when detecting _several_ faces on _one_ pic, the position of _each_ face should be associated and stored ("somehow") persistent in absolute data. Reason: - if working on a pic, the pic can be divided. Up to know, the faces info stay with both pics- which is wrong, potentially. - if showing _one_ face of several, one still sees all faces names, even in this extreme case wher only ony face is visible in the observed area. Reproducible: Always Steps to Reproduce: 1. run face recognition 2. observe the above mentioned appearences 3. Expected Results: every face should have its own (persistent) position information