On Mon, 18 Feb 2019 22:26:12 -0500, =?UTF-8?B?xaBhcsWrbmFz?= wrote: > On 2/18/19 8:19 PM, Robert Krawitz wrote: >> Thanks -- and you see why I harp on this; I need to squeeze everything >> I can out of the workflow. Over the past few years, I've put a lot of >> work into performance tuning KPhotoAlbum to squeeze time out of image >> loading and that, and anything that adds a few seconds per image is a >> real problem for me. > > Hmm... what's all the rush? :)
So it looks like what I'm doing is using a script to parse the RawTherapee sidecar files and then use ImageMagick (convert) to process them. It's very fast (it did 400 files in about 80 seconds on my Xeon E3-1505Mv5) since it uses the full concurrency of my CPU. The script was a pain to get right; all of the different bounding boxes made for a lot of confusion, and ImageMagick's coordinate system is a bit quirky. I also have a watermark step that adds 66 seconds to the same set of photos; no doubt if/when I combine all of that into one it will be even faster (and need only one command). But there's still one thing I do like about Darktable's crop tool, namely that it's shared with the rotate tool so I don't need to type an extra keystroke to bring up the rotate tool. It sure would be nice to have all of that in one package, though :-) There are definitely times I put a lot more effort into individual images; it's just this isn't one of them. But even for shooting, say, fireworks (which does take a good bit of processing), the crop tool in Darktable is awkward. -- Robert Krawitz <r...@alum.mit.edu> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
