Catalog max number of photos?
What is the maximum recommended number of photos in a C1 catalog?
Currently I have multiple catalogs and at some point I was wondering if I should consolidate into a single one.
-
All depend upon your configuration (hardware and software). I know people who have a clean computer and are running catalogues up to 100k images. Others with a messy system have problems with 20k images.
0 -
353K here.
Images from 2003 to current (RAW files from Canon20D/5D/1Ds, Fujifilm XPro1-XPro3). Also Images taken from my iPhone 4 -iPhone 11
0 -
Rather than relying on the Capture One catalog, I've decided to:
- Wait until April to install C1-22 for the bugs to be squashed.
- Use my master catalog that covers 12,000 photos spanning 2010 - 2021.
- Use only sessions for now on.
- Cull with the 1, 2, 3 star system.
- Export the "best of the best of the best" jpegs with all meta data.
- Drag the jpegs into Apple Photo.
It is stunning what Apple Photos does in organizing and searching automatically. Memories, peoples, places, search (lighthouse, boats, skiing, dogs, sports, whatever...)
Plus, "add to photos" from messages expands the content.
Just amazing. Plus, since the iCloud is involved, the "best of the best of the best" are automatically backed up.
1 -
Thank you for the perspective and yes you are right, I need to explore more "sessions" feature, to be honest I came from LR, so I'm very used to get them in the catalog for then edit, but might be better paths.
Now that you mention the DAM is a good option, because one is edit photos to other is to administrate, tag, filter, face detect... etc etc... I'm using google photo for sharing with my family, but that lacks some features I'd love to have so I will look into DAMs. Thanks!
0 -
EtMRS,
Maybe you know, which of the DAMs / photo management apps are developed and maintained by more than one person? It might not matter for you, but it matters for me, as I don't want to rely on a software with a high risk of being discontinued (I know even if software is provided by a company this is not a guarantee that it will be maintained long-term, but chances are probably higher as you don't have the risk of a single person losing interest or having an accident).
I think Photo Mechanic Plus is a "real" company with several employees. Digikam is open source so there is a community of developers. iMatch and Photo Supreme are a one man show I believe.
0 -
Hi EtMRS,
Sure you can assess and take the risk. Still I am not convinced that PSU is more than one person, there is no indication on their website nor did I find any company information in the internet. But I remember an older forums post (in any other forum, maybe dpreview) that "the developer was very responsive" or something similar, and where others read "responsive" I read "the '(only)' developer".
Anyway, if the files are all accessible one can think about a migration any time later, should this concern ever become true.How do you deal with variants of the same raw file having different keywords in C1, e.g. one variant with keyword BW, another with "printed", another with "instagram" etc. Only the first variant in C1 can be synced to xml. Do you create a jpg for each variant to be imported into PSu and stack them with the raw file?
0 -
Thanks.
So, essetially you have a variant specific image file (tiff or jpg) with a variant specific image file name. This file can contain the keywords "photobook1" (the name of the photo book it is) and "printed", another derivative file can contain the keyword "flickr", but how do I know which C1 variant I have used to create this derivate, I would need to add the variant position into the file (and never change the variant position, eg. never delete a variant in C1 which is earlier in the row of variants), or I put derivative file name into the C1 variant keywords or other metadata. Holy moly, this sounds like a lot of manual work.
0 -
Thank you.
0 -
Hi EtMRS,
You can pass each variant metadata (stars, color tag, keywords, iptc fields) to a DAM by exporting a variant, naming the output file using the token "variant position".
This is a one way sync though. The xmp implementation of C1 does not allow to export or load any metadata for variants. In no direction.
The .cos file variant settings concept in sessions (or the equivalent variant settings in a catalog), is fundamentally different from the xmp implementation in two ways:
(1) each file with the same file name (in the same folder) uses the same xmp file, regardless its original settings, wich will eventually be overridden if you sync, and which of the files rules over the others is unclear to me
(2) variants metadata (except the first one in the sequence) just don't appear in any xmp file, and cannt be loaded either
Maybe if a variant specific name and a variant specific xmp file would do the trick, if that would be implemented in C1.
Or, for sessions, a transformation of the .cos files to real xmp files.
0 -
I Hace Ci 22, with a new Mac Book Por with 32 GB of RAM, I am trying to build a catalog with 75 K photos, we are at 65K and this thing is almost Stuck, and has taken the full day! LR did not have any issues with a smaller computer.....Should I be disappointed? feel cheated about the promises of C1?
0
Post is closed for comments.
Comments
10 comments