Switching to RAW Developer
Following earlier posts about this, today I managed to find time to evaluate Iridient RAW Developer 1.5.1 against CaptureOne Pro 3.7.4, for Olympus E-1 RAWs. The results are clear: RAW Developer is extracting more detail and more neutral colour than CaptureOne. As a long time CaptureOne user, I'm a bit shocked...
in Olympus E-System , Sunday, June 18, 2006
Following earlier posts about this, today I managed to find time to evaluate Iridient RAW Developer 1.5.1 against CaptureOne Pro 3.7.4, for Olympus E-1 RAWs. The results are clear: RAW Developer is extracting more detail and more neutral colour than CaptureOne. As a long time CaptureOne user, I'm a bit shocked...
There are plenty of RAW developers (lower case) out there, but a strong motive for my moving to Iridient RAW Developer (let's call it IRD from now on) is that it has no pretence to be a workflow tool. It doesn't even try to read images from newly inserted cards, thank heavens. Therefore I can use efficiently in tandem with iView MediaPro, which is exactly what I want. To be fair, Adobe Camera RAW could also be used in this way, as can Olympus Studio. CaptureOne cannot, easily, because of its sessions concept, and obviously do-everything solutions like Aperture and Lightroom cannot.
Concentrating on RAW development alone has allowed Iridient to focus effort on delivering what must be the most extensive range of adjustment tools in any program of this type. It is complex, and it does take a bit of getting used to moving from CaptureOne (for example there are 4 different sharpening methods, of which 3 are pretty esoteric). You can do an enormous amount of fiddling, but, fortunately, you don't have to - the default settings are pretty good.
Although the workflow issue is important, image quality is still a prime factor. From what I've seen so far it seems that IRD has little to fear here. I settled on a test image which has detail at various scales, and also has a sample of the dreaded, Tetris-inducing bright red in it.
Looking at these two crops, the first thing that has to be said is that the IRD version is basically "out of the box", although I did decide to use the R-L deconvolution at low settings, as this seems to to restore sharpness lost in the demosaicing processing / anti-aliasing filter. In C1Pro, finally I turned sharpening off, because even using the very low settings I had settled on as "capture sharpen" defaults, it seemed over-sharpened. I also turned "pattern suppression" on, but I was really surprised to see the infamous "tetris effect" in various places, and not just in red. It isn't clearly visible in the JPEG here, but one area is outlined in green. As for reds, well C1Pro for whatever reason did not tetrisise (new verb - you saw it here first!) them, but it certainly over-saturates at default settings. Here I am using -20 on the saturation scale, which is quite drastic - and it still looks wrong compared to IRD. To my eyes, IRD brings out more detail, including highlight detail, and delivers a more natural colour. The R-L deconvolution sharpening lends itself very well to different levels of output sharpening.
The IRD versions shows a little low level tetrisisation in the reds, but it doesn't show up in prints.
I've been considering switching to RAW Developer for some time. Now that I've finally found a few hours to evaluate it, I've decided to do so. It's a great piece of software at a very fair price. I'm not saying that CaptureOne is no good. I've been using it happily for 2 years. But I doubt that PhaseOne see much point in improving Olympus RAW performance for the tiny user base which all indications show they have. I think they are more likely to focus on the higher end DSLRs and their own medium format backs in future. CaptureOne can still sometimes be a very obscure program, and the session concept is too limited to provide a full image management solution, whilst getting in the way of programs like iView. It saved me from being stuck with Olympus Studio, but for now, it is probably going to be put out to pasture...
5 comments
Bernard Frangoulis June 19, 2006 - 4:37I have switched from Capture One to IRD as well, and agree about your points - including the workflow part. I'm still trying to devise a good workflow with IRD and iView. I have read "The DAM book", but find it difficult to apply fully here (except perhaps for the file organisation, which rather suits me). But that's another discussion...
One setting I have been playing with lately in IRD is the "Flare removal" control. This setting is not intended to be adjusted for every photograph, it is rather a "global" setting for each camera type.
Flare removal can be set either at "default", or adjusted manually. I find that if I manually adjust it to about 15-16, I get approximately the same flare removal as with the default option. If I increase flare removal to about 18 (or even 20, but this may be too much), the photograph often gains some "clarity", although it is a bit darker. I'm still experimenting, but I like this rendition best for the range of photographs I have tested, and may well set it as a new default for my Olympus E-1 pictures.
-- Bernard
5 comments
David Mantripp June 20, 2006 - 9:27As far as DAM is concerned, I also find the "DAM Book" of limited use. It isn't bad - in fact it is pretty good - but it is very specific to the writer's approach. I don't use Bridge much, hardly at all in fact (I haven't got the patience..) so at least 1/3rd of the book is irrelevant to me.
What I would like to see iView try to come up with is a way of implementing versions, as in Aperture. The problem is that would have to be cross catalog, which would mean that some kind of centralised referencing would have to exist. This might actually be the way forward - if they introduced an optional, master catalog (or index, say) through which you could cross-reference different variants and descendants of a base file 〈RAW or scan〉, then it would be possible for individual users to decide if they wanted this or not.
Actually, I bet it would not be impossible to do this with AppleScript and MySQL.... Maybe I'll try. One day.
5 comments
Bernard Frangoulis June 21, 2006 - 3:31iView implementing versions, with some kind of master catalog: *that* would be great, a complementary tool to the raw developer, not some all-encompassing photographic software.
Do this with AppleScript and MySQL... Yeah, me too. Maybe I'll try. One day. Let somebody else do it first though, days only have 24 hours 😉
5 comments
David Mantripp June 26, 2006 - 7:15A very useful fine tuning tool...
5 comments
Jill carter August 24, 2010 - 4:16