Improved Library Cache Management

Current Issue:

By default, Capture One saves library cache files inside each library package. This poses significant challenges when using cloud services like iCloud, as cache folders can consume considerable space. Additionally, since cache files do not need to be backed up, storing them within the library package is inefficient. Capture One can regenerate these cache files from the master files if needed.

Proposed Solution:

I suggest modifying the default behavior for library cache file storage. Instead of saving cache files within the library, they could be stored in a hidden folder outside the library package. (for exemple in /Users/[username]/Library/Application Support/Capture One/Cache)

Implementation Suggestions:

1. New library creation, cache option:

   • Save library cache within library

   • Save library cache in Capture One default library cache folder

   • Save library cache in a custom path (with a button to select a path)

2. Capture One preferences:

   • Always save library cache within library (checkbox)

   • Change the default library cache folder (with a button to select a path)

This change would improve storage efficiency and provide users with more flexibility in managing their cache files.

This would also facilitate easier sharing of libraries between devices, including desktop, iOS, and iPad.