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 Not a feature request
Workspace Feature requests
Categories Capture One Pro
Created by Benjamin Kim
Created on Dec 8, 2024

Capture One requires better optimization for performance and stability

I hate to say this but Capture One sucks in many ways and yet, they aren't fixing problems and accepting feedbacks. One of the biggest problem with Capture One is the optimization which related to the performance and stability.I directly compared with Adobe Lightroom Classic and it was WAY faster and stable than Capture One Pro in many ways.

Some issues I faced:

1. Whenever I hold down the arrow key to look through images, Capture One freezes and crashes. What kind of bug is this?

2. During culling, it takes 2–3 seconds to move to the next image.

3. The preview generation speed is slow. Even the latest version is slower than LR Classic.

4. Compressed files heavily impact performance. LR Classic has no issues with compressed files and it's so stupid.

5. The overall performance is poor and slow. The export speed is a great proof.

6. The software crashes randomly without any apparent reason. Too unstable to use it for digitech works.


With LR Classic, it never had problems with same file formats. For example, the export speed is 2~4 times slower than LR Classic and this had been proven tons of times. Why? While LR Classic used all CPU cores, Capture One used only 2 CPU cores while wasting resources with GPU which doesn't really improve the performance. I'm using full speced M1 Max MBP and tested on many macOS and results were same: Capture One is slow and unstable. Clean installing macOS did not solve those issues which I can conclude that the optimization is literally poor.


I can tell you that Capture One's optimization is completely messed up. They cant even bring updates for macOS Sequoia as of today which is almost 3 months. I'm a professional who use Capture One all the time and this is NOT what I've been paying for. The support team was not helpful and even said we have no idea what to do but only apologized. One of the solution they provided was changing the langugae of the file which has nothing to do with the problem and again, LR Classic had no issues.


I am not the only one complaining about this issue and yet, Capture One is not listening but ignoring for several years instead of making excuses and focusing on something else. This is why a lot of professionals wrote an open letter to Capture One Pro several years ago. Did they not learn anything from it? I'm sure a lot of users aren't just here or not speaking about it but def mad about Capture One's poor optimization.


No more excuses, just do better with optimization in terms of performance and stability.


  • Admin
    Capture One Product Manager
    Reply
    |
    Dec 17, 2024

    Closing this down as it is not a feature request.

    If you have any issues with stability, crashes or bugs, please open a support case here: https://support.captureone.com/hc/en-us/requests/new

  • Phrank 303
    Reply
    |
    Dec 15, 2024

    Well i only work on a basic MBP M1 with 16GB RAM and 16.3.7.

    It seems like 200.000 photos are the maximum you can handle – LR might be the double. I don't know how many times and i got the rainbowball of death and have to force quit C1…

    I lost a bit faith C1 can be used for proper DAM any soon. Asking for improvemnets since years.

    Doing the management now with PM and Peakto and try to keep C1 catalogs small as possible only for RAW editing.

  • Thomas Kyhn Rovsing Hjørnet
    Reply
    |
    Dec 9, 2024

    As asked in the forum: Is this with catalogues or sessions? If catalogues, how large are they, i.e. how many images?