using dxo lens correction with lightroom

If you would like to post, you'll need to register. Note that if you have a BCG store account, you'll need a new, separate account here (we keep the two sites separate for security purposes).

i just started using dxo pure raw. and like its lens correction feature .

i import into lightroom and see lightroom does lens correction on import too. do you bother to stop. lightroom from doing it too
 
My experience with PureRaw open in PS, the outputed DNG will have lens correction turned off.

Lens correction is non-destructive. When you open a RAW file from LR, I believe the correction isn’t baked in.
 
My experience with PureRaw open in PS, the outputed DNG will have lens correction turned off.

Lens correction is non-destructive. When you open a RAW file from LR, I believe the correction isn’t baked in.
if you open a raw file in lightroom and it’s a newer lens then if you use the option to use camera settings instead of adobe defaults where one size fits all,then the correction is automatically on unless turned off in camera to not allow the software to correct the lens.

since now the raw file goes to dxo first and then is imported into lightroom i have to double check and see if it still keeps lens correction on in lightroom .

iwill try it in a few and see if it is actually applying it 2x now
 
very interesting .

some z lenses like my 26mm. pancake show on import too into lightroom , lens profile built in to camera used. and the module for lens correction is grayed out .

other z lenses like the 50mm f1.4 and the 35mm f1.8 don’t grey out the module …the lens is picked up by lightroom and the profile is used and shows as corrected …

now it gets interesting .

processing a nef file first in dxo and then importing into lightroom had the module grayed out like when it uses the built in profile however now it doesn’t say lens profile built in the lens.

edit:

found a discussion on this .. it makes my hair hurt. ha ha .

i am still confused as to how this interfaces with the correction in pure raw

 
Last edited:
in this video he turns dxo lens correction off to avoid duplication by lightroom since you have no apparent way with some newer nikon lenses to disable the lightroom correction

 
To me the lens corrections are a main reason for using DXO, so I do the other way round, keep DXO and turn off in lightroom. I use Photolab but the denoise and lens correction is the same as pure raw.
 
Canon is the same, some lenses the software correction that you can't turn off is part of the lens design rather than having more elements to do it optically. I'm sure DXO accounts for it.
 
To me the lens corrections are a main reason for using DXO, so I do the other way round, keep DXO and turn off in lightroom. I use Photolab but the denoise and lens correction is the same as pure raw.
What makes you believe the DXO lens correction is superior to Adobe?
 
i have yet to see any review or test where lens correction was better in adobe than dxo .

there are so many comparisons on line .

general consensus is dxo does far more extensive testing
 
i have yet to see any review or test where lens correction was better in adobe than dxo .

there are so many comparisons on line .

general consensus is dxo does far more extensive testing
I tried very hard to find a difference, but I could not. Other than Reviews that say it is supposed to be better, can you spot a difference? To me, this is just fine marketing. Adobe isn't just guessing blindly about the lens correction; they must also do testing or get the info from Nikon.
 
I tried very hard to find a difference, but I could not. Other than Reviews that say it is supposed to be better, can you spot a difference? To me, this is just fine marketing. Adobe isn't just guessing blindly about the lens correction; they must also do testing or get the info from Nikon.
i only down loaded dxo yesterday but haven’t used it yet. just tested a few photos to see how to use it and that’s what made me question the double lens correction going on
 
i only down loaded dxo yesterday but haven’t used it yet. just tested a few photos to see how to use it and that’s what made me question the double lens correction going on
I bet you won’t find a difference…

And don’t try to use their lens sharpening more then soft or stranded. It looks digitally over sharpened.
 
it seems many non f2.8 lenses have lots of inherent distortion to keep weight and cost down … the lenses use a software scheme to work these inherent flaws out . the lenses correction feature cannot be turned off and comes right from manufacturer installed code according to what i was able to find



 
I’m trying to understand their marketing vs. reality.

PR offers 3 services.

Noise Reduction:
Is it in reality a better idea to cleanup noise in a raw vs a photoshop/Tiff?

Lens Softness:
DxO claims they know each lens the weaknesses and apply different sharpening across the frame Vs. ordinary unmasked sharpening. To me this is just fancy marketing. What’s your opinion on this?
It is also confusing their claims,
Soft, sharpening = 0
Standard = 1
= 2
= 3
Using soft, isn’t applying their magic lens soft treatment?!
Using anything more other then soft results in artificial overshapening results.
What’s the truth here?!

Lens profile correction:
So, Only DxO measures the amount to correct, while Adobe uses gauss work?! Give me a break…

