![]() ![]() 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 |