How much improved is the improved catalog speed? Did C1 became a real DAM?
I have rather large catalogues with 100.000+ RAW photographs on a Windows machine. About two or three years ago I tested the cataloging functions of C1 which was a disaster. In fact, the catalog of C1 was not (entirely ?) based on a database. For example, when I said "Show me all photographs in the collection X with the keyword Y and rating Z" C1 seemed to search for these stuff "manually" in all files instead of looking it up in a database. This resulted in unbearable long search processes. Also the support honestly confirmed this behaviour.
At this point, C1 was not useful as a DAM for large catalogs. And they missed to properly make use of the Media Pro software which they purchased before. I switched to Daminion for cataloging images which is superfast and shows all searches instantly. The only problem with Daminion is that it doesn't reflect the editings or variants done/created in C1, which is a pain. So, I still dream of C1 becoming a real DAM which makes use of a database.
As I said, it's two or three years ago I did this tests (as it's a huge amount of work). Maybe it was CaptureOne version 9, but I'm not sure. Now, they state, that with C1 22 the speed on Windows machines increased a lot (I'm using Windows too).
Are you working with large catalogs? And do you know if they modified it towards a real DAM? Or does it still behave like described above?
Many thanks for your insights!
Lorenz
-
If you're asking in relation to the v16.5.2 catalog improvements, in the release notes, it says this:
Optimized autosave improves Сatalog responsiveness and reduces hanging for large or complex Сatalogs.
Which doesn't sound like any sort of a major overhaul. It sounds more like they fixed some glitches/bugs. I'm not aware of any other recent effort to improve the catalog feature.
So, I still dream of C1 becoming a real DAM which makes use of a database.
To be perfectly honest, Capture One's focus (based on the kinds of features they have and have not been working on over the last two years) appears to be mostly aimed at professional studio and event photographers and perhaps photo techs, nearly all of which work with sessions not catalogs because these pros are largely job-based which lends itself better to using sessions since a given job is neatly packaged into a session where it can be independently moved, archived, sent, passed to a tech, shared, deleted, backed up, etc...
If you haven't already, then I'd suggesting voting for these catalog feature improvements:
Would love to see file/DAM performance improvements prioritized
Improve Catalog Performance (Metadata Load)
Or write your own feature request that is specific about what improvements you want to see.
1
Post is closed for comments.
Comments
1 comment