C1P 8.1 catalog corrupt upon Crash
Yesterday during a culling proces of previously imported images C1P gave me the spinning ball of death,
and i had to force quit C1P.
Upon restart, C1P opened an older catalog, with none of my newer images present in the catalog.
Off course a bit startled about my missing images, i started to snoop around, and did a “show package contents"
on my only catalog file.
Inside the package, where 4 catalog files, including one named “….conflicting catalog….."
Since the catalog clearly had issues, i took the chance and deleted all the other catalog files inside “the package catalog"
apart from the catalog file name “…..conflicting catalog….†because the file size of this file, was bigger than the other
files. I then renamed the “….conflicting catalog…..†to "Capture One Catalog.cocatalogdb†and restarted C1P.
Voila - all my images was back again.
Now what worries me is off course consistency in my catalog, even upon crashes.
I am about to start the big migration exercise of all my lightroom and aperture images (30K+) into C1P.
So my question is this. Is there a catalog health check feature/function i can use, that i do not now of, because this
scares me a lot if it was to happen again.
Lightroom and Aperture also crashes from time to time, but i have never lost files before or have had to do this exercise
in these programs before, as they have a rebuild library function.
I am running C1P 8.1 on Maverick and Yosemite.
and i had to force quit C1P.
Upon restart, C1P opened an older catalog, with none of my newer images present in the catalog.
Off course a bit startled about my missing images, i started to snoop around, and did a “show package contents"
on my only catalog file.
Inside the package, where 4 catalog files, including one named “….conflicting catalog….."
Since the catalog clearly had issues, i took the chance and deleted all the other catalog files inside “the package catalog"
apart from the catalog file name “…..conflicting catalog….†because the file size of this file, was bigger than the other
files. I then renamed the “….conflicting catalog…..†to "Capture One Catalog.cocatalogdb†and restarted C1P.
Voila - all my images was back again.
Now what worries me is off course consistency in my catalog, even upon crashes.
I am about to start the big migration exercise of all my lightroom and aperture images (30K+) into C1P.
So my question is this. Is there a catalog health check feature/function i can use, that i do not now of, because this
scares me a lot if it was to happen again.
Lightroom and Aperture also crashes from time to time, but i have never lost files before or have had to do this exercise
in these programs before, as they have a rebuild library function.
I am running C1P 8.1 on Maverick and Yosemite.
0
-
You could run from File menu > Verify Catalog 0 -
Almost to easy 😉
Guess i still has a lot to learn regarding C1P.
Thank you for the quick reply.0
Post is closed for comments.
Comments
2 comments