Skip to main content

Mac - Applying Light Falloff as a part of Custom Style/Preset makes the image look overexposed at the edges

Implemented

Comments

10 comments

  • Official comment
    Helen
    Admin

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

    The release notes are available here: https://support.captureone.com/hc/en-us/categories/360000430178-Release-notes 

  • Jarjan Fisher

    Hi Helen,

    I've reported this bug in January and have been kept on a leash with vague promises since then (that's 7 months now). Last week I was informed that the bug had been fixed, which turned out not to be true.

    I'd like to be reassured that this will be fixed, with a clear timeline. And I'd like to be reassured that this will be fixed within the perpetual license version that I paid for.

    Thank you,

    JJ

    1
  • Rob

    I installed Capture One today and used it for the first time, experimenting with a few features. Despite my lack of experience with the software, the overexposed areas at the edges immediately caught my attention. I can't help but wonder how no one else from capture one has noticed it. Thanks to Jarjan for your post – it saved me hours of searching to figure out if the issue was due to my mistake

    1
  • Helen
    Admin

    Jarjan Fisher Hi, Light Falloff issue has been fixed in the relation to Next Capture Adjustments and Copy & Apply tool, maybe you've seen this information posted in the main thread. Styles behavior is currently under investigation. When we get a confirmation from our engineers regarding the build that includes a fix, we'll share the update both here and via email (if you have an ongoing case with support). 

     

    0
  • Jarjan Fisher

    Helen, Actually, No. I reported this bug and clearly mentioned that it was related to the use of custom styles. I thgen received an email from customer support that my issuie had been fixed.

    I fact, I've now been told twice that my issue was fixed, as it seems customer service can't keep track of it's own messages.

    Also, we're again a month later, and still no news on a fix? I dont get the ímpression that Capture One is taking this serious at all?

    An update would be appreciated. Also, no-one has so far answered my two questions:

    - When can we expect a fix?

    - Can you reassure me that it will be fixed for the perpetual license that I bought?

    0
  • Helen
    Admin

    Jarjan Fisher we're glad to announce that this issue is fixed in 16.2.4. The latest version is already available for download.

    0
  • Jarjan Fisher

    It's also only fixed for the OSX/Apple version. Not for the Windows version that I use. So again I've been misinformed. (Not only here, the same thing happened again to my support ticket as well.)

    And... we're now out of the free updates for my perpetual license. I'm really, really unhappy with CaptureOne.

    1
  • Sebastian Reiprich

    Can anyone confirm that it is fixed on MacOS at least? I didn’t really have the time to try it yet.

    0
  • Jarjan Fisher

    My turn to post an update. It seems like I made a mistake when intially testing the lastest update. And it seems the issue IS fixed, for WIN, in version 16.2.5 (the lastest update that was put online this week).

    0
  • Andreas

    Its back again with Build 16.4.2.1 (97ca21a) on a mac!

    1

Please sign in to leave a comment.