... that is, when applied at the level of "raw" image-data prior to de-mosaicing and prior to NR (which helps to attenuate some of the DD artifacts that inevitably result). DxO Optics Pro 6.x "Lens Softness" corrections can be impressive, indeed. Note that DD is not the only component of the DxO "Lens Softness" corrections:
http://www.dxo.com/us/photo/dxo_optics_pro/optics_geometry_corrections/lens_softnessI have created some comparison examples for viewing. Best to download them and line them up to compare them in an image-viewer (as the DPR display-system downwardly re-samples these images, thus distorting the results).
.
A comparison between two approaches to the business of "sharpening" in order to enhance "image acuity": DxO Lens Softness corrections followed by mild Unsharp Masking; OR Lightroom 3.4 Sharpening (which uses USM and Deconvolution Deblurring):
(1) DxO 6.6 (without Lens Softness corrections) > LR 3.5 Sharpening (Equal Parts USM + Deconvolution Deblurring: Radius=0.5; Strength=100%; Detail=50; Masking=3) > XnView 1.982 (Loss-less JPEG); or
(2) DxO 6.6 (with Lens Softness corrections) > Sagelight 3.1 Sharpening [16-bit USM: Radius=0.5; Strength=100%, (non-linear) Threshold=10] > XnView 1.982 (Loss-less JPEG).
Notes:
In the process of sharpening the 16-bit TIF output image-file resulting from DxO RW2 processing, Lightroom 3.5 was used only as a (USM + DD) sharpening tool. The LR 3.5 "Masking" (linear threshold control) was set to 3/100 (around 5 EV, or "stops", below maximum level). All other LR 3.5 functions were either set to Zero (0), or disabled completely.
In the process of sharpening the 16-bit TIF output image-file resulting from DxO RW2 processing, Sagelight 3.1 was used only as a (16-bit USM) sharpening tool. The SL 3.1 "Threshold" (an exponentially scaled threshold control) was set to 10/100 (estimated to be around 5 EV, or "stops", below maximum level). No other SL 3.1 functions were used.
XnView 1.982 was used in both case to convert the 16-bit TIF results to an 8-bit loss-less JPG (using no Chroma Sub-sampling, and with Quality Factor = 100%).
Below are working links to example images that show the result of applying those two approaches (at 3272x2454 original crop size):
DxO (without Lens Softness corrections) > Lightroom (USM+DD Sharpening):
http://www.dpreview.com/galleries/4464732135/download/1476868DxO (with Lens Softness corrections) > Sagelight (USM Sharpening):
http://www.dpreview.com/galleries/4464732135/download/1476869.
So, do things get any better at a reduced (1600x1200) pixel-size? ...
A comparison between two approaches to the business of "sharpening" in order to enhance "image acuity": DxO Lens Softness corrections followed by mild Unsharp Masking; OR Lightroom 3.4 Sharpening (which uses USM and Deconvolution Deblurring):
(1) DxO 6.6 (without Lens Softness corrections) > Artizen 2.86 (16-bit Lanczos-3 re-sampling to a 1600x1200 pixel-size) > LR 3.5 Sharpening (Equal Parts USM + Deconvolution Deblurring: Radius=0.5; Strength=100%; Detail=50; Masking=3) > XnView 1.982 (Loss-less JPEG); or
(2) DxO 6.6 (with Lens Softness corrections) > Artizen 2.86 (16-bit Lanczos-3 re-sampling to a 1600x1200 pixel-size) > Sagelight 3.1 Sharpening [16-bit USM: Radius=0.5; Strength=100%, (non-linear) Threshold=10] > XnView 1.982 (Loss-less JPEG).
Notes:
In the process of sharpening the 16-bit TIF output image-file resulting from DxO RW2 processing, Lightroom 3.5 was used only as a (USM + DD) sharpening tool. The LR 3.5 "Masking" (linear threshold control) was set to 3/100 (around 5 EV, or "stops", below maximum level). All other LR 3.5 functions were either set to Zero (0), or disabled completely.
In the process of sharpening the 16-bit TIF output image-file resulting from DxO RW2 processing, Sagelight 3.1 was used only as a (16-bit USM) sharpening tool. The SL 3.1 "Threshold" (an exponentially scaled threshold control) was set to 10/100 (estimated to be around 5 EV, or "stops", below maximum level). No other SL 3.1 functions were used.
XnView 1.982 was used in both case to convert the 16-bit TIF results to an 8-bit loss-less JPG (using no Chroma Sub-sampling, and with Quality Factor = 100%).
Below is the result of applying those two approaches (at a 1600x1200 pixel size):
DxO (without Lens Softness corrections) > Lightroom (USM+DD Sharpening):
http://www.dpreview.com/galleries/4464732135/download/1476933DxO (with Lens Softness corrections) > Sagelight (USM Sharpening):
http://www.dpreview.com/galleries/4464732135/download/1476934.
(All methods of applying) DD to images suffer from the possibility of significant artifacts (if/when the number of re-circulations in the Deconvolution-processes is increased). (I think) that the idea of being able to apply DD processes after the fact, and "willy nilly" on random images is a dubious pipe-dream at best [whether or not some algorithm has attempted to "guess" the total system Point Spread Function (PSF)]. See:
In practice, finding the true PSF is impossible, and usually an approximation of it is used, theoretically calculated or based on some experimental estimation by using known probes. Real optics may also have different PSFs at different focal and spatial locations, and the PSF may be non-linear.http://en.wikipedia.org/wiki/Deconvolution#Optics_and_other_imagingVarious people appear to be reading
all kinds of fantasy-applications in to this Adobe "toy" still being tinkered-upon by "Santa's Elves". Such thoughts say more about their naivete (probably a big plus for Adobe's marketing department?) than it does about what is really going on, and what is possible. Adobe has proven that all that a marketeer has to accomplish is to "fool some of the people all of the time", and (in the situation of a high enough volume of sales), "Fat City" is not that hard to (for a time, anyway) find.
BTW - Jue Wang is clearly a highly technically competent individual. Please understand that I harbor no ill-will towards Mr. Wang himself. (However), the way that Adobe Inc. has handled this public relations "FUBAR" is unfortunate, indeed. Those who have actually worked within a design/development engineering environment (as have I) will likely understand
exactly what I am talking about ...

.
Some Deconvolution Deblurring links for the genuinely curious to follow:
Here is the Richardson-Lucy deconvolution approach arising out of the Hubble Space Telescope:
http://adsabs.harvard.edu/full/1994ASPC...61..296.
Some (freeware) command-line executable files (the example-images for which look pretty slick):
http://www.cse.cuhk.edu.hk/~leojia/projects/motion_deblurring/index.html Here's a paper that is co-authored by Jue Wang of Adobe Systems you might like:
http://cg.postech.ac.kr/research/deconv_outliers/There are a number of things already in existence as (GUI) plug-ins and stand-alone applications that you might dig:
The
Refocus (freeware) plug-in for GIMP (Wiener Filtering deconvolution; a real POS).
FocusMagic (not sure if it's Wiener Filtering or Richardson-Lucy; a few people still like using it).
InFocus (looks slicker than FocusMagic; more current from the standpoint of development).
RAW Therapee (freeware) Richardson-Lucy Deconvolution Deblurring (4 controllable parameters). The 4.x releases are much improved from the (still buggy with Windows OSs) Versions 3.x. RT 4.x has what is (in my viewpoint) a better user-interface than DxO, LR3.x /CR 6.x, or Silkypix (SE or Pro 4.x versions).
(And my personal favorite),
DxO Optics Pro 6.x "Lens Softness" corrections which incorporates Deconvolution Deblurring along with other elements (for RAW/JPG processing of supported camera/lens combinations). The DxO (RAW-mode) Optical Corrections Modules work the best. The DxO (JPG-mode) Optical Corrections Modules are impressive (but do not benefit from the originally mentioned ability to perform the DD processes at the "raw" image-data level, prior to de-mosaicing, and prior to any NR applied in processing).