Copy & Paste of Lens Correction values across different lenses produces wrong and unpredictable results

Nico Kaiser

• 28. Juni 2022 19:33

Has anyone else also experienced this issue?

When copy & pasting lens correction values (e.g. light falloff correction amount or distortion correction amount), results are different across different lenses.

Example: Car.ARW is taken with the Tamron A056 (70-180mm) lens
Ship.ARW is taken with the Tamron 28-75mm lens

• Import both files into a new Session
• Select Car.ARW
• Set Lens Correction: Light Falloff to 100%
• Copy the adjustment with the arrows symbol (select only Brightness)
• Select Ship.ARW
• Make a clone variant
• Apply the copied setting with the arrow symbol (Light Falloff correction is now 100%)
• Select the previously cloned variant of Ship.ARW
• Manually set Lens Correction: Light Falloff to 100%

• Compare the both variants of Ship.ARW
• Both have the same values for Lens Correction (both times 100% Brightness correction)
• The images are different, the one with the manually entered "100" is brighter on the edges

This makes copy & pasting lens correction values (e.g. "Apply distortion correction of 100 to all images regardless of their lens" or "Set all Light Falloff correction values to 50") completely unpredictable and produces wrong (way to bright / dark) results. There is currently no way to e.g. apply 100 Light Falloff correction to all images.

1

• 

  Permanently deleted user

  • 29. Juni 2022 01:39

  Yes, It's a known and documented issue by many users. It seems to unpredictably double up on correction values. To be polite, I've chalked this up to another one of C1's 'malfunctions' that tech support just can't seem to reproduce, so there's no solution or fix. Annoying as it may be, just hit reset on the lens tab and type in the values you'd like. Submit a ticket, your .log files and and screen recording of the issue if it really bothers you, but don't hold your breath. 

  0
• 

  Nico Kaiser

  • 29. Juni 2022 06:02

  I'm not sure if it's doubling up values or simply using wrong values (since copying correction values to a picture with the same lens/aperture works fine) / not re-calculating the right values. This is also not quick-fixable by fumbling around in the XML *.cos files, since these also store only the processed/calculated values.

  The current solution (click reset, type in the values) is a workaround, but doing this for hundereds/thousands of photos is really a pain – and a professional tool that claims to have good lens correction (which it does have) should not mess up these good corrections upon simple copy&paste operations.

  I already submitted a bug report along with sample files, so developers can easily reproduce this.

  1

Post ist für Kommentare geschlossen.