Catalog file not opening in Capture One
I tried opening my catalog file and it gave me an error message. When I tried to verify and check the file, its telling me it cant find the database. Im on a job right now and I NEED this cat file to open!
0
-
[quote="scharadlightbourne" wrote:
I tried opening my catalog file and it gave me an error message. When I tried to verify and check the file, its telling me it cant find the database. Im on a job right now and I NEED this cat file to open!
If the database is gone, the catalog is gone - that is where the catalog information actually resides.
If the database is corrupt, there is no easy recovery. You can retreive your images, but not the organisation, metadata or the editting. PhaseOne may be able to do something, but it's no easy task. I don't know if they offer such a service.
You should open a support ticket ASAP.
I see two simple choices
1) Recover from your backups.- On the first page of COP preferences, at the bottom, the backup location is identified. In the backup location, you will find folders with date and time, in each one you will find a database file.
- Open another finder window, select the catalog file, right click, select "show package contents", finder will open inside the catalog. You will likely see the old database file, which is probably corrupt. Delete it.
- Copy the database file from the backup folder INTO the catalog file. Now try and open the catalog with COP.
- If that doesn't work, try an older backup.
2)Abandon the catalog, but retreive the images- If your catalog has only referenced images, no special action is needed. The images are in your OSX folder structure. Start a new catalog or session with the images.
- If your catalog has managed images, open finder inside the catalog (see above) and find the folders with the managed images. (Do a search for all RAWs or all JPGs). Copy them to folders outside the catalog
Catalogs I care about, I backup after every use. The backups are small since it is only the database.0
Post is closed for comments.
Comments
1 comment