Capture One Pro keeps freezing and have to restart mac
Running Capture One Pro on:
- MacBook Pro (15-inch, 2019)
-
2,6 GHz 6-Core Intel Core i7
-
32 GB 2400 MHz DDR4
- OS: macOS Big Sur, however it happened time a time on previous version of macOS as well
Working on my photos as usual and suddenly C1 freezes. I let it running for a long time, tried half an hour. Never unfreeze again.
So, i force quit it. However, it cannot be opened, it will just not start. I have to restart my mac to be able start it again.
How to solve it?
-
As i wrote. It's not connected to BigSur. It happened before as well. No one experience such a behavior?
0 -
I've noticed one more thing. It happens when C1 tries to work with photos stored in NAS over the network.
I understand that it might have some connectivity issues but it shouldn't freeze and be non-responsive.
0 -
I see your point. However, this should be handled by Capture One gracefully. I would understand if some error message come back saying 'connection issue' but it freezes. That's not acceptable, this is suppose to be professional SW.
0 -
I would guess that the NAS has indicated that it has received the request - so C1 has no reason to abandon the command and advise it cannot do as requested.
That I can simply navigate to the NAS and click on it, hear it come to full disk spinning life and then see C1 respond seems to suggest that is probably what is happening.
However, I'm using Windows so the sequence of events as well as the outcome may be different for the Mac/NAS interface and which NAS you have along with which drives are installed and which software running within it may all be influential. In my case no doubt the use of WiFi has some influence too.
0 -
i´m sure c1 support has a long list of reported issues related to the use of external drives, this problems started with co20 but they decided to do nothing as usual. try to remove all c1 support and cache files and hope they solve this problem with co21.
0 -
Interestingly my system seems to have improved its wakeup consistency as well as response speed since I changed the WiFi range extender into which the the cable from the NAS is plugged.
The old range extender had started to go AWOL all by itself - but the only way I could confirm that diagnosis was to replace it.
A pity since the old was was not in-expensive and not really very old.
0 -
hm... great that you windows problems are solved SFA ... but wait what does this say about mac issues ?
0 -
Does the freeze always happen when you try to edit a particular image? If so, the image file may be corrupt and could cause the crash.
I had this problem once and it drove me crazy. I'd be working and suddenly C1 would crash without warning. I narrowed the problem down to a file, replaced the file from a backup and all's well.
Another time I had the problem you're experiencing and regenerating previews solved the problem. First, though, I'd look at either your NAS or for a corrupt file.
0 -
@CSP
Well, since the Mac issues are not necessarily unique as I experience something that sounds very similar with Windows ...
... perhaps they are not exclusively Mac or C1 problems?
0 -
yes maybe, but I very much doubt it. since co20 I see a lot of crashes when c1 tries to access my raid drive connected over usb 3, nothing else I use shows this problems. as a consequence i stopped using c1 except for tethered shooting. this software has rotten code, seems they have not the greatest people working on the mac side or they simply don't care, both is unacceptable.
0 -
Can you prove any of that?
0 -
prove what, that c1 has major issues ? i already moved to big sur so I can't show you the c1 crash reports from this years but maybe you get yourself a mac then edit thousands of files and find out for yourself what's wrong.
0 -
Why would I want a Mac?
Are you suggesting that ALL Mac users of C1 have the same problems?
0 -
I have the same issue, running MacOS Mojave, after updating C1 issue started. Using external SSD's and the first thing that happened was that booth my external drives where ejected without any input from me. After that my Mac froze and had to restart after the restart it took a very long time to get ANY programs back up and running. Definitely C1 issue in my books. Just to clarify , I have not updated anything else then C1 to 20Pro initially and last to build 13.1.3.9.
0 -
In the very rare instances that an app freezes, I'll try to force quit
it before I restart my Mac — also running OS Mojave.0 -
I'm running the latest version of Windows 10 (Build 19041.630), using the latest version of Capture One 13.1.3.13 and I immediately started having issues with my WHOLE catalog as soon as I updated to "this" latest version (Capture One).
-32 GB Ram-Intel Core i7-9800X CPU @ 4.00 GHz
-Catalog on Internal SSD
The same constant "hanging" issue and having to restart the computer, run diagnostic on the Catalog, force quit, create a new Catalog, and then rinse and repeat all again.0 -
I don't work with catalogues and I don't know much
about windows so I can't be of significant help!0 -
I am running macOS 10.13.6 on a sufficient MacbookPro and have this issue this as well. The computer auto-restarts after a short freeze causing a loss in my latest image adjustments.
0 -
2 suggestions.
Try re-installing.
or
Wait for the release that supports "Big Sur" and see what happens then.
-1 -
My comments still stand unless you have already tried the re-installation route.
Right now you are running an unsupported OS. Hopefully that situation will not last long.
If your NAS has a habit of putting the discs into hibernation (like mine does) they may not always "wake up" on a remote demand for action. Or at least that is what I sometime see with mine running Windows. The same can be true, I suspect, if the NAS is performing some types of internal administration or indexing in certain circumstances.
Usually the "long pause" will eventually free up but I find that using the system to to activate the NAS - for example browse to it using Windows explorer - will wake it up successfully and C1 will continue.
It should be mentioned that I access the NAS via WiFi.
I have no idea whether this is a NAS manufacturer specific problem.
There are times when the NAS wakes up just as one would expect it to as a result of C1 activity and no secondary action is required. There may be a way to monitor and assess why this happens but I don't have the experience or inclination to research the problem specifically since it does not cause me enough of a problem to justify the effort and I have an easy way (at least for now) to overcome the non-responsiveness.
I hope these observations may help your investigations in some way.
-1
Post is closed for comments.
Comments
20 comments