![]() ![]() For the sake of argument, let's say it's just safer to maintain catalogs with no more than 10,000 images. Just the idea that the software would put data at risk because of some arbitrary limitation is offensive to me. I will update here when/if I hear anything. I've submitted a support question about my original problem (still not resolved) and I submitted a separate question about this ridiculous 10K image limitation. I have now selected (in preferences) the option "Open Session or Catalog in a new window", which limits Capture One to one catalog or session at a time. The only time I've had problems with corrupted databases is when I force quit Capture One, or when I was running a Catalog and a Session at the same time. If the accumulated backups become too large, it's easy to erase a few (using finder) If a catalog database becomes corrupt, this lets you copy a previous non-corrupted version of the database back into the Catalog. One copy is kept permanently every time a backup occurrs. This makes a copy of the database, which is not that big. You can also chose to manually backup the Catalog from within Capture One at any time. ![]() In Capture One Preferences, I set the Automatic backup for once a day. That should have put me well within the range of useable backups.įor dealing with a corrupt Capture One database, IMO the Capture One backup feature is more effective than Time Machine, in any case it's useful to have both. I did say that I restored from a TM backup several months old. I am also on a MAC so I have a TimeMachine running so the longest I go without a backup is an hour. I have gotten in the habit of backing up after each big editing session. Since C1 stores so much data in its catalog files a backup is essential. Only thing I have done at that point is make a stiff drink and restore from a backup. Any clue what is going on or suggestions on how to proceed? I tried to verify and repair the catalog, but that doesn't do anything.įinally, when attempting to verify the catalog: I deleted the prefs files for Capture One (every file I could find, including for versions 8, 9, and 10 of Capture One). First from a few days ago and when I got the same error message, I restored from a backup that is several months old. I restored the database from a Time Machine backup. I have no idea what happened as I don't think I've had to Force Quit the app or Force Restart my Mac. ![]() This is an archive of images older than 3 years ago and contains A LOT of images. I was able to edit and print from that database. Three days ago, I was working with one of my databases with no problems. I've read through the other threads related to this issue, but none of the fixes I've tried have worked. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |