Comments on: RAW Heavyweights: Lightroom, DxO and Capture One

By: Ray

Ray — Sat, 13 Sep 2008 10:53:29 +0000

PT lens DOES work on Tiff files.

By: De Lira

De Lira — Tue, 19 Aug 2008 10:52:59 +0000

A few updates from a Mac user.
I’m using Capture One for about 2 years now. First 3.7 LE, now the version 4 (Windows and Mac)
I was always happy with the results of this software, plus it’s incomparable stability and speed.
I’ve decided to give a shot on DxO 5.2 demo on my MacBook Pro Core 2 2,5GHz 4GB RAM.
DxO is just slow… Very slow…
And on every 5 pics I work on, it will hang and I need to kill the process.
On the image quality produced, removing the extras from DxO (all geometry and lens conversion), there was nothing I could not reproduce with Capture One. But I will not give up and try some more, as well give a shot to Lightroom. But since LR does not include lens fix, why should I give up my Capture One I’m so happy about!
But a “tip”. For the entire lens correction missing on LR/CapOne. I’m using a very cheap tool, PTLens. Pity only works on JPEG, so you need to convert before, and use this tool after to do your horizon, cropping, perspective, cromatic aberration, vignetting etc.
I think it’s worth a try!

By: Roger W

Roger W — Sun, 17 Aug 2008 10:52:33 +0000

Hi, isn’t life strange? My RAW convertor of choice 2 years ago was Capture One but got sidetracked last year by the added functionality of Lightroom and as of today, I am being sidetracked again in experimenting with DxO. So it’s interesting to hear others views of these and, like Armand, think each has got strengths. Like others views I have read elsewhere I’m tempted to use DxO as part of my Lightroom workflow. So would be interested in others views.

Good review, thanks.

By: Priscilla Turner

Priscilla Turner — Fri, 08 Aug 2008 10:52:08 +0000

Yes, 5.2.0.7009 produces marvellous IQ.

By: donut

donut — Thu, 07 Aug 2008 10:51:38 +0000

I’ve had lots of crashing issues when trying 5 beta, but been fairly stable now that 5.2.1 is out. as for processing speed, it does a photo in something like 15 seconds on a Core2Quad Q9300 on Vista with 4GB of RAM, so I can’t complain.

I’m not a big fan of the workflow though… still think there’s a lot of room for improvement there.

By: Priscilla Turner

Priscilla Turner — Sun, 08 Jun 2008 10:51:06 +0000

DxO 5.1 just released is much better in most ways, and does recognise Pentax .dng files.

By: Blaise

Blaise — Sat, 08 Mar 2008 10:50:36 +0000

Excellent review! As a pro photographer I am always looking at ways to accelerate my workflow and produce the best looking pictures with low involvement.

I currently use DXO 4.51 and ACDSee (for photo management) and of course Photoshop.

I am consitently impressed by DXO – I now only use Photoshop for special filter effects.

I am very interested in Lightroom and you article was a real eye opener.

Thanks!

By: JChristian

JChristian — Mon, 03 Mar 2008 10:50:12 +0000

I’ve been using Capture One 4 for a little while and I’m really enjoying it.
I find it’s well-organized, easy to use, and gives a good result. I do like the
colors I get through my OEM processor (Pentax PhotoLab, which is SilkyPix)
better than C1, but now that I’m used to the basics of the program I’m going
to try and set a camera profile for my Pentax K100d into C1 and see if
that narrows any discrepancy. I’m glad I have C-One 4.

By: Priscilla Turner

Priscilla Turner — Mon, 03 Mar 2008 10:49:51 +0000

Yes, I agree with the last poster: even v. 5.04 is beta software, but without the usual interaction with the testers. Among other defects it is glacially slow.

I have the fastest quad-core CPU made plus 3GB RAM on a stable WinXPProSP2 OS.

By: Laszlo Kollar

Laszlo Kollar — Wed, 27 Feb 2008 10:49:19 +0000

I have used DXO 4 and DXO 5.0.1 on the strongest computer I have (a Dell Precision 670, 2 GB RAM) and I got dissappointed with DXO 5 regarding its performance. You need a dual/quad core CPU for this SW, a 3.6 GHz Xeon with 800 MHz FSB is not enough.

I also had stability problems with it: it crashed patching, then would not accept its own update, claiming that I should close DXO first… (and their support response was a link to the frequently asked questions, suggesting that I have a look there.)

In short, the DXO team should have spent more time on bugfixing a perf. tuning this thing.