Improved DAM: Capture One's database/catalogue needs an update
A subject that is brought up regularly, one of Capture One's weakest spots: its database/handling of catalogues. (See this and this, for instance.)
Perhaps it would be a good idea to summarize in once place the issues users experience with Capture One in this area.
1) Unresponsiveness/sluggishness, e.g. when searching/filtering and when editing metadata/keywords. (See this and this.)
2) Better performance with large catalogues.
3) Keywords:
- search for specific keywords – e.g. "cat", without also including keywords that contain the letters "cat" such as "cathedral" and "caterpillar" (see this below and this)
- suggested keywords
- hierarchical keywords
- sorting
- option to exclude specific keywords on export
4) Option to name variants (so that they can be distinguished in the browser).
5) Configurable metadata tags (see item 1 here).
6) Synchronization of metadata and adjustments between catalogue and sidecar files (.cos and .comask) (see this post).
7) Option to add/edit GPS metadata (see this).
8) Option to add notes to photos (see this and this).
9) Patterned search (see item 5 here).
10) Option to lock edits (see this).
11) Show offline/missing files.
12) Show stored file paths for offline/missing image files (see this).
NB: If other users have something to add to this, please leave comments, and I'll add further issues/information to this post.
-
The issue is actually not with loading itself, at least not loading of images; I haven't really had any trouble with that. It's basically about Capture One becoming unresponsive when searching/filtering and editing metadata. In my experience (from testing), Capture One behaves the same when all image files are offline and previews and thumbnails have been deleted from the catalogue, i.e. when there are no images to load.
Currently, it seems unlikely that Capture One will give any priority to improving this part of the application. Perhaps it's more likely that they will improve integration with other applications, but this would, as far as I understand, also require some fundamental changes to the same part of the application in order to allow synchronization of metadata not just for primary variants but for all variants. Otherwise I assume that external DAMs would have to read and edit Capture One catalogues directly, which is perhaps also possible.
If, eventually, Peakto manages to handle all of this – synchronization for all variants, editing metadata, etc. – that would be a partial solution. Though there's still no access to preview files, only to tiny thumbnails.
0
Post is closed for comments.
Comments
31 comments