Having all our processing as gegl operators it should be straight forward to hand all of the darktable processing over to gimp which can carry on with editing the file and passing the result back to darktable. Sounds familiar? Once that is about to happen we can resurrect the use of gegl in darktable (we actually had it once, but it didn’t work well).
This will bring two features (besides others): non-destructive editing and high bit depths. GIMP is currently moving to gegl as the new underlying core. However, what happens if you want to change the processing in darktable afterwards (remember, non-destructive editing)? All your work in GIMP is useless now. Well, we would have to export the image and tell GIMP to open it, since plain image files is the only common language these two applications speak. “What are the consequences?” you might wonder. None of the operations (with a few exceptions like layer creation, …) are non-destructive, and about bit depth in GIMP has been written enough. The second nice thing in darktable is that we work with high bit depths (32 bit floating point) to get the best possible result. This list can be changed afterwards without negative side effects since those actions can just be recomputed. What that means is that you never edit the actual data in your raw file, but “record” a list of actions (the history in darkroom mode and the XMP files) which shall be executed to get the final image. First of all, every action is done non-destructive. Well, to understand why we don’t have it I have to stress two features of darktable. The arguments of those requesting the button are along the line of “$PROGRAM has it, so it shouldn’t be hard to do” and “I really need to do some small retouching, so it would save me lots of time”. Everytime I answer more or less the same. Every now and then the question arises why we don’t have a button in darktable to open the current image in GIMP.
0 kommentar(er)
