Crashing upon opening, corrupt catalog database.
I just lost 6 hours of adjustment work on 90 photos because somehow the catalog database becomes corrupted at some point while I'm working. When I re-open COP7 with that catalog, it can't find the photos and crashes after about 3 seconds. I tried importing a backup from Time Machine but they too are corrupted until before I began the work.
I can open COP7 with another catalog and use the File > Verify Catalog which shows the corrupted catalog's database as verified, but when I open that catalog, COP7 crashes. That's it. I have to pull up an older backup of the catalog to get COP7 to open, but all that recent work is gone. I'm now going to miss my deadline after troubleshooting as there is no time to re-do all of that work.
Someone needs to get this stability stuff worked out or I'm going to have no choice but to switch back to Lightroom. This is the second time this has happened. Very annoyed.
System: MacBook Pro, OS 10.8.5
Program: Capture One Pro 7, Version 7.2
I can open COP7 with another catalog and use the File > Verify Catalog which shows the corrupted catalog's database as verified, but when I open that catalog, COP7 crashes. That's it. I have to pull up an older backup of the catalog to get COP7 to open, but all that recent work is gone. I'm now going to miss my deadline after troubleshooting as there is no time to re-do all of that work.
Someone needs to get this stability stuff worked out or I'm going to have no choice but to switch back to Lightroom. This is the second time this has happened. Very annoyed.
System: MacBook Pro, OS 10.8.5
Program: Capture One Pro 7, Version 7.2
0
-
I've had the same problem with corrupt catalogs not allowing CO7.2 to open. It has happened three times now. Not sure why. Once I had made LOTS of changes to settings and ratings and color labels to several hundred images in one sitting, and I closed CO at the end of the day, and I'm thinking CO did not have enough time to process through all of those changes, so it then got "confused" and unable to open.
The most recent time, I had deleted several hundred images from the catalog and closed CO, and again, I think I did not give it enough time to process those changes. However in both cases, there was no progress bar or rotating circle to let me know it was still processing anything. But my hunch is that it was.
In the first case I WAS actually able to open the corrupt catalog by doing this: Every time I tried to open CO, the CO screen would appear briefly and then disappear and CO would shutdown. So one time, I tried clicking on the CO screen when it appeared and held down the mouse button, just to see what would happen. Eventually, all of the images appeared and it seemed to be running fine. It worked!
But the last time it has crashed, I never even got the CO screen to appear at all, so I tried to open the backup catalog. Well THAT was nightmare because the default backup folder is buried/invisible in the Mac OS!!! I had to ask out studio tech expert where it was and he told me to use the terminal window utility and a specialized command to get it to show up in my finder. THAT seems poorly designed!!! 🤬 ).
So MY QUESTION: That backup catalog seems to have a more complicated structure with other settings and proxies folders, so I don't want to move it from it's hard to find Backup Folder location. How do I move that back-up catalog to a more user friendly location in the finder????0 -
Just to help answer your question, all you have to do is go to your root folder, click on "Go" in the menu bar and hold down the option key. The Library folder will appear in the list. Click on it and you're able to see the application Support > Capture One and then your backup catalogs.
I've been on with tech support for 4 days now trying to solve this matter with Capture One crashing when opening a particular catalog. Somehow COP7 is either corrupting the catalog database or some sort of link is being lost. I can open a backup of the catalog sometimes, but once I close it then reopen it, COP7 crashes again.0
Post is closed for comments.
Comments
2 comments