The tools in darktable are more esoteric. Lightroom has a lot of its choice/sequence of tools "pre-baked", and there's a lot of wisdom in its choices. Unlike Photoshop, which is primarily a pixel-based editor, both Lightroom and darktable tend to work on the image in aggregate, with tools which are particularly useful to images created via a lens and digital sensor. This is especially true in darkatable v3, which allows re-ordering of of the various algorithms (also known as the pixel pipe) which work on an image. But it is like Photoshop in that it allows a great deal of volition in what happens to the image. Like Lightroom, darktable handles collections of images and allows applying a recipe of alterations to tune up each image. Numbers on controls can't be entered manually, so if you need some exact value you should spend seconds on dragging sliders until you get what you want.Īny other photo software are way ahead of this editor in terms of UI and performance, so I don't understand why this one gets so much attention. Slider knobs are ridiculously small and hard to grab and drag. Meanwhile devs are spending time on css driven UI.īut UI is also unusable: it's very compact and many elements on a retina display are very close to each other, so I'm constantly miss-clicking them. Same with zoom: 24 mpix image takes 3-4 seconds to zoom in/out! Really? How this software is written that simple actions are taking so much time? Enabling OpenCL helps, but not so much: changing exposure takes up to second (yes, 3-4 times faster) and zoom still 3-4. I don't understand why changing exposure on my 16 core i9 macbook takes up to 2-3 seconds for 24 mpix image. Once a year I'm installing the darkroom and giving it another chance, but usually half hour later I'm deleting it. XMP files could be versioned with Git if duplicate files are a problem. The goal is to move file operations outside of Darktable where they can be automated in the shell. The other an inverted index of all the XMP documents. One which takes a list of XMP files and generates new XMP files based on Darktable's duplicate semantics. What I think I want is more tooling for operating outside of Darktable (I already ingest images from my camera with Rapid-Photo-Downloader). This breaks my tiered backup logic.or rather complicates reasoning about it beyond the number of brain cells I can commit to it. Practically speaking, local-sync doesn't work for me because it munges filenames. Particularly since duplicating a Darktable image only consists of a new XMP file there's little point in overwriting an existing one to save a few bytes. Disk space is cheap enough that I don't find an append only workflow cost prohibitive. That's probably never what I want in my workflow. Local-sync's is inherently mutable state semantics. The XMP sidecar files are the actual data records.well ok, so are the images but they're immutable. When it's deleted, rebuilding is 'simply' a matter of reimporting all the files. Functionally, it's an index over the XMP sidecar files. Even Adobe's Cloud.ĭarktable's database is not the single source of truth. It's anywhere the CAP theorem is relevant. The difficulty managing files across multiple machines is not unique to Darktable. I'd like to see more blog posts and pros offer these. There's one main website, but it's not really curated. The community around "styles" (presets) doesn't scratch the surface compared to Lightroom's. And you have to make sure all your directory structure and naming schemes are the same on all your machines. Should be noted that dragging files + their XLF's from temporary machine to primary machine wont import into the "database" for you. I have yet to find a workflow - with the "Local sync" feature, or simply moving files and their edit files across the network - that feels simple. Generally do initial edits on another and then move the files across. My use-case is I have a central database with all photos on one machine. Managing multiple databases across multiple machines. That said, pain points for me have included: As someone who doesn't want to lock my whole photo-processing pipeline into a subscription-based model for the rest of my life (Lightroom) it's by far the most powerful tool at my disposal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |