Capture One v10 crashes often and is slow....
I think, I experience a lot issues, which are discussed in this forum.
It is nearly impossible to work with CO v10.
I'm using the newest iMac 32 GB Ram and an external harddrive with the catalog and an external folder with all my images (about 60.000 on the same harddrive).
In some cases CO opens the catalog in about 30 sec, in other cases it takes some minutes (it seems the software scans all images, because the harddrive works all the time extensively).
When it is possible to load the database, I can use CO (more or less), as far as I work within a project. But for instance when I try to work with all images (f.e. filtering), the coloured ball starts spinning. CO doesn't react any longer. It seems to me, that CO tries to "read" or to scan all images again (the hard disk is used extensively), after some minutes all processes die and you have end CO by the system. Then the database is corrupted and unusable.
Then I have to repair the database-package:
Sometimes I have to delete the journal file within the database-package. In this cases the database itself is ok. In other cases I have to use a backup of my database, too.
Thomas
It is nearly impossible to work with CO v10.
I'm using the newest iMac 32 GB Ram and an external harddrive with the catalog and an external folder with all my images (about 60.000 on the same harddrive).
In some cases CO opens the catalog in about 30 sec, in other cases it takes some minutes (it seems the software scans all images, because the harddrive works all the time extensively).
When it is possible to load the database, I can use CO (more or less), as far as I work within a project. But for instance when I try to work with all images (f.e. filtering), the coloured ball starts spinning. CO doesn't react any longer. It seems to me, that CO tries to "read" or to scan all images again (the hard disk is used extensively), after some minutes all processes die and you have end CO by the system. Then the database is corrupted and unusable.
Then I have to repair the database-package:
Sometimes I have to delete the journal file within the database-package. In this cases the database itself is ok. In other cases I have to use a backup of my database, too.
Thomas
0
-
Granmon,
unfortunately there is currently no real work around. It helps to split catalogs. 25.000 is the maximum on my (slower) machine. Avoid "all images" at all and do not leave it activated when closing as it takes ages and next opening is worse.
See details in
viewtopic.php?f=68&t=25212
Best
Frank0 -
Hello,
I am having the same problem but my catalogs are not nearly that big. It is becoming troublesome to continually have to restart CO10 to the point I just stop working. I do report it every time.
My set up is MacPro 2013 with Sierra using a Thunderbolt 4tb drive for image storage so processing & transfer speeds should be a non issue. I recently created a new catalog importing my old Lightroom and that one doesn't even want to open at all and causes lock ups. I think I have only had it successfully open once but while scrolling through it locked up.
I am hoping for a patch very soon because I do love CO and would like to have a a solid replacement for Lightroom.
Thank you!
Lisa Rose ATL0 -
Hi
Same problems here, especially when it tries to render a .tif file edited in Photoshop. It will just sit there spinning forever and when I finally quite COP10, it dies with an error report. I'm turning off OpenCL HW processing to see if this helps. I would have thought Phase One would have a fix out for this by now.
Scott0 -
Something I have noticed with the performance issue.....
I have roughly 45,000 images in a single catalogue and as has been described in many posts the performance can be woeful, especially when first opening the catalogue where it can take several minutes. My files are all referenced on an external USB3 connected 2TB HDD and my catalogue is on the MacBook Pro's internal 1TB SSD.
However....if I leave C1 v10 sitting on a single folder with only a few dozen or few hundred images at most in it when i shutdown....the next time I open C1, it opens really quickly (relatively.....within say 20-30 seconds), whereas if I am sitting on "All Images" or an album with many many images in it, it takes forever (can be more than 3-5 mins sometimes....btw ....i have found that being impatient and cancelling/force quiting that very long open seems to be the root of quite a few problems re corruption). Now once it opens, you will still get the performance lag the moment you switch to "All Images" , as others have said, as if its doing something to read in a lot of data.
Hence my workaround is avoid "All Images" or albums/folders etc with many thousands of images and at least I can get up and working relatively quickly. Likewise I only switch to All Images if I really need to.
Just my experience..0 -
The new update (10.01) has the same behaviour .... no solution.
the only way is - as mentioned earlier -
- avoiding "all images" and/or
- using smaller catalogues
until there is a working update...
Thomas0 -
until there is a working update...
I think it will come with CO 11 or 12. 🤬0 -
compared to Apple Aperture, a software that's many years old, the performance is ridiculous not to say not acceptable - we all should get our money back. 0 -
Don't forget : If, like me, you have some problems when you're browsing large catalog (spinning balls…) , contact support.
The only way to hope a quickly fix is to have more and more cases reported about this issues.0 -
Filed several support cases. Unfortunately feedback from support is not very promising yet
Frank0
Post is closed for comments.
Comments
9 comments