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

Capture One 20 - Slow - Mac

Comments

7 comments

  • Ian Wilson
    Moderator
    Top Commenter

    My MacBook Pro (Late 2012) is a little bit like that (but not as slow as your iMac sounds). But my iMac which is the same vintage and similar spec to yours is really good. (I actually have less RAM than you do.) So I would expect you to be OK.

    What size are your previews set to? (I don't know if it would make a difference, but I wonder if there is an issue if they are not large enough.) Also where are the images stored - an internal drive or an external one?

    Ian 

    0
  • Christopher Manzeck

    Good questions re: preview sizes and image locations!

    Preview image size is I believe set to the standard; 2048. Curious to see what yours are set to for the iMac ... it's a reasonable conclusion that if the preview images are actually too small, upscaling them to refresh edits could take extra time (which again, shouldn't be an issue anyway with the specs on this iMac, but I digress). Images are stored on the internal SSD within the iMac.

    I'm wondering if this has to do with using a session vs a catalog ... may try to load the images into a brand new catalog and see if there is a performance difference. I'll also try with higher scaled previews.

    Do you use sessions or catalog? Your preview size?

    -Chris

    0
  • Ian Wilson
    Moderator
    Top Commenter

    I'm away from home at the moment, so I've only got the MacBook to hand. I have a large(ish) catalog on the iMac (just under 40,000 images, I think). My preview size was set to 2560, which I think is actually the standard, but with the new iMac I think I changed it to 3840, though I didn't upgrade the previews on all existing images. 

    I use sessions initially, typically on the MacBook and then transfer them to the iMac, and then add the keepers (basically the Selects folder images) to the catalog. I don't see why it should struggle with a session though. Typically it would have fewer images and have less to worry about. 

    You could increase the preview size for some images and see if it makes a difference. You could also try turning off hardware acceleration and see if (counter-intuitively) it is better. And perhaps then turn it on again and see if that persuades Capture One to set it up again. 

    After that I am out of ideas, but perhaps someone will come along who has other things to suggest.

    I have to say that it all works so much better for me now I have my new iMac, compared with my previous 2011 one, so I would hope that you can get to the bottom of this and see the performance that you ought to with that spec.

    Ian

    0
  • RC Photo

    To my understanding:

    If your previews are smaller than the screen resolution, CO will load the full size image every time the image is selected and an edit (e.g. WB change) is done. This would slow down the whole system. I.e., you might want to set the preview size to 5120 px for best performance (also consider to recreate the preview images)

     

    Additionally, the setting for the XMP synchronisation will have a huge impact (e.g. full synchronisation will cause that CO scans all images in the session/catalog if there are any changes to be applied in either direction)

    0
  • Micaela McLucas

    SO SLOW FOR ME TOO !!  so frustrating !! never had an issue with any other version of capture one. I run of 2018 Macbook Pro fully loaded. 

    support says its because im running off hard drives but thats never been an issue in the past. I literally cant even rotate images in sessions. Ive toggled on & off the hardware accelerator i've tried everything. 

    Running off latest version of C1

    my mind is also boggled 

    0
  • RC Photo

    For understanding, what is slowing down your systems, please check with activity monitor

    • How does the CPU usage look like?  Can be shown via 'Activity Monitor' -> 'Window' -> 'CPU History'
    • How does the GPU usage look like? Can be shown via ''Activity Monitor' -> 'Window' -> 'GPU History'
    • How much memory is used? Can be shown in 'Activity Monitor'
    • HDD or SSD load is more difficult to check but if other topics are ok the problem might be located there (XMP synchronisation setting, image preview too small for the screen resolution, ...)
    • If items need to be loaded over a network connection, this can also influence the performance a lot.

    As reference, I do not seem to have performance issues with my MBP 13" [(2019): i7 2.8 GHz, 16GB RAM, 1TB SSD] and 46 MPix Raw-Files

    0
  • Alex Shapovalov

    I believe problem that C1 broke to support GPU and with HWA at AUTO settings program moves barely. Only solution I found to date is HWA set NEVER. Windows thread have the same problem, that's the point

    0

Post is closed for comments.