Capture One Catalog Database Stability/Repair

NN635312785285747094UL

• June 27, 2014 20:13

With the death of Aperture I now have to find a replacement DAM.
Reading the forums here there seems to be quite a few posts related to Capture One Catalog Problems.

I know with both Aperture and Lightroom adjustments are not only saved into the database they are also saved in accompanying settings files that can be used to repair recreated the database in the event of corruption failure.

Does Capture One have a similar setup ? Is there a way to recover from Catalog File corruption deletion ?

0

• 

  RobiWan

  • June 28, 2014 15:10

  [quote="NN635312785285747094UL" wrote:
  
  I know with both Aperture and Lightroom adjustments are not only saved into the database they are also saved in accompanying settings files that can be used to repair recreated the database in the event of corruption failure.
  

  
  
  This is not correct. Aperture/ Lightroom are using the same Database Engine (SQLite) and not any extra Files. SQLite is SQL database with transactions-loging.
  
  I'm not a "super-power-user" but I never had any problems with C1 database/ catalog.

  0
• 

  Mark Connell

  • June 29, 2014 06:11

  [quote="RobiWan" wrote:
  
  This is not correct. Aperture/ Lightroom are using the same Database Engine (SQLite) and not any extra Files.

  
  
  Lightroom allows you to store all your develop settings within the sidecar XMP file used for IPTC metadata. So, if you corrupt the Catalog (DB) then re-importing your RAW files with XMP sidecars will restore your processed images.

  0
• 

  RobiWan

  • June 29, 2014 19:20

  [quote="msbc" wrote:
  

  [quote="RobiWan" wrote:
  
  This is not correct. Aperture/ Lightroom are using the same Database Engine (SQLite) and not any extra Files.

  
  
  Lightroom allows you to store all your develop settings within the sidecar XMP file used for IPTC metadata. So, if you corrupt the Catalog (DB) then re-importing your RAW files with XMP sidecars will restore your processed images.

  
  
  This is of course true, but in my opinion not practical because the speed greatly suffers under it.

  0
• 

  sizzlingbadger

  • June 30, 2014 05:14

  You can batch write the xml data manually in LR so no issues with performance.
  
  I started out on Aperture and then moved to LR. I also use CO a bit but have found the catalog to be unreliable. I have just started to use Fuji X-trans cameras and their raw files don't look that great in LR. They aren't too bad in Aperture but they seem to be best in CO. I have tried other convertors too, Iridient, DXO, Lightzone etc... but was not happy with any of them.
  
  I will probably keep my older non x-trans files in LR and just use CO for my Fuji's. This will keep the catalog size down. CO doesn't play nice with my older dng files either.

  0

Post is closed for comments.