cap one pro 20 - so slow on my macbook pro (with 16 GB ram), almost unusable.
After Cap1 pro 11 kept crashing I decided to upgrade to C1pro 20. I am running it using sessions on a macbook pro with 16 GB ram, with files stored and accessed from a NAS drive using a wireless network. It has ground to a halt, with the spinning wheel of death on most of the time. Activity monitor shows no other software running of any consequence. C1 20 is using less than 10% CPU at any one time, but idle wake ups are in the hundreds and thousands for C1 20 - so something weird is going on. Any suggestions on how I can make this work? Am I asking too much for it to run across a network.
-
I would recommend moving your files to the SSD of your laptop to speed things up. If you do not have the space, the next best thins would be an external SSD that is attached through USB C (something like Samsung T5). This might even be a setup that is explicitly unsupported by C1. And, let me put it that way: Apple is not particularly famous for providing top notch network file access functionality with OS X.
0 -
Many capture one performance complaints mention the use of NAS drives. I do not know, but suspect that the way Capture One monitors changes especially when using sessions doesn't work well with a NAS.
Capture One works OK (not a speed demon, but certainly usable) when I keep my Catalog file when using a catalog and my Session files when using sessions on my main drive. I keep my images on an external drive, another SSD that is USB-C connected. Another guess: capture one needs to access/update .cosessiondb and .cocatalogdb files often. Keeping these files on your fastest drive may help performance.
0 -
Thanks for your prompt response.
So if I interpret what you say, if I locate the actual C1 cosessiondb files for each session on a SSD drive attached via USB to my computer, but store the image files I am working on on a NAS drive, then that should speed things up and prevent crashes? I don't have enough space on my computer HD to store the volume of material I have as images, so I need to retain the NAS system as my primary storage source.
I will give it a try.
0 -
I have never tried storing the image files on a NAS drive and would imagine that it will come with a some major downsides (mounted drive offline, slow access, network problems).
My solution to this problem is to split my library into multiple SSD drives that are attached through USB C (Samsung T5 with 2TByte). I found C1 to be unacceptably slow on my laptop if a catalog exceeds approx. 30,000 images anyway. And those easily fit on one SSD drive.
0 -
So if I interpret what you say, if I locate the actual C1 cosessiondb files for each session on a SSD drive attached via USB to my computer, but store the image files I am working on on a NAS drive, then that should speed things up and prevent crashes?
Maybe. I don't use a NAS and can't say with any certainty that having images stored on the NAS won't slow you down. I do think moving your catalog file to an attached SSD drive will be better than storing it on the NAS. But I could be wrong and it may make no difference at all.
0 -
Ok, thanks Marco. I will report progress.
0 -
The one keyword that stood out to me in your original post was "wireless".
If you are trying to do I/O on a drive wirelessly, that likely is the FIRST problem I'd address.
Nothing wrong with external drives, I use them myself, but when working with image or video files, WIRED connections are your friend for speed.
Hitting the filesystem for I/O is usually the slow point of any workflow...and wireless just is not fast.
Ethernet is better than wireless...and even better are the thunderbolt and USB3 I believe, but I don't have the numbers on those in front of me.
Quite often it is optimum to have your applications working on your main drive, and have your images external on a wired connection that way you aren't running into I/O contention hitting the same drive constantly and better to spread the access needs over multiple devices.
Anyway, I ramble...haven't had morning caffeine yet....but in short, try to get off wireless.
0 -
I've been having very slow performance issues since the latest update (13.1.2.37). I'm using Capture One on a 2013 MacPro and a 2019 5K iMac. Never had the performance issues before.
0 -
Once again, thanks everyone for your comments. I have been using Cap 1 for many years now and find it to be the best raw converter around. I keep trying to do more post processing with it but despite my best efforts, its slow speed of operation makes Lightroom and Photoshop my ultimate software of choice for post processing. I was hoping that V20 might be better, but it is still too slow. I tried modifying my workflow and even purchased an SSD drive but to no avail. The problem is not the wireless network or NAS drive per se, as Lightroom works fine in this workflow environment. Waiting for the spinning wheel to stop after each instruction in Cap1 is not an effective use of time. So at the moment this very expensive program is being used just as a raw converter for preparing images for further work in Lightroom and Photoshop.
0
Post is closed for comments.
Comments
9 comments