Skip to Main Content
Improve Capture One

Request a new feature, or support for a camera/lens that you would like to use in Capture One.

Status Awaiting review
Workspace Feature requests
Categories Capture One Pro
Created by Guest
Created on May 22, 2023

OM-1 HighRes Sharpening

What problem do you see this solving?

High resolution RAWs (50/80MP) from Olympus and OMDS camera's don't sharpen well using CO's sharpening tool.

When was the last time you were affected by this lack of functionality, or specific tool?

Every week.

Current workaround

Are you using any workarounds or other solutions to achieve your goals in Capture One?

I'm round tripping to DXO to get this support, or just using DXO to edit these files.

  • Marcin Mrzygłocki
    Reply
    |
    Oct 30, 2023

    374108460437 this would match quite well how denoising basically does not change anything on my A7RV files, forcing me to likewise use another tool like DeNoise AI.

  • Nicolas Det
    Reply
    |
    Oct 30, 2023

    Add also similar improvement other OM System / Olympus camera with HighRes shoot: EM-1 Mark III , EM1X.

    Indeed, the sharpening out of the camera as well as the sharpening in OM Workspace is a lot of better as in C1. Unfortunately, one gains sharpness but loose the colours controls.

  • Andy Reynolds
    Reply
    |
    Sep 9, 2023

    This would really help me too. I use Hi-Res on my EM1 MK3  for expanding dynamic range (rather than extra resolution) and am finding it really useful. But the processing of the files has been problematic, they can be really soft without some sharpening and I've not yet found the best way to sharpen them successfully.

  • Guest
    Reply
    |
    May 28, 2023

    This is interesting. I don't work for C1, but I can imagine that, if their algorithm is based on bottom-up math, instead of top-down math (i.e. starting with pixels and working their way up to the bigger picture, rather than starting with the overall image noise and working their way down) then this would definitely be a problem.

    I've noticed in other parts of their app that they have limitations on the sample size/granularity of something, so it wouldn't surprise me if there was an inherent size range assumption baked into their feature parameters.

     

  • +3