SUMMARY Following the bug entry 427907 where Maik exlained me what the problems were with import from picasa3 where digikam does not correctly take the faces out of the metadata i went to try to import part of the photos I have (more than 600Gbyte, about 150'000 photos. The original scanning took Digikam almost 24hours without being able to open digicam...just wait time. So first comment here. I do not have an issue with this but probably many users that just want to try digikam will be scared away from the SW and go for ACDSEE or something else.... the reason why is that it blocked my computer for a full day (every operation was slower on the computer and it has ssd disk and good processor): So could you not improve it and do the scanning in the background like PICASA3 does. So at least the people can browse their photos immediatly. User Experience would be 100 times better). Next when the scan was finished, again NO Face rectangles were recognised at all out of the PICASA3 faces. All the names of the people were in the list of persons but no face rectangles at all. So same as my first experience. I had to reread the metadata for each photo. This was my input for this big bunch of photos. But basically, making Digikam do the scanning and then face recognition work in the background would make it a great SW like Picasa3 was. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION see bug 427907
A test here when importing a few thousand images under my Windows 10 VM in various ways shows no problems. All metadata and face rectangles were correctly scanned by digiKam. I also suspect an external cause such as anti virus programs that block digiKam in the scanning process. Which anti virus program do you use? Maik
Hello Maik, I am not sure to understand the relation between the antivirus and Digikam but I use Norton as an Antivirus and Zonealarm as firewal. Best eregards Laurent
Hi Maik, I guess using a VM and the real W10 might not be the same. Still no clue why it did not import the picasa3 faces? thanks Laurent
Hi Maik, I tried to move one test directory to a sdd hd internal. Of course it went about 2-3 times faster than the normal hdd. But also all the faces were imported properly. Could it be that Digikam just skips reading the metadata of certain files or that the DB SQlite just times out and skips the entries? Best regards Laurent
No images are skipped when the drive is slow. Maik
(In reply to Maik Qualmann from comment #5) > No images are skipped when the drive is slow. > > Maik thank you Maik. Still not understanding why reading the same directory from the HDD it skips faces and from the SDD it does not?
Which kind of file systems do you use on SDD and HDD. It's the same ? Do you have any extra sidecar file stored in album from on disk and not from the other one ? Check with 'ls -al' on both devices... Gilles Caulier
Hello Gilles both disks are NTFS disks. For the sidecar I do not know. Actually the command ls -al, isn't this a unix command? I am on W10. But I would say no, as the files come from Picasa3 where I used the option "write faces to xmp". So the data is in the photo itself. Am I wrong? Currently I still keep using both SW, and Picasa3 because it is so much quicker than Digikam for the tag and face features search that I use a lot. Digikam is great too and I will move there slowly and especially when the smaller faces are detected like it will be as Maik explained. Hope this helps. Kind regards Laurent
@Lrnt digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier
@Lrnt, This problem still reproducible with the new digiKam 8.2.0 pre-release Windows installer available at usual place: https://files.kde.org/digikam/ This new bundle is based on last Qt framework 5.15.11 and KDE framework 5.110. Thanks in advance Gilles Caulier