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 really SLOW?

Comments

25 comments

  • Robert Farhi
    Hi,

    Did you try with hardware acceleration off ?
    Robert
    0
  • SFA
    milo1234 wrote:
    Having massive problems running 20. It's really slow I can feel my computer struggling to keep up. When I click on a file the preview takes a long time to load.
    Granted my computer is a bit older (Mac) but it ran 12 no problems.
    I reduced the size of previews and hardware acceleration is on. Is there anything else I can do to speed it up?
    Anyone else having these problems?


    Are you running with a Catalogue?

    Have you upgraded the catalogue from V12 already?

    How many images in the catalogue?

    Are you running a mass update for:

    Previews (the size change you mentioned.)
    Thumbnails (thumbnail resolution changes for V20 although I don't think auto regeneration applies)
    Processing Engine version for the images.

    If you open the Activities Window is anything being reported?


    Grant
    0
  • Paul Steunebrink
    milo1234 wrote:
    ...
    I reduced the size of previews and hardware acceleration is on.

    This may actually slow down your Capture One experience if set to low in relation to your screen resolution.
    0
  • Adrian Mauricio

    Buenas tardes;

    También estoy teniendo problemas lentos con mi C1-20 (estoy probando). Tengo un catálogo de 9500 imágenes y me di cuenta de que cuando uso más de 3 capas es imposible trabajar; Cualquier cambio que realice en la capa inferior o en cualquier capa nueva tarda de 3 a 10 segundos y esto es insoportable.


    Me he dado cuenta de que si dejo el perfil de la lente en "Genérico", los problemas de lentitud desaparecerán.

    Mi computadora: Win10 pro 64-bit / Intel Core i5 9600KF / 32GB RAM / Nvidia GTX 1050.

    Saludos.

    0
  • Clayton Hairs

    I've worked with C1 for nearly 8 years....

    I am running a 3GHz Mac Pro (10 core - Intel E5) 32GB RAM - so plenty of grunt ... I work on10GB individual files in PS with this machine with little to no sweat....even while 12 other 100MP files open at the same time...

    but am finding this release of C1 has resulted in preview of images taking an incredibly long time to render to full resolution ....

    I am working with IQ3 files and D850 (nikon) files - about 50:50 ratio in the folder - total images in the session is 1430 so a fair number but prior to this upgrade I'm almost certain it didn't take this long to render files - I seem to be waiting forever (sometimes up to 5 minutes) to allow me to preview individual images at 100% in order to check focus...not quite the whizz bang upgrade I was led to believe it would be sadly....

    anyone else finding this problem?

    1
  • Bryan Moberly

    I usually wait to update software. However, I updated to 13.1 because I ASSuMEd it would run just fine and I wanted the features that came with it. It is so slow that it is unusable. I went back to 13.0 and now I am having issues with it due to the fact that I started to make adjustments to some files in 13.1 and it is not compatible. Preview has not rendered in over 10 minutes!

    Running OS 10.13.6, MacPro Late 2013 with 128 GB memory.

    0
  • Clayton Hairs

    I'm going to move back to the older C1 20 now - I am also working on a Late 2013 Mac Pro .... wonder if that might be the reason....anyhow doesn't seem P1 or C1 developers pay much attention to these posts sadly...

    0
  • Christian Palm

    Cheers,

     

    I also am experiencing immensly slowness in C 20.1, since upgrading from 20. Rendering previews takes AGES, and working in the catalogue is also very very slow (creating a variant for example takes almost 4 sec now)

    I did not have this problem in 20.0 

    I have almost 70000 pics in the catalogue. It seems a problem with updating the old catalogue to the new one. That ist because when I create an absolute new catalogue it´s very fast! What can I do? I don´t want to recreate my huge catalogue again...

    I am using a Macbook Pro 2018, it´s very fast and has 16 GB RAM. 

    1
  • Paul Steunebrink

    It seems a problem with updating the old catalogue to the new one. That ist because when I create an absolute new catalogue it´s very fast! What can I do? I don´t want to recreate my huge catalogue again...

    Christian,

    The answer is in your remark. Create a new catalog and import the old catalog that is slow into the new catalog.

    Beware, do not import the images, but import the entire catalog via File menu > Import Catalog.

    0
  • Christian Palm

    Thank you for the very quick answer. I will try it now.

    0
  • Evaan Kheraj

    Having same issues with slow down. How does this stuff get released with such obvious problems?

     

    0
  • Christian Palm

    @Evaan: an old problem at Phase One: they release too early and have serious issues with almost each update. 

     

    BUT: Importing the old catalogue into a new catalogue solved my problems. Which took around 15 hours - so beware ;) 65000 pics have been imported.

    0
  • Alex Pott

    Yeah maybe it seems I should have checked here first.  I just upgraded to V20 on Windows 10 running on a pretty beastly i7 Dell XPS.  I was using V11 and it was snappy.  Now it's molasses.  I shoot fashion so it's not a one-click-and-wait deal.  The clients want to see the poses coming in quick and fast but Capture is just struggling.

    I'm shooting on Nikon D850 so I realise they are big files but the only thing that has changed is the version of capture.  V11 dealt fine with D850.

    It seems the import of the tethered image is reasonable fast but then it takes 2 seconds to apply the white balance from the last shot.  V11 did this in a flash.  Is this all getting too bloaty now with so many fancy features that it can't do quick tethered shooting?  I shoot into a session - so nothing to do with background catalogue upgrading or any of that stuff.

    Super disappointing if this is the new state of play.

    1
  • David Bleeker

    This is such a pain!

    Will importing the old catalogue into a new catalogue  also import user collections?

     

    I really hope so!!!

     

    0
  • Christian Palm

    Of course! User collections are part of the catalogue and will be imported.

    0
  • George Lippert

    Capture One 20 on my Late 2018 mac Mini with internal SSD is horribly slow. It took over an hour to import and generate previews for about 7000 medium sized JPG files. And I noticed that during all that, it was using about 30% of one of the 6 CPU physical cores, 10% to 20% of the other 5 physical cores, and 0% of the six hyperthreaded cores. That is just bad coding, I would think. The Activity Monitor shows that this app is not obviously I/O bound while doing this. So it is simply not making use of the CPU effectively. I've filed a ticket on this, send in the logs, submitted a screen-capture movie of it, and the support response was that they can not reproduce the problem. Really? I asked if I am alone in experiencing this incredible slowness. Silence. This version should never gotten out of alpha testing! Right now I am watching it generate previews at the incredible rate of about 2 per second, using about 1/12 of my CPU. Glacial.

    0
  • George Lippert

    Update to my last post: I bought Lightroom and duplicated the import of the 7000 photos mentioned above. Instead of Capture One 20's performance of taking well over an hour and using only  1/12 of my CPU capability, Lightroom took 15 minutes and had all of my cores, real and hyper, lit up for a total utilization of about 7/12 on average. And Lightroom was substantially more responsive on tasks like selecting photos by keyword.

    0
  • David Car

    I'm getting nervous now! I just subscribed to CO20 and am noticing it takes ages to load my catalogue. I've only imported 5,600 images from my Lightroom catalogue and it chokes trying to load the thumbnail image previews. I have the preview generation set to my long screen resolution size. I've "rebuilt" these thumbnails a few times, but every time I load up CO20 it opens some quickly and about half don't, and it takes a long time to fill in. I'm running on a newer Macbook Pro with 16GB RAM and 2TB Samsung SSD. It's not a problem with LR. It's not file specific as it does this with jpg, tif and NEF files. I really do prefer CO over LR and am hoping to make the jump, but if I can't work in it, not sure if I'll be ready to make the switch. I hope they are listening and will let us know they acknowledge this and are working on a fix.

    0
  • Jerry C

    I have found shutting down and restarting my iMac Pro (3GHz 10-core Intel Xeon W, 64 GB 2666 Mhz DDR4 RAM, Radeon Pro Vega 64 16 GB; referenced files on a 4TB USB 3 G Hard Drive) very often solves performance problems. The worst of these is a delay in displaying All Images that seems to be infinite and requires a forced quit (that can corrupt the database, so I always do a backup before doing anything that has a history of behavior that might require a force quit).

    So before testing speed, I make a backup and do a shutdown and reboot. I also unplug to reset the SMC. Times with version 13.1:

    Opening my catalog with 60,500 images takes 38 sec (12 sec faster than 13.0.4)

    Selecting All Images takes 13 sec to display and 8 seconds to redisplay the same after navigating to another folder

    Backing up the catalog takes 17 seconds (13 sec faster than 13.0.4)

    Importing, exporting and adjusting times pending

    My experience with the healing powers of rebooting suggests the wide variations in users' experience is not only related to hardware, but also related to how the computer handles conflicts related other software, memory, etc. Some of this may relate to the C1 coding, but perhaps not all. As software and hardware get faster and more complex, colliding electrons are bound to cause occasional mayhem.

    0
  • David Leyes

    i changed my preview size to match my resolution size to 5120 and my proofing has become so much faster : )

    0
  • Anand Sankaran

    @george - I am struggling with this as well. Previews do not work for me at all.

    Capture One is a piece of shit software.  I ended up buying Photo Mechanic for cataloging and use Capture One just for editing at the moment.  I will not upgrade it ever and when I get a new camera, look at other RAW editors. (Not a fan of Adobe subscription, but it at least works).

    0
  • Ben Broomfield

    Any updates on this? I've got a 16" specced Macbook Pro, and a new M1 Mac Mini, and Capture One is really slow with previews just taking ages to load anything. Even heal brush slowing the program down massively.

    I first got Capture One a year ago with an early version of 20, was fantastic. Upgraded to 20.1(?) and the problems started. Tried free versions of each upgrade, same issues. 

    Just used Lightroom and... well super fast now. 

    0
  • FirstName LastName

    It just took my Dell XPS 17 (2021), with a 11th gen Intel i9 and RTX 3060, about 8 minutes to import 38 raw files from a Canon 5D IV.  That's about 12 seconds per file.  Capture One is shaping up to be my worst photography purchase in my 14-year history in the hobby.

    0
  • BeO
    Top Commenter

    Dell xps 13 (2020) with i7 1065G7, not even a dedicated gfx card. 39 raw files from Nikon Z7 in way under a minute.

    I know the processing for Canon raw files generally differ from the processing of raw files from other manufacturers (at least this was the case a few years back) but if it takes 8 minutes, even for Canon files, there must be something wrong. Don't call C1 the worst purchase just yet.

    Did you check in the preferences if hardware acceleration is enabled?

    0
  • FirstName LastName

    Hardware acceleration is enabled.  Thanks for pointing me towards that:

    For giggles, I just toggled both hardware accelerations off, restarted Capture One, and did an import.  Now it's as fast as I'd expect!

    Because I enjoy spending my time this way, I toggled both hardware acceleration settings back on, restarted Capture One, and did another import.  It is a similar speed as with them toggled off!  (And much, much faster than before when they were set this way!)

    Capture One redeemed?  Sheesh.

    0

Post is closed for comments.