10 thoughts on “digiKam 4.0.0 released!

    • The part that he has done in Photoshop: Yes, no problem.

      But most of the work has been done in 3D programs – and that’s the wrong area for GIMP. Blender could do that, I think.

  1. It’s a matter of the right tool for the job at hand. digiKam is invaluable if you’re fighting to keep order between thousands or even ten of thousands of images and especially if you need to reliably filter and find them. As good as darktable is, it’s simply not up to this task.
    But if you found the images and want to process them (maybe in several variants) before starting Gimp, then that’s a different story. This is out of digiKam’s league and the realm of programs like darktable and Photivo (and a few others).

    • Are you sure that darktable is so bad at managing images? Where do you see problems?

      I have to test that, up to now there are only some hundred images in my collection.

      • One issue is simply speed. Switching between dirs holding a few thousand images each is very fast in digiKam but with the size of your collection growing changing film rolls in darktable gets slower and slower. At some point you have to wait several minutes before even the first thumbnail is displayed. And it’s not waitstates, darktable is burning cpu.

        Filtering for several tags at once and e.g. for a specific day in the calendar view is way easier to use. Also tagging a large number of images if you have many tags that have to be distributed is somewhat more “smooth” and faster.

        Another advantage is digiKams tight integration. The tags are available in other programs as well and if you have kipi plugins it will be able to use them.

        Last is the face recognition — but as I haven’t really used that up to now I won’t rate on this.

      • In my opinion Darktable is a really excellent image editor but for managing the photos it’s just a less-than-ideal solution. The UI is a little bit limited and inconvenient for tagging and searching tasks. Tagging the images is sometimes quite laborious. The list of available tags on the right of the light table shows only 5 of them (on my screen) and they are unsorted. So you have to scroll again and again to assign the tag of interest. I haven’t found out a way to do complex searches (searching for multiple tags for instance). In contrast DigiKam’s options for searching or selecting images seem to be endless. You can search for more than one tag simultaneously, search for ratings, filenames, image formats, image orientation, colour models, used equipment, subject distances, exposure settings, faces, geographic location and so on and you can combine several of these criteria. The time line is also great for finding images. Furthermore you can create fingerprints of each image. Thus you can do a fuzzy search: all images similar to a given one can be found. Finding duplicates is no problem either. Performance and speed of DigiKam is very impressive and its UI is well arranged. The only issue on my machine is the stability of DigiKam. It crashes frequently. No data is lost and when the software is restarted, everything is fine. I’m not sure that DigiKam is to blame for the crashes. Perhaps it’s a problem of my system configuration. On the other hand I like Darktable’s way to control the search for the used camera or the lens. While in DigiKam you have to type in the name of the used camera or lens (so you have to know the exact term) Darktable provides a list of all found bodies and lenses your images were shot with, so you just have to select one. Despite my general preference of DigiKam for image managing I love Darktable as the most exciting image editor!

        • digiKam crashes are mostly caused by locking failures (given that it’s not a genuine bug or the database got corrupted, which would be another cause for trouble). Reason is either lack of memory or an nfs home. Memory-wise digiKam is quite demanding, especially when new images are to be scanned. I’ve seen it using 12 or even more gb of resident memory when importing a new album. I think, when importing you should leave it alone and not do other things and it should be fine even with muss less ram. Nfs home is an issue many are not even aware of. When creating the database it’s explicitely stated it can’t reside on nfs and most people adhere to this. But while running digiKam used a socket file and pipes in your home, which would randomly break on nfs too. This has only now been fixed.

  2. Great Info, Rolf. I’m currently looking deeper into the capabilities of DigiKam. I’ve underestimated this software for a long time. Now I can say that DigiKam, Darktable and Gimp are The Magnificent Three of my workflow. Nothing more is needed. Each of these tools is amazing and none could be replaced by one of the others.

Anything to add from your side of the computer?