Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Mac - Light Falloff is not applied correctly.

Implemented

Comments

72 comments

  • Jarjan Fisher

    I'm experienceing the same issue (PC/Win) and was promised this would be fixed in the latest release, but alas, after updating I'm still having the exact same issue. It's been over 6 months now since I've reported the problem. I'm seriously disappointed by Capture One. This bug makes the use of custom styles impossible for me, and that's a big issue!

    1
  • Nico Kaiser

    Jarjan Fisher Does this also still happen if you completely reset the Lens Correction tool using the reset arrow in the tool's title bar?

    0
  • Jarjan Fisher

    I'm not entirely sure what you mean by that?

    But I tried:

    - reset the Lens Correction tool as you say

    - un-apply and the re-apply the custom style with vignette correction

    * The image now looks evenly exposed

    - Re-start capture one

    - Corners are over-exposed/washed out

    If that's what you meant then yes, it still happens.

     

    1
  • Nico Kaiser

    Yes, you are right! Applying Lens Corrections via style or preset is still broken. I'll re-open the ticket. I honestly do not know what they are doing at Capture One, and how hard it can be to interpret "100% correction", but the internals of the tool must be a real mess...

    4
  • Jarjan Fisher

    I'm happy you confirm the same issue, though very unhappy that it's indeed still not fixed! :-D (And even more unhappy the Support actually promised me it had been fixed... I'm quickly losing the last bit of trust I still had in Capture One...)

    0
  • Sebastian Reiprich

    This cannot be true… If you re-open the ticket anyway, please also mention distortion and CA correction, because I simply assume that those are still broken as well…
    This is such a basic functionality and still they don’t seem to understand what a 100% correction means… And even if they finally fix it in the next update I am pretty sure that it is going to be a paid update…

    1
  • Jarjan Fisher

    Ps, I've also replied to customer support via email, so I assume my ticket on this is re-opened too.

    0
  • Nico Kaiser

    Same here. This is such a basic feature ("apply 100% lens correction"), and there was _no_ way to achieve this reliably for years.

    One can argue over the (very doubtful) decision of only applying Distortion correction "sometimes" (support told me it is only applied automatically when distortion is over a certain threshold), but until recently there was no way to apply 100% distortion correction to thousands of photos, but doing it manually for every single photo. This is embarassing.

    Quality control at Capture One seems to be in a very very concerning shape.

    0
  • Michael Lake

    I can confirm that I'm seeing the same behavior as others here. If I set Light Falloff to 100 on a new, unedited image, it seems to work fine (and stays consistent between app launches). But if I apply a preset that has any Lens Correction (even if it's just the Distortion setting), setting Light Falloff to 100 causes the double-exposure problem.

    1
  • Sebastian Reiprich

    I just assume that it applies for the sharpnees correction as well, but this is very hard see with your bare eye…
    I tend to say that the „Pro“ stands for problem…

    0
  • Jarjan Fisher

    Interesting... With me it also happens at different levels (I usually have the light fall-off set at around 85%), but applied via a custom style. This brings out the issue for me.

    As I like to use a custom style for my default/starter settings based on the lens used, that's quite a big problem...

    0
  • Sebastian Reiprich

    If you analyze an image for CAs and copy and apply the lens correction settings or all settings of an image to another one the CA corrections of image A are also applied to image B, C and D by default which can cause very bad fringing.

    0
  • David Kosmin

    This is really troubling. I’m glad I didn’t install the update yet. Has there been a response from C1?

    0
  • pixmania

    Interesting conversation, madding problem to be sure!

    Can we all agree that it's the "lens style" or a pre-applied correction that begins the issue?

    I belive that Nico nailed it here; https://support.captureone.com/hc/en-us/community/posts/10984244456349/comments/11974176146333

    Kevin

    0
  • Nico Kaiser

    Helen This is not fixed completely, again. Customers are slowly getting angry and are losing faith in Capture One software quality, which once was a reliable, stable, professional tool. Please make this a high priority issue and have staff work on it, it is ridiculous that in 2023 it is still not possible to apply a consistent lens correction to a bunch of photos via preset without the risk of messing up photos with very unpredictable results.

    Here is the new issue I just opened: #198133

    ---

    The Lens Correction tool unfortunately has a long history of failure. Here is a new problem which happens in Build 16.2.3.32 (11312e2):

    • Open a photo
    • Set Light Falloff to 100
    • Save a Custom Preset with the Light Falloff value
    • Apply the Preset
    • Light Falloff value is still 100, but the correction is wrong (much too bright)
    • Clicking on the "Light Falloff" label (to temporarily revert to uncorrected) fixes the problem

    Here is a screencast to demonstrate the problem:
    https://cloud.kaiser.me/s/WPGTwBHJrCByWgi

    This also applies when using Light Falloff correction in a style.

    This might be related to #147964, #187902, #187900.

    ---

     

    1
  • Nico Kaiser

    I just realized, Copy & Paste for Distortion correction might also be broken again in 16.2.3, I'll re-open the ticket and do another screencast.

    0
  • Sebastian Reiprich

    Yesterday a felt a little relief after reading the release notes of the update. Reading all of this now makes me really angry…
    I once tried to create a script to set distortion correction to 100 hundred. But it did not work because C1 expects another value for this type of correction.

    0
  • Nico Kaiser

    Sebastian Reiprich Good to know. I also thought about applying the correction via AppleScript instead of typing "100" a thousand times, but never got that far.

    The "another value for thsi type of correction" seems to be the root of this problem. Instead of simply saving "100" (or maybe 1.0), the "LensGeoAbr" entry is saved (and presumably then copied/pasted) as "0,0;8289.2001953125,-80.5;12012.400390625,-222.899993896484;15735.5,-435|100.000000|1|100|-1", which – without knowing the internals – seems to be heavily dependent on my particular lens and its aperture/focal length of the picture.

    The last few updates on this only seem like a deperate attempt to convert back-and-forth these values but they all fail at some point (thus the "double" correction mentioned above and other funny effects).

    0
  • Nico Kaiser

    Here is my current "Test Suite" for the Lens Correction mess:

    Example photos: https://cloud.kaiser.me/s/zGw7mTsmN32SCBX

    • Create a new Session, import DSC00001.ARW and DSC00002.ARW

    Distortion correction (copy & paste):

    • Select DSC00001.ARW
    • The Distortion correction is already at 100
    • Copy the Distortion value and apply it to DSC00002.ARW
    • Make a New Variant of DSC00002.ARW
    • Set Distortion correction to 100 (manually enter the value) on the new variant
    • Both variants of DSC00002.ARW should look the same (still broken in 16.2.3)

    Light Falloff correction (copy & paste):

    • Select DSC00001.ARW
    • Set Light Falloff correction to 100
    • Copy the Falloff value and apply it to DSC00002.ARW
    • Make a New Variant of DSC00002.ARW
    • Set Light Falloff correction to 100 on the new variant
    • Both variants of DSC00002.ARW should look the same (This seems to work in 16.2.3)

    Light Falloff correction (preset):

    • Select DSC00001.ARW
    • Set Light Falloff correction to 100
    • Save Custom Preset in the menu of the tool
    • Apply the just saved preset
    • Applying the preset should not change the image (still broken in 16.2.3, corners get really bright now)

    (Sharpness Falloff is left out here because it is very hard to see, and I could live with never touching Sharpness Falloff at all)


    I considered making a script for this, but honestly I'm really done with this for today...

    0
  • Sebastian Reiprich

    I am starting to get tired of this as well. I pay for the Adobe subscription anyway. There is no real logical (at least for me) to pay extra to have C1 as well. Except that I am used to it more…

    But if you already do some testing add a test for CA correction as well. I used to analyze all of my images for CAs directly after import but at some point I noticed that this was messed up as well when copying and applying adjustments.

    The thing is that this bug is really hard to notice. It only became more visible when the bright vignette started to occur when re-opening a session. But it‘s been broken for so long and negatively affects image quality…

    0
  • Sebastian Reiprich

    I just thought about how changing the values that C1 expects from absolute to relative values would cause some issues as well. This would basically make all presets and styles which contain those corrections and have been created on an earlier version of C1 useless. And the reason would be hard to honestly communicate to the customers.
    Maybe they could add new additional variables for light fall off and distortion correction based on relative so C1 could handle both of them internally and create new presets and styles with the new ones only.

    0
  • Helen
    Admin

    Nico Kaiser Hi, huge thanks for sharing your "Test Suite", you did an awesome job that is highly appreciated. I hope you don't mind if I use your info to share the current status of the issue with our engineers.
    Light Falloff behavior has been fixed in the relation to Next Capture Adjustments and Copy & Apply tool, so we will look into the Styles and Presets behavior right away. It would be great if all the affected users can mention their support cases or create ones, so that I can jump into them, add those to the report and keep everyone updated.

    0
  • Sebastian Reiprich

    My support case is 166330 and I assume 152142 as well (I never got a reply for the latter)

    0
  • Jack W
    Admin

    Sebastian Reiprich You did receive an answer in #152142 but I can see Helen followed up on #16630 a matter of minutes ago. I'll leave you guys to it :) 

    0
  • Sebastian Reiprich

    Maybe I have deleted the answer to 152142 then. The only thing I could find in my mails regarding this case was a short note about how the situation in Ukraine is affecting the C1 team.

    However Helen just replied to the other case as you said.

    0
  • Sebastian Reiprich

    Just because I want to put this information in this forum as well (and because Nico already mentioned it):

     

    Since a few Versions C1 has support for Apple Script. And the documentation shows that you can also write a script to automatically set distortion correction on your images.

     

    I tried to do that as a workaround and since the slider in C1 lets you set values from 0-120 I assumed that the script requires a value of 100 to do a 100% correction. However this gave me an error message. So I tried a value of 1 and 1.0 and 10 and 10.0 and so on, but C1 always gives me an error message.

    It basically says the desired value cannot be set.
     
    So I selected an image in C1, manually set the distortion correction to 100 and saved this as a preset. I looked for the preset on my hard drive and opened it in the text editor. It looked like this:
    The value for „LensGeoAbr“ is very specific to say the least and I assume that this is an absolute value that C1 directly applies to every image this preset is used on instead of using a relative 100% correction for your specific lens and settings. And I assume that the „100“ at the end only shows the position of the slider in C1. So to the user it seems like a 100% correction because the slider says so, but under the hood some other values are used.
    0
  • Helen
    Admin

    We've recently created a separate post dedicated to Styles/Presets behavior. You can follow the updates here:
    https://support.captureone.com/hc/en-us/community/posts/13000419772573-Applying-Light-Falloff-as-a-part-of-Custom-Style-Preset-makes-the-image-look-overexposed-at-the-edges 

    0
  • Sebastian Reiprich

    Could you create one for the wrong behavior of distortion correction as well?

    0
  • Jarjan Fisher

    Still not fixed for the Windows version - I reported this bug in January and have since been promised 3x that it was fixed, 3x that turned out to be a false promise!

    0

Please sign in to leave a comment.