Version: 0.10.0 (using 4.2.4 (KDE 4.2.4), 4.2.4-6.fc11 Fedora) Compiler: gcc OS: Linux (i686) release 2.6.29.6-213.fc11.i586 Hallo I usually take pictures as jpg and raw (Canon cr2). If I start a search for double pictures all my pictures are shown as most are available as jpg and raw. So it is almost useless. It would be nice if I can configure the extensions to be used for double checks. Thanks for the fine application btw. Martin
I think in general it would be nice to apply some of the same filters to fuzzy searches that are available to the normal search. Martin has given one very good example. I'd like to be able to filter on date ranges or albums. I've got some duplicates in my collections (imports from my wife's computer, etc.) that I'm aware of. I just haven't taken the time to resolve them. I'd like to be able to search for duplicates with creation dates in the current month so I can prevent my issue from getting any worse, or for dates I know there are duplicates so its easier to tackle the task in smaller chunks.
In digiKam 1.0.0, you can limit find duplicates to albums and tags and set a threshold: http://farm4.static.flickr.com/3476/3951141403_79ac47306e_o.jpg Maybe this is enough in your case? We can think of adding more control in the future, but for digiKam 1.0.0-final this will not be done anymore.
This seems to be step in the right direction. As I usually have my raw and jpeg pics in one album this is not much of help, but I can tag all raws and jpegs with separate names, so the search is limited. BTW: After I searched for duplicates in my whole photo collection, the startup was verrrry slow. after deleting the database (and rereading all photos) start was much faster. So a database cleanup button may be nice as well (but this another story). Martin
No need to delete the whole database, only the find duplicates search. I agree we should add such a button, because a huge search result really seems to slow down the startup time.
*** Bug 280760 has been marked as a duplicate of this bug. ***
Currently (5.4.0), it is possible to filter by album and tags. In 5.5.0, it will be possible to restrict the result set even more. For example, if you have an image I in Album A, you can exclude all other images in Album A as potential duplicates of image I. So, if you have your raw images together with the jpeg pictures in one album, they are filtered out. By the way, 5.5.0 will also come with database cleanup. But this was not the problem for your start-up. Should this file stay open?
I think yes, as resolved fixed and fixed-in = 5.5.0. If the file need to be re-open by users, this is always possible. Don't forget to patch NEWS file of course. Gilles
Git commit c900075b8d938d81c2cf8d9e6b2d2ce83439fde5 by Mario Frank. Committed on 28/02/2017 at 15:44. Pushed by mfrank into branch 'master'. Update the news. 1 bug is fixed by multiple changes in digikam in history. FIXED-IN: 5.5.0 M +2 -1 NEWS https://commits.kde.org/digikam/c900075b8d938d81c2cf8d9e6b2d2ce83439fde5