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

10 slower than 9 on Retina MBP

Paul1121
Seeing claims in the release notes of quicker performance when making adjustments in v10 I was excited to download the update.

Unfortunately the opposite is true. I now have 9 and 10 installed on my system and can go back and forth and clearly see that with v10 there are hiccups and delays when switching between images and/or making adjustments such as exposure/wb that are not there with v9. Disappointing.
0

Comments

5 comments

Date Votes
  • Christian Gruner
    Please contact our Support, and let them take a look at your setup.
    0
  • Sergey Grachev
    The same issue is here ! Not retina yet, but Macbook pro 2011, SSD, 16 gb RAM.! 10 Capture one much slower than 9. It's like slow motion right now !!! When I start to use 10, my current catalog was open without any question, and now I can't open it by version 9 ! Thank you very much for that guys !!!
    0
  • NNN635158767546269381
    Hi!

    C1P10 got nice new features. Here, it's not slower, but not really faster as well.

    I think, the software got release a little to early. I think, the software will just get mature in a few mouths, after some bugs fixed...

    I already upgraded. However, I think PhaseOne should release more "mature" software.

    Regards
    0
  • antonioyussif
    Same here, Version 10 of Capture One runs slower than version when browsing images.
    My Setup is MacBook Pro retina Mid-2015, 2.2 Ghz i7, 16 Gygs RAM, Intel Iris Pro. Will submit this to support anyway in hopes of having this resolved.
    0
  • Permanently deleted user
    Hello. Same problem with an other machine : 10 slower than 9 on Imac 4k (16 Go RAM and 1To Fusion druive).
    To sum up : GOOD performance for editing, BAD performance for browsing.
    The différence is huge for large cataloge (15000 pictures). Opening the whole catalog, select a variant could take over 1 minute before you can begin to edit. The simple action to quit capture one (without backup) need sometimes 40 secondes. And the spinning beach ball appears frequently when browsing. Howewer, more 20 minutes after launching, the navigation becomes - almost - fluid. As an engine that needs to warm up before to be powerfull. But it's not a solution ☹️
    I submitted a support case. Wait and see. But for now, i stay with C1 9.
    0

Post is closed for comments.