Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

How to stop Capture One from regenerating previews and thumbnails

Comments

2 comments

  • Ian Wilson
    Moderator
    Top Commenter

    If you right click the catalog file in Finder, and choose Show Package Contents you will see that it contains several elements in the package. See screenshot:

     

    The database contains the adjustments you have made to the images, but not the previews. They are separately stored in a subfolder as shown. If you replaced the database, it would make no difference to the previews, if there was a problem with them. Probably best to let it regenerate them and put up with it.

    Ian

    0
  • Jerry C

    Ian, I am familiar with the contents of the package. Years ago, I found that you could replace just the database with a backup of the database in the catalog package if the database had been corrupted. It did not need to regenerate the previews and thumbnails. I wrote about this, a few years ago.

    If you open the database directly from a backup, it will reconstruct the cache and import its adjustments from the backup. The database point to these, but the full resolution previews and thumbnails are not, which is why it regenerates the previews and thumbnails. It looks like Capture One does this when you ask it to recover a catalog rather than just replacing the corrupted database in the package with a backup. Perhaps the folks writing the software presume that if the database was corrupted, the cache might also have been corrupted. However, the only thing that is prone to corruption is the database file. The cache contains individual files and the corruption of one of these would only corrupt one preview or thumbnail. This is what makes Capture One so much more stable than an application that stores all of its data in a monolithic database.

    What Capture One does to recover from a corrupted database (regenerating previews and thumbnails) exceeds what is needed almost all of the time. What I am suggesting is that you should not have to regenerate things that do not need regeneration.

    Nevertheless, you are right. Just letting Capture One do its thing to recover a catalog, is pretty easy and largely foolproof.The disk churning for hours while preview and thumbnails are regenerated does slow Capture One down somewhat, but it is largely in the background and if you leave it on overnight, it will be done, unless your computer freezes up partway through. 

    0

Post is closed for comments.