Changing an old habit

I'm a keen amateur photographer and have been since I was at school. Of course back then it involved smelly chemicals, strange lights and dark rooms. The expense and hassle of film eventually did it in for me and in 2000 I bought my first digital camera. After a series of increasingly sophisticated devices, back in 2007 I bought a Nikon D80 and soon thereafter I discovered that you can do things with raw camera files that have some analogies to the darkroom processing of my youth.

I'm a keen amateur photographer and have been since I was at school. Of course back then it involved smelly chemicals, strange lights and dark rooms. The expense and hassle of film eventually did it in for me and in 2000 I bought my first digital camera. After a series of increasingly sophisticated devices, back in 2007 I bought a Nikon D80 and soon thereafter I discovered that you can do things with raw camera files that have some analogies to the darkroom processing of my youth.

For most of the time since then I've used UFraw for processing my raw images, combined with increasingly sophisticated batch files to harass it into shape. It has increasingly frustrated me that UFraw doesn't do several things that are essential to processing most files, since once the image leaves that programming it usually ends up in an 8-bpp processing path. It seems to me that the saving the processed image into an 8bpp format like jpeg is the last step before leaving the image alone.

Of course this can't always be the case since sometimes a judicious use of the 'Resynthesizer' plugin can make some unsightly elements just disappear, or one needs to carefully apply some censorship to the 14 year old in the background so that the 7 year-old's parents can put the photo on the mantelpiece without worrying about what Granny will say about how much better children's manners were in her day.

I'm hoping too, that when I have grandchildren I'll be able to tell them that 'in my day we only had 8 bits per pixel, and we were lucky', but The Gimp isn't there yet, no matter how much promise Gegl seems to offer.

The thing that has particularly annoyed me is sharpening. UFraw doesn't, and as a result my workflow has either involved applying some blanket sharpening, much like the camera does, or moving the image into a second tool just to apply some sharpening.

This week has been particularly demanding, as the school asked me to 'take some photographs of the production'. So of course that's a thousand-odd photos that I want to do a cull down to a hundred or so, and then I want to quickly do justice to the good ones so I can move on to other stuff.

Well this time my frustration with UFraw hit that ceiling that got me to try something else. I've done this in the past, and found myself going full circle and ending up right back at UFraw with a few extra lines added to my script, but this time I tried rawstudio and in processing the 'can you do the class shots overnight please' test it produced much nicer results in much less time than I have ever been able to with UFraw.

So I've switched, and the more I use it the more convinced I am that UFraw will be getting uninstalled pretty soon.

That's not to say that rawstudio is perfect: it isn't. In particular it has some user interface failures that are kind of annoying to me, but they aren't enough to stop me using it. In fact I liked it so much that I immediately had to pull the nightly repository and build that, just to get the new saturation handling.

The user-interface niggles that do get to me are:

  • The keyboard key to switch between zoom 1:1 and zoom to fit is '*', which I have to access with 'shift' down since I'm on a laptop. This was less bad when I discovered I could right-click, but it's still annoying. 'z' would be a much better choice for right-handers, or '/' for left-handers. Or perhaps they could both be made to work. When working on an image I often want to switch between some particular area and the whole image when checking colour balance, sharpening, noise, etc, so this is one of the most used keyboard functions.
  • Using the mouse wheel to adjust sliders varies greatly in it's effect. A single detent for contrast or saturation often overshoots the useful range, so I have to drag the fiddly slider a fiddly pixel-and-a-half to go from a contrast of 1.00 to 1.03.
  • Not all modifications to an image show in the UI. When I crop or align an image RawStudio remembers the settings for these things (which is fantastic) but if I come back three months later I might not realise I'm looking at a cropped image. I can see all of the hue, saturation, sharpening and so forth, but there should be something in the UI to indicate that the crop and alignment have happened also.
  • It confuses me what settings get applied to a fresh image. I seem to get some kind of random selection of which DCP profile is being applied, and there's no way to set a default sharpening or noise reduction. Of course some of this is hard: noise reduction defaults really need to change depending on camera & ISO, and sharpening defaults probably should vary by lense and aperture too, to some extent.
  • The icon view runs across the top, taking up important screen real-estate. On my widescreen laptop I'd like the option to run it vertically where otherwise there's wasted space.

Things that I immediately love, over what UFraw gave me:

  • Sharpening.
  • Straightening images.
  • Cropping images (in some versions of UFraw this works, and in some it's broken, but the UI is useless in all of versions I've seen).
  • Colour profiles.
  • Lens corrections.

Things that I immediately miss from UFraw:

  • White balance presets.
  • Wavelet noise reduction.

There are a bunch of things that RawStudio also does that I haven't particularly found a use for yet, but which I suspect I will quite like when I do. The image classification and stuff seems likely to be useful, for sure.

