Darktable 3.2.1
darktable.org
darktable.org
After switching to Linux I had trouble replacing CaptureOne, mostly because of its simplicity. Pretty much every setting has a sensible default, and making the most important changes to a photo (exposure, sharpening, noise reduction, levels, etc) can be done without being exposed to any overly-complicated UI.
For awhile, I switched rapidly between Darktable and RawTherapee, not really satisfied with either. Even after doing my best to learn the ins and outs of each, I could still make my photos look much nicer in 10mins in CaptureOne than in 30mins in Darktable/RawTherapee.
I settled on RawTherapee over DarkTable last month. It's still the case that I can't get as good results in RawTherapee as I can in CaptureOne (not because RT is not powerful, but rather because there are SO many knobs/switches/etc and it's hard to find the ones that actually do what I want).
The moral of this rant is, I'm exited to try this new version of DT, and hopefully I can finally settle on a RAW editor that only shows me the knobs that matter to me by default without making me feel like I'm playing with a 747's control panel.
I'm inclined to try RawTherapee and DarkTable again. Years ago I tried but they never worked as well as the proprietary alternatives.
Still miss my film simulations, though. They were great starting points when editing a big photo shoot.
I should give RawTherapee a try. The UI with Darktable is definitely its biggest disadvantage.
While I did keep a Windows VM for Lightroom for a while when I switch back to Linux from macOS (and could do the same for Capture One), it is just not worth the hassle, and loss of privacy with Darktable being so good.
But if you are happy with Capture One, and do not plan on switching your operating system anytime soon, I do not really see a reason.
Darktable has a better rendering engine, but only pixel peepers will notice, and the fact it is open source only matters to a limited amount of people, myself included, but might not matter to you.
Lightroom is simple - everything is in one folder. Capture one creates some kind of magical folder system and I’m unable to find anything.
What resource can help me understand its organization?
I put together a little guide [1] to FOSS for photography a couple of years ago that I think is still pretty relevant (happy to hear about anything I should update!), including resources for learning Darktable.
With lr it’s one click and the edited image appears in the strip.
It's fantastic and I now I prefer it to Lightroom (Although I haven't used the latest version of Lightroom).
That said I shot a model this week and went back to trying to use Dark-table to go over the results as quickly as possible, it was actually pretty efficient to rate the images.
(In an hour-long shoot I'd taken about 500 images, and it was painless to look at each RAW file and star the ones that I wanted to keep. I went through everything and ranked about 50 as three-stars, then after a bit of thought and coffee marked the 25 I was going to hand over to her as 5 stars which I could then later process and edit with rawtherapee afterwards.)
This got me interested. Care to elaborate?
Keeping my own structure is one reason why I don't use any software that won't work "in-place". So I chose rawtherapee because I can point it at a directory of raw images, get a set of JPGs out, and it won't try to move/file/organize them behind my back.
Anyway my structure looks something like:
/srv/
/srv/images/
/srv/images/2020
/srv/images/2020/08/
/srv/images/2020/08/05.Claire
/srv/images/2020/08/05.Claire/RAW
/srv/images/2020/08/05.Claire/JPG
/srv/images/2020/08/05.Claire/Results
/srv/images/2020/08/12.Sanna
..
Basically data-based, but I also create a ".info" directory beneath each per-person tree which will have: location=Blah
event=Random Shot|Birthday|Party|Event
date=05.08.2020
tags=model,claire,monochrome
theme=pirate
contact=phone-number|email|address
..
Then I have a shell-script that lets me search for all shoots which had a specific location, tag, name, or similar.I hope I don't start any flamewars, this is a genuine question. And I remember initially there was some statement that rawtherapee handled x-trans RAW files better but some other people said that because they use the same software it doesn't matter. I intended to write up a blog post on both of these at some point for people in the future who have these questions, but time is what it is I haven't had the time to sink into it to get an intimate understanding of both (I still have a lot of photos I need to go back and process generally).
[1]Admittedly have not put in the work of going through guides or anything it was just kind of fumbling around in the software.
edit: Didn't know asterisks italicized, though I should have... Replaces asterisk with [1] instead...
For me, a photo editor is a tool I am likely to use for years...and indeed, I've been using Darktable continuously and frequently for almost five years. I'm still learning how to better use and discovering new things it can do.
This is not in any way saying it is better than RawTherapee...though it has proven to be better for me when I have used RawTherapee over the past five years to see what it offers.
Mainly, for me it is Darktable gave me a workflow that let me work through a few hundred just taken images in a few hours the first time I sat down to work through a few hundred just taken images in a few hours and allowed me to constantly improve that workflow over the years to shave hours off of the few hours to fewer hours.
One of the big differentiators for me was Darktable's support of GPU hardware acceleration via OpenCL. Googling suggests RawTherapee has not added it and LightRoom only got support in the last two or three years...at least for operations in the pixel-pipeline.
Darktable doesn't really mirror Lightroom because as commercial software, Lightroom exposes less of the underlying mechanisms to appeal to a wider segment of the market. Darktable's UI is much more "mathy", e.g. the tab showing the order of applied modules in the pixel pipeline (and the use of "pixel pipeline" as an explanatory term and fundamental concept).
I don't find Darktable's interface intuitive, but it's very familiar at this point and that's good enough or maybe even better.
A few months ago, I tried to do a big comparison of RAW developers, maybe you'll find it interesting: https://bastibe.de/2020-05-01-raw-developer-comparison.html
What I learned from that is mostly that these are all massively complex programs that can't really be judged without investing a few months into them. But even at the superficial level that can be compared in a trial month, there are serious differences in how even the simplest tools work in all of these tools. And that many of them actually exhibit quite severe artifacts.
But Darktable and RawTherapee were among the best of them in terms of results. One truly does not need to invest money in a RAW developer if one doesn't want to.
If you don't already, head over to discuss.pixls.us for in-depth discussions of Darktable's and RawTherapee's inner workings.
The only downside is the workflow and interface. In my opinion every piece of software on the market now has adopted the wrong workflow in separating photo management from the edit screen, e.g. the light table/dark room split in darktable. The film photography workflow doesn't make sense to me in a digital world.
Apple got it spot-on with Aperture, and I will forever resent them for abandoning it. Its interface and flow were basically perfect for me. Everything being on one screen made it so quick to adjust lots of photos. Everything since has gone the route of Lightroom and I find it really annoying.
But, darktable is free and the tools are good. I can deal with it having the wrong workflow. It has helped me get back into photography again.
Same here. I don't even care how much it costs, I'd pay dearly to get a supported and updated version of Aperture. Whoever worked on its UI is worth their weight in gold and then some.
Disclaimer, I'm not a Lightroom user and have used Darktable exclusively for the last five years or so. I actually use the mac builds, which is hardly ideal given that OpenCL support on Apple is not great. Darktable definitely has lots of rough edges that make it less than ideal for some less experienced users to switch over to. While the UI has improved with this release, it is still quite complex. Many of the modules are not for the faint of heart and have steep learning curves. Simpler to use alternatives are available (there are usually multiple ways to do things in Darktable); some of which are explicitly intended for novice users. Most of the complex ones are awesome once you figure them out.
The highlight in this release for me is the improved integration between the exposure and filmic module. Both existed in previous versions and they were always intended to be used together. However, in the new version they finally replace the base curve as the default way to do tone mapping. The new default scene referred mode is basically about these two modules being turned on by default and the base curve no longer being used by default. I noticed already with 3.0 where I manually configured my defaults to do the same that this reduced the amount of work I had to do. Usually, I do some minor tweaks to the grey point with the exposure module and then finish the job in filmic. In 3.2, these seem to do a better job out of the box than in 3.0; even for (deliberately) under exposed photos. If it is too dark, you simply add a few stops in the exposure module and filmic dynamically updates the black and whitepoints. So instead of blowing out your highlights, it actually brightens the grey-point while compressing blacks and whites in a way that makes sense. Unlike the base curve, this is dynamic and unrelated to pre defined camera profiles for what would constitute a good base curve for a camera that you get with the old basecurve module. I never really got usable results with that.
I ended up deleting my settings and presets to get the new defaults in 3.2. If you upgrade from an older version and want to benefit from the new & improved defaults, you may want to do the same. I noticed when upgrading an old 2.x version on my Father's laptop that doing this may also be needed if it fails to start because of changes in its internal db (he was still on 2.4). Unfortunately it did not fail gracefully and I had to drop to the command line and rm -rf the old files. Stuff like this is exactly the kind of rough edges that make this product still a bit of a hard sell for less experienced users.
A lot of thought went into the last few releases and it shows.
Thanks to Filmic and the Tone EQ, we can actually edit landscapes without these issues.
Or sunsets without false-color rings around the sun. Or the majesty that is Color Zones...
It might be better to use the URL about the release: https://www.darktable.org/2020/08/darktable-321-released/ (rather than the "news" page)