Crashes and spinning beachballs constantly
C1 Pro (v.8.3) is the buggiest software I've experienced for many years. Like many new users I'm in the process of switching from Aperture. I have my smallish catalogue (13k images) stored on a Drobo via Firewire while the application is running on an SSD in an iMac with 16GB Ram and decent amount of disk space available. I experience frequent delays while the beach ball spins, and just as many crashes. The crashes can happen randomly - while importing images, doing a round-trip from Photoshop CS6, or sometimes for no reason at all, when the software is running in the background. I have the subscription version in case that makes a difference. I send an error report after each crash. I'm sick and tired of the constant crashes with this software, especially as stability is one of its marketing features. Is this a common situation?
0
-
[quote="NN635480313308136073UL" wrote:
I send an error report after each crash. I'm sick and tired of the constant crashes with this software, especially as stability is one of its marketing features. Is this a common situation?
The standard error reports are useful for general analysis but are not personal problem reports from you to Technical Support.
To get the personal service create a Support Case so that the Support Team can help you work through any likely known problems with your total Hardware/OS/Applications package and seek a solution.
HTH.
Grant0 -
This may or may not help but it's worth a try:
In the first tab, the one that looks like a little folder. There is a tool called "Filters"
To the right of "filters" is three little dots.
Click on those dots.
Click "Remove Tool"
In my experience, the filter tool causes spinning beachballs and eventual crashes. So I removed it.
Let me know if it helps.0 -
[quote="NN635480313308136073UL" wrote:
C1 Pro (v.8.3) is the buggiest software I've experienced for many years. Like many new users I'm in the process of switching from Aperture. I have my smallish catalogue (13k images) stored on a Drobo via Firewire while the application is running on an SSD in an iMac with 16GB Ram and decent amount of disk space available. I experience frequent delays while the beach ball spins, and just as many crashes. The crashes can happen randomly - while importing images, doing a round-trip from Photoshop CS6, or sometimes for no reason at all, when the software is running in the background. I have the subscription version in case that makes a difference. I send an error report after each crash. I'm sick and tired of the constant crashes with this software, especially as stability is one of its marketing features. Is this a common situation?
Do raise a support case to have support look at your individual situation (as suggested above).
In the mean time, for other users to help you (at least have a better shot at it), could you please share more details. Which OSX, sessions or catalogs, where is the session/catalog placed: drobo or ssd? What does decent amount of diskspace mean, how much free of how much total?0 -
Thanks for the comments. I wasn't expecting personal technical support after sending the error logs, but just mentioning the fact that I send them for the sake of completeness. The catalogue is stored on the Drobo (connected via Firewire) and C1 is installed on the iMac's SSD (which is the start-up disk). The 250GB SSD has 209GB of available space. The iMac is a mid 2011 27" 3.4GHz i7 with 16GB of RAM running OS 10.10.3 (the latest). So all-in-all, the machine should have enough grunt to cope with C1. The C1 catalogue is 359GB and contains about 13,000 images.
I did import my very large Aperture library into C1, but it caused it to run at snail's pace, so I deleted the Aperture images (which took several days to accomplish). Could there be some remnants from the Aperture library still left hidden in the C1 catalogue? The C1 catalogue verifies without problems.
The crashes seem to occur at random, and as I said, they sometimes even happen when C1 is idle in the background. The comment about the filter tool causing issues is interesting. I'll remove that and see if it improves the situation.
Thanks all.0 -
First aid, move your catalog file (folder actually) to your internal drive. I assume (hope) you have your images referenced, so they stay on the Drobo. Over 50% chance that all is working much faster. 0 -
Revert back to the previous version!
Whenever I install Capture One I alway rename the previous version. Like Capture One 8.2.2 then he new version is named 8.3 not just Capture One which over writes the pervious version.
Then after a month or so of reading about bugs and work arounds. I'll consider upgrading if I need to
when I job comes through that I need the new software for the new camera that my client rents.
Capture 8 is still laggy when using multiple local corrections on even the fastest MacPro (bug).
Brian0
Post ist für Kommentare geschlossen.
Kommentare
6 Kommentare