Other then the “Speed” of their newest deep prime xd2, I couldn’t find any difference between DxO and the latest ACR Denoise AI.
I tried pixel peeping in LRC on a number of different pictures, under different conditions, different subjects. From portraiture to wildlife.
I couldn’t detect any differences.

The only real difference I can see, and I like it, is NX Studio… I love the randor of the colors. I could never get Adobe to really match it.
And the free Noise Reduction in NX, is VERY effective and the most natural of them all. Although NX will not provide a buttery smooth and clean noise free background. It still looks good and pleasing to eye. If Nikon would go the route DxO took, I would love to use NX for basic correction, sharpening, NR, and most of all, “Picture Profiling”.
Nikon’s D-light is a lovely toolbox that works wonderfully for most situations.
Sadly NX is behaving like an outdated software on an outdated computer….
 
Hi Joel
Where does Adobe get the values for the lens corrections? Does Adobe test itself or does it get the values from the individual manufacturers? DXO tests itself.
Everyone has to decide for themselves which tool they use for corrections.
 
I’m trying to understand their marketing vs. reality.

PR offers 3 services.

Noise Reduction:
Is it in reality a better idea to cleanup noise in a raw vs a photoshop/Tiff?

Lens Softness:
DxO claims they know each lens the weaknesses and apply different sharpening across the frame Vs. ordinary unmasked sharpening. To me this is just fancy marketing. What’s your opinion on this?
It is also confusing their claims,
Soft, sharpening = 0
Standard = 1
= 2
= 3
Using soft, isn’t applying their magic lens soft treatment?!
Using anything more other then soft results in artificial overshapening results.
What’s the truth here?!

Lens profile correction:
So, Only DxO measures the amount to correct, while Adobe uses gauss work?! Give me a break…

Other then the “Speed” of their newest deep prime xd2, I couldn’t find any difference between DxO and the latest ACR Denoise AI.
I tried pixel peeping in LRC on a number of different pictures, under different conditions, different subjects. From portraiture to wildlife.
I couldn’t detect any differences.

The only real difference I can see, and I like it, is NX Studio… I love the randor of the colors. I could never get Adobe to really match it.
And the free Noise Reduction in NX, is VERY effective and the most natural of them all. Although NX will not provide a buttery smooth and clean noise free background. It still looks good and pleasing to eye. If Nikon would go the route DxO took, I would love to use NX for basic correction, sharpening, NR, and most of all, “Picture Profiling”.
Nikon’s D-light is a lovely toolbox that works wonderfully for most situations.
Sadly NX is behaving like an outdated software on an outdated computer….
i have to see if anyone did a comparison on lens correction
 
if i remember correctly, the difference was in noise reduction and sharpening , not lens correction now that i think about it. when steve perry. tested the differences

on a side note i just wrote dxo to see how they handle the fact that lens correction code is written into the software for many z lenses and will be rendered by lightroom regardless

my guess is that since dxo disregards all the edits lightroom applies it may disregard the instruction set that applies automatically the built in corrections and then does its own based on dxo testing
 
Last edited:
I asked Thom Hogan on this.
His response:

Answers below



--

Thom Hogan, writer/photographer

bythom.com, dslrbodies.com, sansmirror.com, zsystemuser.com





  • Is it in reality a better idea to cleanup noise in a raw vs a photoshop/Tiff?

Yes, if the algorithm is good. The problem is that when you demosaic an image, you use near-neighbor values to create a specific RGB pixel. That means that noise is encoded from the neighbors as well as the original pixel. This can be subtle, but it’s a real issue.

> DxO claims they know each lens the weaknesses and apply different sharpening across the frame Vs. ordinary unmasked sharpening. To me this is just fancy marketing. What’s your opinion on this?

No, it’s not fancy marketing. The whole thing about DxO from the beginning has been that they actually take product and measure it. Again, it’s subtle, and your sample of a lens may vary some from theirs, but lenses (and thus images) are not invariable in blur circle from edge to edge.

> It is also confusing their claims, Soft, sharpening = 0 Standard = 1 = 2 = 3 Using soft, isn’t applying their magic lens soft treatment?!

That you’d have to ask them for details about. This is the usual “the engineers now what they did, but the marketing team either is trying to simplify that to absurdity or didn’t understand it themselves.

> So, Only DxO measures the amount to correct, while Adobe uses gauss work?! Give me a break…

No, DxO actually does their own measurements. Adobe uses (for the most part) the camera companies “profiles.” It’s those profiles that are problematic. For some lenses they’re overly simplistic, which is one reason why you sometimes see residual linearity issues even after Adobe (or the camera maker) applies a profile. This specifically shows up with lenses with mustache distortion, because the profiles only define simple barrel or pincushion adjustments and where to make those.

