However, there may be some ideas or information that you can adapt to your own unique processing style. There is of course no ultimate workflow for processing RAW files. I originally wrote it for the Canberra Photographic Society. I make those now in darktable, used to be geeqie.This post is of interest to people who use cameras and process images.
#Add key words fastrawviewer full
Consistency is important when you try to find something later.įastRawViewer, which I now use under Wine in Linux, at basically full speed, is excellent for weeding out generally acceptable pictures, not so much for A/B style 'which one do I keep' decisions. a hierarchy of bee diseases for documentary shots taken for my wife.īecause the photo library used to be managed by Picasa, dates are still the last day of an event, because Picasa auto-created a folder with the current data on import. good ol' Picasa would think that the moved file is a new one. The reason is that the hierarchy is accessed by multiple tools (and users) in addition to darktable, and e.g. Once move into the structure above, I try to avoid moving files. One is for family photos, one for everything else.īoth follow a shallow yyyy/yyyy-mm-dd_event-or-content/ structure, sometimes subdivided below into days, sometimes with a subfolder for panos or focus/exposure stacks.īEFORE they go there, or even anywhere in darktable, I use FastRawViewer for culling, with a global 'rejected' folder, which I clean out from time to time. a set of pictures clearly belongs to one or the other, not both. I suspect I'm not using the full power that darktable has to offer - so I was wondering, from-camera-to-darktable, what sort of organisation and import process do folks like to use?I have two folder hierarchies - which likely could be three, but the point is they are disjunct, i.e. My archives are starting to get bulky - just now I do a "dump" from the camera/SD card to a folder, and then I import all of that into Darktable - go through and tag all the non-keepers for deletion, and then tag the rest of them by genre. What sort of organisation do people generally use for their folders and files in darktable? That means a lot less tagged images to sort through.
On the whole I only tag these edits and they lead me to the base archives.
Because my editing finishes with Gimp which is a "destructive" editor all finalised work is "exported as" to an editing folder for that month.
#Add key words fastrawviewer archive
These form my base archive and I guess it is defined as sorted chronologically. Having all these daily folders means there is not too many thumbnails in DT at a time. This makes for a bit of complexity but I group them monthly using the traditional folder hierarchy system (ie done by the operating system). So, in the background, do you keep all your photos in one folder with the tags stored in the metadata so that you can filter them that way, or do you manually sort them into folders?I use "Rapid Photo Downloader" which in it's default state (I think) creates daily folders. That said, loading got a little slow with some of the larger collections (when the collection itself contained a lot of images) - but it was nothing I couldn't deal with.
Interesting! My installation seems to be running fine despite having a lot of collections - which, to be fair, is part of the problem - as most of the collections are random file dumps.