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

Performance Issue C1 16.2 on Mac

Comments

7 comments

  • Abbott Schindler

    Since performance didn't improve when you tried the current version of C1, I suspect that something in your setup is amiss. I can open collections with 5-10k images in a few seconds in my 55k image referenced library (stored on a Thunderbolt 4 connected SSD), editing is responsive and I've been happy with the way everything works. Same when I ran 15.4 on Ventura (I upgraded mostly for the AI Masking features).

    I'm currently running v16.3.8 on a M2 MBP Max and a Studio Ultra running Sonoma 14.6 (I'm waiting a while longer for 14.7), 16GB memory, 1 TB SSD, and it runs just fine—no noticeable difference between Ventura and Sonoma. What Support told you means 2 things to me: 1) Capture One hasn't qualified/certified your version on the OS you're using, so they don't support it, and 2) not being supported doesn't mean that it won't run fine, but they're not going to be able to help if a problem arises...so you're on your own. With that in mind..,

    First thing: how full is the disk you're working off of? It sounds like you may not have sufficient free space on your internal SSD and/or external disk(s) (C1 does a lot of caching, for example). Have a look at System Information (Option-click on the Apple menu) and verify that you've got >20% free (I keep ~50% free). Be sure to pay attention to what the system's using for snapshots, which can consume a lot of "invisible" space. Also, have you tried quitting other apps when you're using Capture One?

    Next: what are the speed of your card(s) and reader? I use 512 GB Delkin Power CFexpress Type B cards on my 45mpxl camera, connected to either a ProGrade USB 3.2 or an OWC Atlas FXR Thunderbolt 4 reader, and images are imported either to the MBP's internal SSD or to a TB4 connected SSD. In all cases, transfers happen very quickly; on the OWC reader I measure >1.5 GB/sec (the ProGrade's slower at only ~.6 GB/s). A slow card can impact you badly. Note that, at least with some older 128 GB CFexpress Type B cards, transfer rates can be a LOT slower because of the way the cards were constructed.

    Check your C1 Settings > Image > Preview Image Size and be sure that it's set appropriately for your display. Using too small of a preview can cause preview generation delays when editing images. And if previews aren't already generated or are too small, opening large collections slows down a LOT. (Is your library referenced or managed?)

    There may be other things going on, but these are the ones that come to mind first...

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Have you created a new catalog and imported your existing slow catalog to it to see if that improves things? Perhaps your existing catalog has some cruft or bad indexing that is dragging it down. The core of the catalogs is a SQLITE 3 database. The tables have indexes that need maintenance every so often. It is good to run a catalog verify periodically because it will also optimize the catalog tables and indexes.

    1
  • Fabrizio Giudici (stoppingdown)

    I'm using an older MacBook Pro (2019 16", still Intel cores) with 32GB of RAM and I don't see the specific problems you see during import (in the past months I've imported even more than a thousand photos from a single card). I second Walter's suggestion to try a test with a fresh catalog. Also, do you have the “Auto Adjust” option in the importer enabled? Some auto adjust options, such as auto dust removal, slow down dramatically the import speed — even though this should slow down things even when you use the workaround (first copy to SSD and then import from SSD).

    BTW, how faster is the workaround?

    0
  • Walter Rowe
    Moderator
    Top Commenter

    Also .. do you have auto-syncing enabled for metadata? That is a HUGE performance suck. Turn it OFF if it is on..

    0
  • FirstName LastName

    Hi, 

    first of all, thank you for your support!

    I have tried the import on my second Macbook (M3) with a new catalog, so that it is also a different hardware. It is just as slow here too. I do not use any Auto adjust or things like that. Auto-Sync is disabled. Preview size is correct and my SSD has more than enough space.

    The card reader cannot be the problem, only the import with “copy to” in Capture one is extremely slow. If you copy the RAW data manually to the SSD using Finder, it is extremely fast. Importing in LR is also extremely fast.
    The workaround with manual copying and then only adding to the catalog brings about a time factor of 5-10.

    By the way, deleting images from the hard disk (emptying the recycle bin with deletion) also takes 3-4 hours for 1000 images ;)

    But I have found out something else...
    The preview when scrolling through the images is extremely slow if there are also a few TIF files in the folder. Generating the preview data of TIF files seems to take an extremely long time and blocks the generation of the other preview images. Apparently Capture One does not save the preview images for very long either? Folders with only RAW files are much faster.

    I also googled the problem. Apparently a few more people have the exact same problems with Capture One and M3 MacBooks... 

    By the way, Capture One support has tried to help me despite the outdated version. Even if no solution was found, I give Capture One a lot of credit. The personal support is also a reason why I don't want to switch to LR (yet) despite the problems.

    0
  • FirstName LastName

    At least I could solve one problem now -  Slow speed when scrolling through the images, it takes long to generate previews:

    I found the solution at the website of Thomas Fitzgerald. One have to use the native resolution of the MacBook screen (3456x2234 px). Then everything is fast  But you can hardly read anything. How do you handle the resolution on the Macbook?

    Alex

    0
  • Fabrizio Giudici (stoppingdown)

    How do you handle the resolution on the Macbook?

    Unfortunately it's hard. I can't read with the full native resolution, so I trade off with a slightly inferior resolution (fortunately I don't have the scrolling problem you experience). Even so, it's hard and often I have to resort to the system magnifying glass (in the accessibility options of the system settings) to enlarge portions of the screen.

    You can vote this request to add an option for enlarging fonts.

    https://captureone.ideas.aha.io/ideas/FR-I-1424

     

    0

Please sign in to leave a comment.