Restoring adjustments

Spicyjello

• 2017年04月12日 18:17

Hello,

I have recently had C1 crash and failed to launch. Got an error that the database was invalid. I had 3 backups. The newest backup would not restore but a backup a week earlier restored fine. Restoring an earlier backup ment I lost the adjustments on several images. I see in the backup folders that there is a adjustment folder included. Is it possible to manually restore settings saved in the newer backup?

Thanks for the guidance!


Troy

0

• 

  Paul Steunebrink

  • 2017年04月12日 18:48

  Hi Troy,
  
  The Adjustments folder in the Catalog folder contains adjustments that can not be stored in the database, like file-related adjustments (ICC profile, local adjustments mask).
  
  So the answer to your question is no. You can not manually restore adjustments from another source then from a backup database that you restore manually.
  
  As you might figured out, doing a daily database backup is paramount. You can set a reminder in the Preferences.

  0
• 

  Spicyjello

  • 2017年04月12日 23:09

  Thanks for the reply.
  
  C1 crashed after a long editing session while shutting down and backing up.
  
  Im really concerned about this being an issue in the future. With LR I used sidecars files and that way all settings were written one file at a time. If there was a crash I might lose that last image edited but thats it.
  
  How common is it for C1 to crash?
  
  
  Thanks again!
  
  Troy

  0
• 

  Permanently deleted user

  • 2017年04月13日 08:03

  Hi Troy,
  
  I've never had any crash with Capture One. I am working in the catalogue mode, and I backup my catalogue every time I think that my work is important enough not to loose it.
  In your case, perhaps it could be better to work in the session mode, where all the adjustments are saved in real time in a subfolder of the "sidecar" type.

  0
• 

  paintbox

  • 2017年04月13日 09:24

  John, I too have found working in sessions better. Then when finished, just migrate your photos to an aptly named user collection in your catalog.
  You will also find that the collections seem to be better behaved as well.
  
  One thing to remember, if C1 starts beachballing, just relax and walk away. A lot of times it will "find itself" and you can continue.
  I used to think it was hopeless and just force quit. Now, i'll just check the weather, Facebook or whatever. Things always seem to work out.

  0
• 

  Eric Nepean

  • 2017年04月13日 16:07

  When Capture One starts beach balling, about the worst thing you can do is a force quit, that often results in damaage to the database.
  
  I don't think I've ever experienced a crash of a released version of Capture One Pro.
  
  However I have seen many hangs with beachballing, and during the import of a large ctalog or library I have seen a beach ball hang may last up to an hour. Otherwise usually less than 2 minutes. I think this will improve in upcoming versions.
  
  I observe that when beachballing occurs, COP has typically started to use more than the equivalent of 1 CPU. Typically COP CPU usage maxes out at about 2 CPU equivalents. I kind of wish it would use even more, quite often I see alot of unused CPU capacity on my I7 when COP has maxed out at 2 CPU core equivalents.
  
  When I get a beachball that is more than 10 seconds or so, I bring up the activity monitor and check the memory usage. As long as the memory pressure stays in the green or yellow zone , I know COP is going to be OK, just be patient. In a very few cases (certain Applescript commands), I have seen COPs allocated memory climb and climb and climb, and when the memory swap file size gets over 10GB I know COP is in trouble and likely not recoverable.

  0

投稿コメントは受け付けていません。