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. ⚠️

After 16.2.0 Update  Smart adjustment is not working

Comments

11 comments

  • Permanently deleted user

    I'm having the same issue they don't seem to be working at all. 

    0
  • FirstName LastName

    I'm also having this issue, doesn't work at all in batches

    0
  • Stephen Kimmel

    Same here. Doesn't work at all.

    0
  • FirstName LastName

    Any of you guys get this working?

    0
  • Stephen Kimmel

    Yes. Updated to newest version then rebooted computer and then it was working again.

    0
  • FirstName LastName

    That didn't work for me but I think I solved the problem. If you're doing bulk adjustments and if just ONE of the RAW files is very underexposed (like a flash not going off) and overexposed, it messes up the entire sequence. I've been trying to contact CaptureOne but they take absolutely forever to respond and keep telling me its working fine or I won't hear back from them until there's an update and they tell me to try the new update.

    0
  • Michał Dudek

    I have the same problem. It works for single photos but not for multiple photos.

    0
  • FirstName LastName

    @Michał Dudek make sure you put in a support ticket to let them know it’s not working. I did and they’re taking forever to respond so my guess is that they’re not getting enough complaints because bulk smart adjustments is a pretty niche thing. I have several different cameras and computers and it doesn’t work on any of them post 16.2.0, it’s definitely broken and not just me

    0
  • Stephen Kimmel

    I almost forgot, the other thing I did was reset preferences.  If you haven't already, worth a try:

     

    https://support.captureone.com/hc/en-us/articles/360003121597-Reset-the-application-s-preferences-file 

    0
  • FirstName LastName

    Stephen Kimmel just tried resetting preferences and that didn't work either.

    0
  • eric park

    I hope this helps anyone who finds this post.
    I found that the cause of this bug is language.
    This bug only occurred in Windows from v16.2 to v16.5,
    and I found that this is a language issue.
    I use the Korean version.
    Change the session or catalog name from Korean to English, re-run capture one, and import the session and catalog. This bug will disappear.
    If you are using a language from another country, change the catalog or session name to English immediately and test it.
    I hope you can solve your problem.
    If it is not a language issue, I am sorry.
    In my case, at least after a long time of trying, it was definitely a language issue.

    0

Post is closed for comments.