Originally posted by GUB Trying to get my head around this - it has nothing to do with the history list - ie if you go back to an earlier point in the history you delete all that comes after it. But if say your first step was say colour temp - then you did a heap of other things - then went back to readjust colour temp it would reset the earlier attempt rather than add to it. And so for each tweak of the tone curve you may do it will boil down to one maneuver . This is distinct from Gimp or PS where as each attempt would be additive. Have I got it?
I don't use Darktable, but if it's non-destructive I guess it works in a similar way to Lightroom.
The way I understand it, the software stores a list of parameters for all the adjustments you have made to an image, and each time you load up the image and make further adjustments it applies the full list of adjustments to the original image, which remains unchanged.
For performance reasons, I think most software stores a cached copy of the modified image often at lower resolution, but the pixels of the original are never altered.
It's a bit like the difference between a vector graphic (eg a font) that describes HOW to draw an image, and a bitmap image such as a photo that describes the individual pixels. This is somewhere in between, it records a set of operations to be applied to a bitmap image.
The other side of this is if you want a permanent record of your edit that can be recognised outside of the software you used to do the edit, you need to export the image to produce a copy that has all your edits baked in to the pixels.
Even Lightroom and Photoshop, which are pretty tightly integrated do this; if you choose to edit a Lightroom image in Photoshop, from Lightroom, it will create a TIFF file, as Lightroom recognises that Photoshop can modify the pixels, so won't send the original image to Photoshop.
I'd imagine Darktable and Gimp probably work together in a similar way.
It's actually why I started to get excited about DxO. I use Nik effects, and I can use them directly from Lightroom, but because Lightroom doesn't recognise Nik edits, it creates a TIFF file any time I send an image to Nik, and all the individual list of adjustments are lost, they're just baked into the pixels in the TIFF, and when the image comes back from Nik, the same applies.
With DxO, it looks like it's possible to do both Lightroom type adjustments and Nik type adjustments and have all the edit parameters retained, so if I change my mind on anything, I can go back and tweak it without having to redo a whole major edit, and without having to end up with a massive TIFF file.
---------- Post added 10-30-19 at 09:54 AM ----------
Originally posted by microlight
As you can see, unless I need a specific effect or technique, pretty much all my workflow exists in Bridge/ACR/Photoshop.
Hope this has helped a little.
In my camera club, quite a few people use Lightroom, but one person refuses and swears by Bridge/ACR, but in the end Lightroom or Bridge/ACR actually produce the same edits. Lightroom is essentially a management tool with ACR baked in, so all the raw adjustments available are exactly the same as what is available int ACR.
Bridge and Lightroom each have their pros and cons depending on how you want to work with images. Bridge doesn't require you to import images, but then it also doesn't allow you to search for offline images, and I think Lightroom's batch processing of raw edits is better, however the way I've seen a lot of people try to use Lightroom, honestly Bridge/ACR would be a better choice.
Basically if you don't want to use Lightroom's image management features, and want to do raw adjustments to individual images Bridge is quicker, as it just browses folders, and provides many, though not all of Lightroom's features.
I do use the full image management features of Lightroom so find it useful.