https://bugs.kde.org/show_bug.cgi?id=399923
--- Comment #111 from caulier.gil...@gmail.com --- Even if digiKam use PGF to store thumbnails in database, we have plenty of codec usable as alternative. The code is here: https://cgit.kde.org/digikam.git/tree/core/libs/threadimageio/thumb/thumbnailcreator.cpp#n758 The switch to the right codec depends of the format recorded to the thumbnail database schema at DB creation. If you compile digiKam yourself, the magic line to touch is located here: https://cgit.kde.org/digikam.git/tree/core/libs/threadimageio/thumb/thumbnailcreator.cpp#n769 The storage of thumbnails is always forced to PGF. Just use another one as PNG for ex. Of course the thumbnail database size will grow more quickly that PGF as there is no wavelets compression in PNG. The possible formats as listed here : https://cgit.kde.org/digikam.git/tree/core/libs/database/thumbsdb/thumbsdb.h#n48 Note that JPEG do not support alpha channel, and cannot be used everywhere, but for JPEG or RAW photo it's fine. I don't recommend to use JPEG2000... Before to change this line of code, make a database backup before ! recompile code and before to run, remove the database sqlite file for thumbnail. Only this one must be affected by this change. Start digiKam, the thumbnail database must be recreated from scratch. Start to navigate in album, thumbnail must be generated and appear in icon-view. The cache mechanism must be active when you switch to another album and go back to previous one, the thumbnails already calculated and stored in database must appear immediately. Now run the face management again, all look if stability is improved. When you complete the test, revert the source code line changes and recompile. restore the database backup done previously. Voilà Gilles -- You are receiving this mail because: You are watching all bug changes.
