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

  • Official comment
    Helen
    Admin

    This issue is fixed in the new release of Capture One (16.2.3).
    Follow the link to download the latest version: https://www.captureone.com/en/account/download 

  • 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
  • Thodoris Chorianopoulos
    Admin

    Hello all. I understand the disappointment of some because of the nature of the bug and that it can prevent you from tethering a proper session. Perhaps the only workaround at the moment is to shoot without any Lens Adjustments (in that case Light Falloff), and add it later. The problem seems to be only when the Light Falloff is set to carry over to the next image as an adjustment.
    Also the nature of the bug is one of those that cannot be fixed in one release and it requires some time. Be sure that whoever creates a ticket will be inform as soon as the fix will be available and we will update this page here as well. So make sure that you follow this page to get any updates regarding known bugs.

    3
  • Michael Lake

    Ran into this and can confirm.

    2
  • Cali Creative

    I am also experiencing this problem, Exactly as Jack has described, except I'm using sessions, but everything else is the same... Has anyone found a way to fix this? 

    2
  • Nico Kaiser
    Unfortunately the Lens Correction tool is currently (and maybe has always been) broken and cannot be trusted at all. Here is why:
     
    When applying Distortion and Falloff correction, C1 does not save the amount value (e.g. "100"), but the actual correction values, which are specific to the camera, lens, aperture and focal length.
     
    When Lens Correction values are set for each individual image, they work fine.
     
    Now when these adjustments are copied and pasted to a different image taken with a different lens (or even only a different focal length or aperture), the correction values of the previous lens are applied, so the values are likely to be completely wrong (even when the value shows "100", this is misleading). This leads to sometimes subtle but sometimes very obvious distortions.
     
    What makes it worse though, is the fact that "automatic lens correction" is not always applied. E.g. for a Tamron 28-75mm lens, Distortion correction is applied only for some focal lengths. According to C1 support there is a threshold above which corrections are applied, but I consider this as a very bad design decision. There is no way to automatically enable Distortion correction to 100 for all (new or already existing) images (see above).
     
    Same applies to Light Falloff, which also is wrong when pasted from another image.
     
    Conclusion: Lens Correction values need to be typed in to every single image and cannot be copy & pasted between images.
     
    In version 16.1 (?) some things seem to have changed regarding Lens Correction, which introduced another bug:
     
    Copy & pasting Light Falloff values seems to somehow have improved ... until the Session/Catalog is closed and re-opened. Then, the correction seems to be applied twice, which leads to a very bright vignette in most cases. This also only happens when values are pasted.
     
    The combination of this bug and the poor design decision of trying to be smart by not always applying lens correction leads to the need of manually typing in "100" 2.000 times when importing 1.000 photos. This is more than annoying.
     
    This is a known issue (#147964, #187902) for quite some time now (I first reported this issue in 2021), and I really hope this bug is fixed soon and included in a patch version instead of a new ($$$) feature version.
    2
  • Jack

    I also have this problem.

    I'm using a catalogue rather than sessions.

    It started happening after upgrading to Capture One 23 Pro build 16.2.0.112 (250ab96). (Mac)

    Previously applied light falloff correction is massively over applied (for the same given value. e.g. "100") when re-opening the catalogue. Photos appear with hugely over exposed halo around them.

    If I reset the adjustment and then re-apply, it displays correctly, but only while the catalogue remains open. If I close the program and re-launch, it is over-applied again. I don't want to have to re-do the Light Falloff on thousands of photos every time I open the catalogue!

    Very frustrating.

    I have graphics acceleration switched off, as this has previously caused display issues too.

    1
  • Jack

    UPDATE/EDIT: Ignore this; I was wrong; the Light Falloff bug has returned today. Updating did not fix it.

     

    So I just updated from 16.2.0.112 (250ab96) to 16.2.1.13 (492d50d), which seems to have resolved the problem, EXCEPT:

    All of the images that I opened or work on whilst experiencing the issue, still have the incorrectly applied Light Falloff and need to be manually reset and reapplied.

    I'm pretty upset, since this is going to be a lot of work, since there's no easy way to filter these images, and no easy way to reapply the adjustment globally (copy/applying lens corrections produces very weird effects in C1, especially with zoom lenses, since it copies the actual adjustment instead of the slider value). Disappointing.

    I generally love C1, but the Lens correction tool is awful. Great lens profiles, but the implementation of global copy/apply of lens corrections is terrible (especially with zoom lenses).

    1
  • David Treagust

    Experiencing the same here too - Frustrating! 

    1
  • Christopher Manzeck

    I am also noting the same problem on my end. Super hard to even work with any images knowing that when I return to the session (after having closed it once), all of my images which have applied lens correction for light falloff will need to manually have that setting reset to zero and reapplied. This needs to be fixed asap before I get into the busy wedding season where I apply this to 1,000's of images and can't afford to go back and revisit each image, each time I close and reopen a session.

    1
  • Breezy

    This issue has happened for me for every session since upgrading to Capture One 23 build 16.1.1.16.

    Each time, I've been tethered shooting using light falloff adjustment. When I close the session and open it back up, every image's light falloff is set to 100 and images are overly bright and have a white halo. The even more frustrating part is that it doesn't seem to work to reset the light falloff and copy/apply over to all of the images. Only works on individual images. Super annoying. Please fix this. 

    1
  • Nico Kaiser

    What's a workaround once you did the shooting already? 

    The workaround (and fix for broken images) is resetting the Lens Corrections and manually type in the desired values for each and every image.

    1
  • Tim Nikischin

    Hi Thodoris, this is great news thank you so much! Looking forward to this update already!

    1
  • Nico Kaiser

    That's great news, looking forward to the 16.2.3 update!

    1
  • Tim Nikischin

    I started using Capture One 15.4.3.4 for my latest jobs and I just noticed the issue also happen in that version WTF ... really looking forward to the 16.2.3 release!

    1
  • 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
  • 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
  • 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
  • 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
  • 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
  • Łukasz Gałecki

    My post from 3 months ago (screens included):

    "This bug is present in CO since at least version 9. In my case it appears in all images from sessions I move between workstations. It is visible only in sessions workflow, catalogs are free of it. It often reapers when I move session to archive on different drive and reopen session some time later (probably because of different version of CO then one used to create original adjustments). Only fix I found is to reset lens correction tool and reapply correction. Below screen of two variants of same raf file, one affected and other after reseting and replaying correction. Overcorrection is visible in browser and it affects Mac and windows. Version of Capture One used is 16.2.5 so this bug fix is very far away from being implemented."

    link fork sake of clarity: https://support.captureone.com/hc/en-us/community/posts/10984244456349/comments/13983288782749

    At the moment I use version 16.3.3 and it only happened with one photo so far as I recall. Before with 16.2.5 almost all sessions I moved between workstations (Windows and Mac) where affected. It might not affect me anymore since I use almost exclusively manufacturers correction profiles for my GFX photos. One in the post I linked use CO profile.

    1
  • Sunil Thakkar

    Just checked this.

    Not facing this issue on Mac with the same build.

    0
  • Jack

    UPDATE/EDIT: Ignore the above; I was wrong; the Light Falloff bug has returned today. Updating did not fix it.

    0
  • FirstName LastName

    I'm experiencing the same but it applies to both Light Falloff and Vignette.

    0
  • Thodoris Chorianopoulos
    Admin

    Hello there. Can you please create a ticket for the support team and please include a screen recording for the Vignette issue you are mentioning?

    0
  • Justin Patterson

    Same issue on my end. I have a ticket open so hopefully they are working on a fix. Super annoying to have to copy, reset, and then apply adjustments each time I reopen a session. This only started happening since the last 2 most recent updates.

    0
  • Tim Nikischin

    Same here... super annoying. Opened a support ticket (#192834). Startet on 16.1.1 for me, but updated from v15 before.

    Most likely only in combination with tethered shoots

    0
  • Jack

    I also submitted a support ticket.
    I was assured they’re working on it, but the latest update didn’t fix it.
    Very frustrating, it's been a month and I’m not doing any editing since I always do lens correction and it feels unusable at the moment.

    0
  • Tim Nikischin

    What's a workaround once you did the shooting already? Not even removing the images from the catalog and importing them again helped. After restart same issue again. Impossible to use Capture One to edit my pictures unfortunately.

    0
  • Tim Nikischin

    Thank you so much for the additional information! 

    I have tried again with v15 and the bug does not happen on this version. Although I agree the lens correction tool always has been a bit buggy (like mixing light falloff and lens distortion values, ...).

    Really don't understand though why this bug only happens on pictures shot tethered in v16, not with any others (or at least I luckily haven't yet noticed) shot either tethered with v15 or shot in camera. Also it seems like there's nothing too bad burned into the images, as if I open the images shot tethered in v16 with the v15, I do not have the double light falloff applied in v15 after restart.

    So either I need to go back to v15 with a new catalog, as it's not possible to open my v16 catalog with v15 or I will be only able to shoot in camera as I am not going to apply the same setting manually on a few thousand pictures.

    Super annoying considering the fact, the issue has been addressed 5 months ago already and it doesn't looks like it can be expected to be fixed too soon: https://support.captureone.com/hc/en-us/community/posts/8932390678941-Extremely-annoying-issue-with-double-applied-vignette-support-very-slow-to-respond?page=1#community_comment_12009326314909

    0

Please sign in to leave a comment.