Jump to content

Recommended Posts

Advertisement (gone after registration)

The lack of lens distortion corrections is increasingly annoying: it should have been fixed in the most recent round of Creative Cloud updates but the distortion corrections are still not working. On some lenses this is a real issue and on others it’s less important. Subject matter also makes a difference. But for my sort of use, some lenses are almost unusable at the moment… see the shot from the Trip-Elmar today at, I think, 18mm. More mustache than a mariachi…

Leica says of this lens: “Due to the minimal distortion and barely perceptible field curvature, it can be recommended for highly demanding architecture photography even at the 16mm setting”

I don’t think so. We need these lens corrections and we need them now! Who should we be talking to about this? 

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

  • Like 1
  • Thanks 2
  • Haha 2
Link to post
Share on other sites

Does anyone know if C1 has this issue too?

Do the jpegs have this distortion too?

adobe don’t make a lens profile for each camera, just a profile for each lens (ie adobe have a profile for x M mount lens and it should work whether it’s an M9/240/10/10R/11) and this clearly isn’t working…

  • Like 1
Link to post
Share on other sites

51 minutes ago, hdmesa said:

You may want to download the C1 demo.

I have the full latest version of C1 (and the latest LR CC) - I just don't have an M11!

My point is this. To identify a problem first note where you can observe the problem. So is this a problem with the M11 and every single RAW app out there (including the in camera JPEG engine) or is it just in LR/ACR?

So.. does this happen in C1? (I assume yes!)

My hunch is that this is adobe's job to fix... if for no other reason than ideally it's their job to support cameras not camera companies job to support them

 

  • Thanks 1
Link to post
Share on other sites

Advertisement (gone after registration)

1 minute ago, Adam Bonn said:

I have the full latest version of C1 (and the latest LR CC) - I just don't have an M11!

My point is this. To identify a problem first note where you can observe the problem. So is this a problem with the M11 and every single RAW app out there (including the in camera JPEG engine) or is it just in LR/ACR?

So.. does this happen in C1? (I assume yes!)

My hunch is that this is adobe's job to fix... if for no other reason than ideally it's their job to support cameras not camera companies job to support them

 

I just checked an M11 shot I had with the 28 Lux. If I select the 28 Lux profile in C1 (C1 creates these themselves) and adjust the distortion correction slider, it appears to correct the distortion. There is no option to choose "Manufacturer Profile", but I think that's because I may have had lens detection turned off. My replacement M11 arrives tomorrow, so I'll try it again with lens detection on.

  • Thanks 1
Link to post
Share on other sites

Note that lens corrections with Tri-Elmar work if I change the model name from "LEICA M11" to "LEICA M10-R" (I used DNG Cleaner to change the name).

Seems clearly an Adobe bug.

  • Like 2
  • Thanks 3
Link to post
Share on other sites

4 hours ago, hdmesa said:

I just checked an M11 shot I had with the 28 Lux. If I select the 28 Lux profile in C1 (C1 creates these themselves) and adjust the distortion correction slider, it appears to correct the distortion. There is no option to choose "Manufacturer Profile", but I think that's because I may have had lens detection turned off. My replacement M11 arrives tomorrow, so I'll try it again with lens detection on.

Please let us know how you get on….

  • Like 1
Link to post
Share on other sites

6 hours ago, SrMi said:

Note that lens corrections with Tri-Elmar work if I change the model name from "LEICA M11" to "LEICA M10-R" (I used DNG Cleaner to change the name).

Seems clearly an Adobe bug.

IMHO that’s 100% the answer

slightly OT but years ago C1 had a similar thing where lens profiles for the Fuji X-T2 worked but the same lens profiles for the X-Pro2 didn’t.

Link to post
Share on other sites

9 hours ago, hdmesa said:

I just checked an M11 shot I had with the 28 Lux. If I select the 28 Lux profile in C1 (C1 creates these themselves) and adjust the distortion correction slider, it appears to correct the distortion

IMO if an app offers a lens profile, then the user shouldn’t have to correct for distortion themselves. To my eye….. the C1 lens profiles for the 35 rit, 90 rit and 50 lux do absolutely nothing at all. Despite C1’s claims of testing their lens profiles extensively.

 

Link to post
Share on other sites

7 hours ago, SrMi said:

Note that lens corrections with Tri-Elmar work if I change the model name from "LEICA M11" to "LEICA M10-R" (I used DNG Cleaner to change the name).

Seems clearly an Adobe bug.

I forgot to add.. Great work Srdjan.

You’ve proved that Leica’s DNG content (this is separate from the dcp file folks) is correct and implemented as per their previous cameras. Adobe appears to be incorrectly rendering the file against the parameters contained within its own lens profile files and has work to do (and no folks, this doesn’t mean making a new dcp profile file)

Now that adobe officially lists the M11 as ‘supported’ FWIW I think that M11 owners start logging this bug.

https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-bugs/how-do-i-write-a-bug-report/idi-p/12386393

https://www.adobe.com/products/wishform.html
 

Edited by Adam Bonn
  • Thanks 1
Link to post
Share on other sites

3 hours ago, Adam Bonn said:

IMO if an app offers a lens profile, then the user shouldn’t have to correct for distortion themselves. To my eye….. the C1 lens profiles for the 35 rit, 90 rit and 50 lux do absolutely nothing at all. Despite C1’s claims of testing their lens profiles extensively.

 

Yes, something is wrong with many C1 M lens profiles with regard to distortion correction. But unlike LR, I don’t think it’s tied to using the M11 profile, since I noticed the issue with the SL2-S as well. 

  • Like 1
Link to post
Share on other sites

45 minutes ago, hdmesa said:

Yes, something is wrong with many C1 M lens profiles with regard to distortion correction. But unlike LR, I don’t think it’s tied to using the M11 profile, since I noticed the issue with the SL2-S as well. 

Yup, it’ll be because c1 didn’t encode distortion corrections into their profiles.

Link to post
Share on other sites

We need a Lens Distortion Alliance 😂

In C1 I gave up on having a profile for all my lenses a long time ago. C1 is years behind delivering profiles for new lenses from major manufacturers. C1 has fewer profiles in general than LR because they create their own, whereas Adobe will use manufacturer-provided profile data for theirs, which speeds up the process. The benefit to the C1 profiles is they are often more accurate than what the manufacturer delivers. Of course in C1 if there is an embedded profile from the manufacturer, I can select that instead of manually choosing the lens, but when I do that, I can't change how much distortion or vignetting correction is applied – it's all or nothing.

Link to post
Share on other sites

32 minutes ago, hdmesa said:

They did for the 28 Lux, so it must be a problem specific to certain lenses.

The cynic in me thinks it's a value proposition.... if (say) Fuji or Sony make a new lens tomorrow then C1 knows they'll have lots of customers complaining if there's no profile for it.

With the M lenses I think the user base is smaller so they put less effort erm resource into coding for it 

28 minutes ago, hdmesa said:

We need a Lens Distortion Alliance 😂

I'm up for that, beats me buying more expensive better corrected lenses anyway  😅

29 minutes ago, hdmesa said:

In C1 I gave up on having a profile for all my lenses a long time ago. C1 is years behind delivering profiles for new lenses from major manufacturers. C1 has fewer profiles in general than LR because they create their own, whereas Adobe will use manufacturer-provided profile data for theirs, which speeds up the process. The benefit to the C1 profiles is they are often more accurate than what the manufacturer delivers. Of course in C1 if there is an embedded profile from the manufacturer, I can select that instead of manually choosing the lens, but when I do that, I can't change how much distortion or vignetting correction is applied – it's all or nothing.

I think sometimes LR a little 'over corrects' (sic) for things like vignetting and I end up dialling that back a bit.

I really love how LR supports lens from Zeiss and CV etc in M mount versions that C1 doesn't seem to acknowledge as in existence..

I was a massive C1 fan back in my Fuji days (until I got an X-Pro2 and C1 took ages to support it, ironically with lens profiles) but since going all in with Leica I've really cooled to it. I've tried to go back a few times.. but I just somehow don't like it as much.. it's not the GUI (I prefer some things about the C1 interface and some about LR) but just somehow I prefer the output from LR, in back to back testing I see that C1 has tangibly better highlight recovery, and far more user control over sharpening etc but somehow the LR output just carries a more pleasing look to my eye (other eyes will vary)

Perhaps when I eventually end up with a high res M (I have an M9 and M10) C1 will be the way to go, but for me, for now I prefer how the files look coming out of LR

 

  • Like 1
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...