> Other then the “Speed” of their newest deep prime xd2, I couldn’t find any difference between DxO and the latest ACR Denoise AI.

Yeah, well I don’t know what you can and can’t see. I don’t know if you’re trained to see what you’d need to be trained to see. I discount pretty much all claims of “I don’t see a difference.” Some of us measure, some of us have been trained (heck some of us are trainers). No doubt that we’re up to the point where we’re chasing small differences, and most people can’t see small differences, and most uses of an image wouldn’t come close to reveal those small differences.

> I tried pixel peeping in LRC on a number of different pictures, under different conditions, different subjects. From portraiture to wildlife. I couldn’t detect any differences.

Note what I just said, but also know this: LRC (and most products) don’t ever really show you actual pixels. They scale to the display, and many, including Adobe’s use math I’d call “challenged.” That’s because they want to do what they do fast, not accurately (which takes time).

> The only real difference I can see, and I like it, is NX Studio… I love the randor of the colors. I could never get Adobe to really match it.

Note what I said about trained versus trainers. I can match Adobe to NX Studio. It’s not simple and it’s not something that can be applied across all images (e.g. a preset), but it can be done. But also, we’re back to that math thing and the display. If you take shortcuts with the math, which Adobe does, you get different results than if you use floating point correctly.

> And the free Noise Reduction in NX, is VERY effective and the most natural of them all.

Not in my judgement. It’s okay, but it really has an interaction with sharpening that can make it stand out.

> It still looks good and pleasing to eye.

Pleasing to YOUR eye. That’s actually one of the issues facing everyone. We have varying degrees of what we can see and what we like. By all means, choose what you like, but don’t for a second believe that’s a “standard” and that everyone will like it.

> Sadly NX is behaving like an outdated software on an outdated computer….
Well, it is. NX Studio is actually Silkypix—and I believe an older version—on which Nikon has mounted their JPEG rendering engine.
 
I asked Thom Hogan on this.
His response:

Answers below



--

Thom Hogan, writer/photographer

bythom.com, dslrbodies.com, sansmirror.com, zsystemuser.com





  • Is it in reality a better idea to cleanup noise in a raw vs a photoshop/Tiff?

Yes, if the algorithm is good. The problem is that when you demosaic an image, you use near-neighbor values to create a specific RGB pixel. That means that noise is encoded from the neighbors as well as the original pixel. This can be subtle, but it’s a real issue.

> DxO claims they know each lens the weaknesses and apply different sharpening across the frame Vs. ordinary unmasked sharpening. To me this is just fancy marketing. What’s your opinion on this?

No, it’s not fancy marketing. The whole thing about DxO from the beginning has been that they actually take product and measure it. Again, it’s subtle, and your sample of a lens may vary some from theirs, but lenses (and thus images) are not invariable in blur circle from edge to edge.

> It is also confusing their claims, Soft, sharpening = 0 Standard = 1 = 2 = 3 Using soft, isn’t applying their magic lens soft treatment?!

That you’d have to ask them for details about. This is the usual “the engineers now what they did, but the marketing team either is trying to simplify that to absurdity or didn’t understand it themselves.

> So, Only DxO measures the amount to correct, while Adobe uses gauss work?! Give me a break…

No, DxO actually does their own measurements. Adobe uses (for the most part) the camera companies “profiles.” It’s those profiles that are problematic. For some lenses they’re overly simplistic, which is one reason why you sometimes see residual linearity issues even after Adobe (or the camera maker) applies a profile. This specifically shows up with lenses with mustache distortion, because the profiles only define simple barrel or pincushion adjustments and where to make those.

> Other then the “Speed” of their newest deep prime xd2, I couldn’t find any difference between DxO and the latest ACR Denoise AI.

Yeah, well I don’t know what you can and can’t see. I don’t know if you’re trained to see what you’d need to be trained to see. I discount pretty much all claims of “I don’t see a difference.” Some of us measure, some of us have been trained (heck some of us are trainers). No doubt that we’re up to the point where we’re chasing small differences, and most people can’t see small differences, and most uses of an image wouldn’t come close to reveal those small differences.

> I tried pixel peeping in LRC on a number of different pictures, under different conditions, different subjects. From portraiture to wildlife. I couldn’t detect any differences.

Note what I just said, but also know this: LRC (and most products) don’t ever really show you actual pixels. They scale to the display, and many, including Adobe’s use math I’d call “challenged.” That’s because they want to do what they do fast, not accurately (which takes time).

