Hi y’all. I’ve recently started looking at getting back into running Linux again as a main OS. With Proton and Steam all my gaming works fine. And with so many web apps those are all cross-platform anyways.

However the one application which I have not yet found a good alternative for is Adobe Lightroom. I’ve found Lightroom to be simply the best experience for managing a large (100k+) catalog of photos. I’ve really tried to get into using Darktable but while it can do a lot, I’ve found the UX to be incredibly bad and painful to use.

Is there a photo workflow app which is relatively simple, efficient and easily usable that lets me manage my photo library, can do some basic editing (levels, crop, etc.) and runs on Linux? Thanks.

  • Ada@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    13
    ·
    edit-2
    2 days ago

    Digikam was my replacement for photo management and tagging. And darktable for editing. You can launch darktable from the Digikam catalogue, so it’s pretty smooth.

    It took me a while to get used to darktable, especially the masking, but I genuinely prefer it to lightroom now.

    You can also use other editing apps, like Gwenview, etc for quick and dirty edits. The only thing I’ve had no luck with are things like Topaz and DxO. They won’t run on Linux and don’t really have equivalents.

    • tychosmoose@lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      ·
      2 days ago

      Same here. DigiKam and darktable.

      Getting color balance with raw in darktable took quite a while for us. It was helped by using a Color Checker Passport in a few shooting conditions to use for reference and calibration. Once we got past that darktable has been great.

      • MangoPenguin@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 days ago

        Is there some explanation as to why Darktable is different from every other RAW editor out there? It’s so complex to use even for the most basic stuff, and nothing ever looks quite right.

        • tychosmoose@lemm.ee
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 day ago

          My understanding of why is that it relates to their change to a scene-referred workflow. Up to v3, darktable used a display-referred workflow like other programs. In that model the image you start with is mapped on a tone curve from the start where 0 is pure black and 1 is pure white, and the midpoint is set to midway between. This is all from the standpoint of what your display can render. The scene-referred workflow in v4 doesn’t do that. All the tones are mapped in an unbounded and uncurved way. So images look flat, but you’ve retained maximum data, so you have more to work with. The developers assume that you want control and maximum fidelity. There’s a better explanation in the intro of the documentation. This impacts everything - especially the color balance.

          One of the problems is that all of the display-referred tools remain as modules in the interface, and some are even used in the base processing, but you’re not supposed to use them. At least if you want to do things the ‘right’ way. We created a custom panel that has 90% of what we regularly use (shared UI with my partner). That plus creating some presets that work well with our cameras has made it very quick to get a satisfying output in a minute or less.

          Honestly, if you want to do minor tweaks to a RAW and mostly want what the out of camera JPEG looks like, there are much easier tools. If you at least occasionally deal with really challenging photos, or you want to get creative in the processing of some of your RAW images, darktable opens up a lot of possibilities, while being free and open source. So I think it’s worth the effort to learn. Shooting with a colorchecker helped us get the presets we wanted for a variety of shooting conditions.