How to rebuild a Capture One catalog? Help, please!
One of my USB hard drives with a small managed catalog crashed. ☹️ I am fortunate to have recovered the catalog using a program called Disk Warrior. 😊 However, the catalog is no longer one unified file. I have a series of folders called "Missing Folder [x]", where x is a number between 2 and 9. Drilling down into these directories I can see :
... my DNG files
... COP files
... COF files
... COMASK files
... files with no extension
The catalog was just getting started. I didn't even have time to back it up. It only had 1300 images and I can see all of them inside the subdirectories.
Is there a way to rebuild this catalog with all the separate files? I would be shocked if its not possible.
Please help!
Thanks!
... my DNG files
... COP files
... COF files
... COMASK files
... files with no extension
The catalog was just getting started. I didn't even have time to back it up. It only had 1300 images and I can see all of them inside the subdirectories.
Is there a way to rebuild this catalog with all the separate files? I would be shocked if its not possible.
Please help!
Thanks!
0
-
I created a new catalog and imported all of my images into it. Inside the catalog is usually a directory called :
Adjustments -> LAM -> [Year] -> [Month] ->[Day] -> [x]
where x is just a sequential number indicating the number of total imports into the catalog.
That directory contains a bunch of *.comask files. I thought I could copy those files into the new catalog package but C1 doesn't recognize them. Then I thought I need to make a dummy layer, like a gradient for example, so C1 would think a mask exists at all. Then it would look into the individual files to see what they are. That didn't work.
I think there is a database file that indexes these *.comask files and that database file would tell C1 to look for the masks.
Any ideas on how to recreate the database file?0 -
I'm afraid I can't help you as I haven't had the same thing happen to me but would suggest you open a support case. Support usually reacts pretty quickly. 0 -
The CO catalog never is one unified file. It is what is called a package- meaning that OSX shows it as one file, but it’s really gust hiding that it’s a folder, not a file, and contains folders and files inside. These you can see using Terminal directly, or with finder by selecting the “file†and then right click, show package contents.
If you look at a CO backup of a catalog with referenced images, it is pretty much just the database, and masks. All else can be recreated.
So, finding the database file is critical. It’s an sql database file probably between 50k and 100k in size.
Probably best if you start by opening a ticket.
fwiw I have my auto backup set to once a day (if the catalog has been used).
I’ve always distrusted managed catalogs. You have just reminded me why 😐0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare