![]() And you have thrown away all the advantages of non-destructive editing. And besides the explosion of storage space you are still stuck with baked in editing, baked in color space, etc. And it turns my 3.85mb Olympus E-M10II 16mp JPEG file into an 83.5mb compressed 16-bit TIFF file. Some people suggest saving all the edited files to 16-bit TIFF files with the Lightroom editing baked in (sRGB or Adobe RGB or some other color space) which turns my 16.5mb Olympus PEN-F 20mp raw file into an 86mb compressed 16-bit TIFF file. On rare occasions I undo all the edits and start over, but mostly just a few changes to an already edited photo. I often go back to earlier edited photos and tweak them a bit. They all have keywords (tags), most have star ratings, many have color labels, many are in collections, etc. I have 112k photos in my Lightroom catalog: 110k out-of-camera originals + 2k scanned film files. I was using darktable 3.2.1 which was the release before the new 3.4.0 released a few days ago. I experimented with it this year by importing a few of my files along with their Lightroom XMP sidecar files to see what darktable would do. ![]() metadata (keywords (tags), star ratings, color labels, etc.).There are 2 different types of data to import: You can also read the 3.4 manual info about importing Lightroom XMP files here: Here is a 2013 article written by the developer about importing Lightroom XMP files along with image files into darktable: First, take a look at the following 2 links and then below you will see things I learned that are undocumented and I have never seen written about anywhere despite having searched, watching a couple of videos, etc. We'll see what happens.I will write about my experience playing around with the darktable import function that imports Lightroom XMP files along with images and tries to translate some of the data for use by darktable. The original raw file, the sidecar file and now thirdly, the LUT file. With LUTs there's the problem that now you need three files instead of two, to reproduce an image. I think some of the AGFA emulations you've already seen in some of my recent uploads. There's an absolute wealth of film emulations distributed as luts that I previously couldn't use via Darktable. Well now Darktable 3.0 has full support for LUT files, including these HaldCLUT png files. ![]() When that is selected, I do local adjustments and sometimes go deeper into curves to achieve local contrast ("Clarity" in Adobeland) and other things. Speaking of tone curves, the major reason to use tone curves for me are the film emulations by Joao Pedro Almeida. I still base most of my work on the default base curve and tone curves. What was introduced in 2.6, "filmic" to replace base curve when desired, is now obsolete and "Filmic RGB" is a rewrite of that feature. I don't think it works perfectly yet but I can't but wonder: is it allowed to have tools this easy? ![]() Not exactly Silver Efex but cool nonetheless. I'm not sure yet what to think about the feature but there's now a cool zone-system-esque module called "Tone equalizer" which defines 8 zones to the picture and you can manipulate them by pointing to something in the picture and wheeling your mouse to push or pull that zone. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |