Skip to main content
Adobe Photoshop Family

31 Messages

 • 

396 Points

Thu, Jul 21, 2016 3:58 PM

Solved

Lightroom: Wrong Zeiss Batis 2/25 lens profile

The lens
profile for the Zeiss Batis 2/25 is obviously faulty. The vignette correction
goes either the wrong direction or is way too bright. It creates a sort of a
white vignette to the images. Who’s to address this issue – Adobe or Zeiss?

Responses

Official Solution

Adobe Administrator

 • 

14.6K Messages

 • 

283.3K Points

4 years ago

Sr. Product Manager, Adobe Digital Imaging

31 Messages

 • 

396 Points

Great! But with the new Update I now expierence a same issue with the Sony SEL70200G. Very odd. Might be a mix up with the SEL70200GM - a new, faster lens.

381 Messages

 • 

7.6K Points

Hi André,

I checked our test images for the 70-200G, 70-200GII, and the 70-200GM and did not notice a vignette over correction. Each profile was selected/applied as expected. If you have some sample images (including any XMP side cars with your settings) that I can review, please feel free to share a link to my email ccastleb@adobe.com.

Regards,

- Chris

31 Messages

 • 

396 Points

Sorry, I had a very terrible week. I'll e-mail you.

31 Messages

 • 

396 Points

4 years ago

The same image without the profile - noticeable dark vignetting.
s

381 Messages

 • 

7.6K Points

4 years ago

Hello André,

The vignette corrections for the Batis 25 are based on lens design data (i.e. optics model data). It's possible that it could be a bit aggressive, though our sample raw images from this lens do not demonstrate this behavior.

Would you be able to upload a few raw sample images to Dropbox (or similar) for me to use for investigation?

Thanks,

- Chris

31 Messages

 • 

396 Points

That sure is possible. Can you please contact me via mail, because I don't want to post the images to a public forum.

381 Messages

 • 

7.6K Points

Sure. Please send to ccastleb@adobe.com

- Chris

381 Messages

 • 

7.6K Points

4 years ago

Following up. Logged internally as bug #4176197. Fix submitted. Should be available in a future release.

- Chris

31 Messages

 • 

396 Points

Thanks! :)