In choosing to switch RawStudio I also looked at RawTherapee, which has recently relicensed under the GPL, but I chose RawStudio because it has vastly better performance on my laptop, and because I found the interface much more immediately accessible. RawTherapee also exceeds what UFraw can do in many ways, and looks like it might be useful for the really difficult cases, but learning to drive it with any facility could take some time. Especially if you only have an i7 740QM with 6G RAM, it would seem.

Last year I bought my first

Last year I bought my first DSLR (A Nikon D5000) and started tinkering with raw files - I've mostly been sticking with UFRaw because it integrates nicely with F-Spot, but I've been tracking the development of RawTherapee ever since it was relicenced under the GPL.

What I've found is that (especially with recent RawTherapee builds) it is a snap to make a photo that looks as good or better than the in-camera JPEGs, but cropping in RawTherapee is clunky and frustrating. UFRaw (0.16 and 0.17) has excellent cropping funcionality, but generally makes it difficult to achieve nice, vibrant colours. You're right that RawTherapee is much more complicated than UFRaw, but the workflow is largely the same - start with the left-most tab, get those settings correct, then go to the next tab and tweak those.

If you tried RawTherapee, messed with the Tone Curve control and watched your machine jump straight into swapping hell, that's a known problem that was fixed in revision 219, I believe. Unfortunately even Debian Experimental only has revision 193, so compiling it from source is still the best way to experiment with it.

I haven't tried RawStudio myself, although I have it installed.. I'll have to give it a go!

I might have to take another quick look at RawTherapee

If that performance issue is a resolved problem I might have to take another look at a recent build. I didn't notice swapping (mind you, with 6G of RAM... :-), but I did notice the fan on the laptop cranking up a lot, and some operations that were happening at essentially interactive speeds in RawStudio seemed to be taking multiple seconds in RawTherapee.

Darktable

Hmmmm... Stewart Smith suggested looking at Darktable also. So: download, install and load 4000 photos into it, and it looks like it has a very nice plugin architecture. Responsiveness is slower than RawStudio, though acceptable, I guess. The user interface feels like it's copying something I've never seen, and still has lots of annoyances to someone more used to contemporary Linux UI: no context menus. No menus of any sort, in fact. After two hours of fiddling I can adjust all sorts of things to do with an image, but have no idea how to create a jpeg from a nef. It seems to do lens profiles, but separates the vignetting adjustment from the rest of the lens where RawStudio (sensibly, to my mind) combines the two.

So for now, I think I'll stick with RawStudio for the bulk of my images, although maybe I could see a use for Darktable for effects processing. On the other hand I'm happy enough doing that in The Gimp, really, and it has a wider range of tricks. I like the RawStudio interface for straightening too - much easier to use than The Gimp's arbitrary rotation tool which the rotate for Darktable seems to follow. Something specific which is definitely missing from Darktable for the crop tool is a 16:9 ratio - no doubt just an oversight on the part of the developer.

And after another hour of mucking around I still haven't figured out how to save a nef in some format to put up on the intarwebs... I think I've tried right-clicking and left-clicking and middle-clicking just about every place I could find :-(

The two fixtures of

The two fixtures of traditional photography are the light-table (for examining, organising and grouping photos) and the dark-room (for developing and tweaking them); Adobe Lightroom does both, and grabbed elements of both words while Darktable (which I believe works much like Lightroom) grabbed the other half of each word.

The problem I have with Darktable is that although it lets you catalogue and organise photos, it keeps all your metadata in its own SQLite database instead of saving them to EXIF in each photo, or to an XMP sidecar file. That means if you ever decide to switch from Darktable to some other software, either that software needs to know how to import Darktable data, or you lose all that work.

I used to use Digikam; when I switched to F-Spot I just pointed it at my photo directory and imported everything - and there were my descriptions and tags all ready to go. I won't lightly give that up.

Darktable

I've been trying Darktable recently - http://darktable.sourceforge.net/ - it's got promise, still somewhat rough around the edges, but none of that nasty 8-bit downsampling.

8 bits per pixel

My how times have changed. When I started with computer-based imaging, if we had 8 bits per pixel we were lucky. And typically on those 8-bit machines, we had fewer than 8 bits per pixel in order to have any kind of resolution. All from a palette of a small number of colours. It's kind of amazing looking back at some of those images and realising just how primitive they look now, but also how effective some artists could be with those limitations.

Now we're complaining about only 8-bits per channel, per pixel (24 bits or 32-bits with an alpha channel). And we have the technology to make it obvious that it isn't actually enough for "perfect" replication. (Like sub-pixel rendering it appears to me the problem isn't so much in the final reproduction as in the accumulated losses in the intermediate steps.)

Thanks for the pointer to RawStudio. All my photos have been going through basically the same ImageMagick processing path that I came up with almost 10 years ago. And it might be time to think about something else. (I've avoided all the all-in-one photo tools, because of excessive levels of hand touching things. Oh, and the fact that F-Spot never seemed to do anything other than spin 100% CPU displaying nothing until I force quit it.)

Ewen

[D] [Digg] [FB] [R] [SU] [Tweet]