> The only real difference I can see, and I like it, is NX Studio… I love the randor of the colors. I could never get Adobe to really match it.

Note what I said about trained versus trainers. I can match Adobe to NX Studio. It’s not simple and it’s not something that can be applied across all images (e.g. a preset), but it can be done. But also, we’re back to that math thing and the display. If you take shortcuts with the math, which Adobe does, you get different results than if you use floating point correctly.

> And the free Noise Reduction in NX, is VERY effective and the most natural of them all.

Not in my judgement. It’s okay, but it really has an interaction with sharpening that can make it stand out.

> It still looks good and pleasing to eye.

Pleasing to YOUR eye. That’s actually one of the issues facing everyone. We have varying degrees of what we can see and what we like. By all means, choose what you like, but don’t for a second believe that’s a “standard” and that everyone will like it.

> Sadly NX is behaving like an outdated software on an outdated computer….
Well, it is. NX Studio is actually Silkypix—and I believe an older version—on which Nikon has mounted their JPEG rendering engine.
excellent post
 
I asked Thom Hogan on this.
His response:

Answers below



--

Thom Hogan, writer/photographer

bythom.com, dslrbodies.com, sansmirror.com, zsystemuser.com





  • Is it in reality a better idea to cleanup noise in a raw vs a photoshop/Tiff?

Yes, if the algorithm is good. The problem is that when you demosaic an image, you use near-neighbor values to create a specific RGB pixel. That means that noise is encoded from the neighbors as well as the original pixel. This can be subtle, but it’s a real issue.

> DxO claims they know each lens the weaknesses and apply different sharpening across the frame Vs. ordinary unmasked sharpening. To me this is just fancy marketing. What’s your opinion on this?

No, it’s not fancy marketing. The whole thing about DxO from the beginning has been that they actually take product and measure it. Again, it’s subtle, and your sample of a lens may vary some from theirs, but lenses (and thus images) are not invariable in blur circle from edge to edge.

> It is also confusing their claims, Soft, sharpening = 0 Standard = 1 = 2 = 3 Using soft, isn’t applying their magic lens soft treatment?!

That you’d have to ask them for details about. This is the usual “the engineers now what they did, but the marketing team either is trying to simplify that to absurdity or didn’t understand it themselves.

> So, Only DxO measures the amount to correct, while Adobe uses gauss work?! Give me a break…

No, DxO actually does their own measurements. Adobe uses (for the most part) the camera companies “profiles.” It’s those profiles that are problematic. For some lenses they’re overly simplistic, which is one reason why you sometimes see residual linearity issues even after Adobe (or the camera maker) applies a profile. This specifically shows up with lenses with mustache distortion, because the profiles only define simple barrel or pincushion adjustments and where to make those.

> Other then the “Speed” of their newest deep prime xd2, I couldn’t find any difference between DxO and the latest ACR Denoise AI.

Yeah, well I don’t know what you can and can’t see. I don’t know if you’re trained to see what you’d need to be trained to see. I discount pretty much all claims of “I don’t see a difference.” Some of us measure, some of us have been trained (heck some of us are trainers). No doubt that we’re up to the point where we’re chasing small differences, and most people can’t see small differences, and most uses of an image wouldn’t come close to reveal those small differences.

> I tried pixel peeping in LRC on a number of different pictures, under different conditions, different subjects. From portraiture to wildlife. I couldn’t detect any differences.

Note what I just said, but also know this: LRC (and most products) don’t ever really show you actual pixels. They scale to the display, and many, including Adobe’s use math I’d call “challenged.” That’s because they want to do what they do fast, not accurately (which takes time).

> The only real difference I can see, and I like it, is NX Studio… I love the randor of the colors. I could never get Adobe to really match it.

Note what I said about trained versus trainers. I can match Adobe to NX Studio. It’s not simple and it’s not something that can be applied across all images (e.g. a preset), but it can be done. But also, we’re back to that math thing and the display. If you take shortcuts with the math, which Adobe does, you get different results than if you use floating point correctly.

> And the free Noise Reduction in NX, is VERY effective and the most natural of them all.

Not in my judgement. It’s okay, but it really has an interaction with sharpening that can make it stand out.

> It still looks good and pleasing to eye.

Pleasing to YOUR eye. That’s actually one of the issues facing everyone. We have varying degrees of what we can see and what we like. By all means, choose what you like, but don’t for a second believe that’s a “standard” and that everyone will like it.

> Sadly NX is behaving like an outdated software on an outdated computer….
Well, it is. NX Studio is actually Silkypix—and I believe an older version—on which Nikon has mounted their JPEG rendering engine.
Very good answers IMHO
 
Back
Top