Maximum catalog size
I have used Capture One since version 8. I shoot raw with a Canon 5dsr that creates fairly large files. When I started with Capture one I found that it took a long time to open my very large files of over 20,000 images that were held own external hard drives. So I broke them up into multiple catalogs and that sped things up a great deal. CP20 seems to work faster for me. So I am thinking about combining my catalogs into one large catalog. I keep my raw files in my catalogs as I do not like reference files held in different places. I know that I have duplicate raw files, but it works for me. My question is - Will a large single catalog holding up to 2T images open in CP 20 in a reasonable amount of time. The Catalog will he stored on a G Technology Hard drive spinning at 7200 and connected via USB 3. I have a mid 2015 5K mac with a 3.3 Ghz Quad core processor and 32 GB of Ram.
-
If I understand correctly you have 2TB of image files, and you want to put all of these in one managed catalog. If the average is 20MB per file that is about 100,000 images.
Some people are unable to get reasonable performance with 100,000 referenced images, other are successful.
I have not heard of anyone who is successful with more than 200,000 referenced image files.I have not heard of anybody trying as many as 100,000 files inside the catalog.
One thing I am sure of - if you have a problem with such a catalog, it will be rather difficult to extract the image files from the catalog.
I personally wouldn’t consider it.
0 -
Thanks for your answer. I never really added up all of the images I have. My present total is around 60,000. I used the 2T size to include additional photo shoots. Your answer confirms what I thought. I will continue to use my present system. I only wish the was a way to easily transfer images from one catalog to another. I have a catalog for final images that I have completed all my post processing on, and I export them from their home catalog as originals with changes and then import them into the appropriate location in the final images catalog. A two step process that does not take a lot of time.
0 -
I have seen comments from number of people who were successful with 60,000 referenced images. My biggest catalog is 20,000 referenced images and it’s quite OK.
I think the expected way of working with Capture One is that the images from one shoot are handled in one session. Then the final good images may be imported into a Catalog or Master session. You’re kind of half there already.
0 -
I have never used sessions. I think I will continue to use my method. It seems to work for me. Thanks for your suggestions.
0 -
I only have few sessions, not sure I fully understand them. What I do know:
1) sessions are more mature (have been part of C1 longer) and have fewer issues than catalogs
2) it is easy to import a session into a catalog; it’s very difficult to move or copy images and edits from catalog to session
3) I have seen comments that is very easy to share images and edits between sessions. I haven’t tried it.0 -
One thing I am sure of - if you have a problem with such a catalog, it will be rather difficult to extract the image files from the catalog.
Images need not live in the catalog. I might go as far as saying they should not. You have many more storage options when they live elsewhere. Example: my catalog (about 50K images) is on my boot drive. My images live on a separate drive for media. The media drive is cloned once in a while in addition to being part of normal Mac time machine backups. My catalog is backup up in time machine AND every 7 days by Capture one.
If something should happen to my catalog I've time machine backups and the Capture One weekly backup. If something should happen to may boot drive my images are safely stored elsewhere.
There is nothing wrong with using sessions, but Catalogs make it very easy to search my entire image library on various pieces of metadata, something quite important to me as a non professional user.
Down side: it takes 40ish seconds to open my master catalog. I do hope Capture One addresses that issue someday.
1 -
Bob W. holds the raw files not only "within" the catalog but also outside ("duplicate raw files").
No raw file will be kept hostage. If you ever wondered what the empty "Originals" folder is for, in a "normal", managed catalog, this is the location for raw files of a catalog which holds the raw files "Inside catalog". That means they are not stored in the catalog database file itself, nor are the adjustments, they are stored in the file system fully accessible via Explorer (probably the same on Mac with Finder).
The problem I personally would have with a big catalog of this type is (1) the missing folder structure (sub folders) and (2) the inflexibility regarding where raw files can be stored e.g. if I wanted to store the older images somewhere else.
(Probably you can "simulate" a "Inside catalog" type of catalog by creating your desired folder structure beneath the folder "Originals" and copy raw files manually to this folder, then import them using "current location". Then my two "problems" would be solved.)
For the question regarding performance it should be irrelevant if using a referenced catalog or a selfcontained catalog, if my assumption that they are basically the same is correct, assuming the location is on the same disk.
Bob, I think the size on disk (e.g. 2T images) does not matter, it is rather the number of images, thumbnails, previews etc. which is the factor to determine the performance, as well as the disk and overall system speed.
regards
0 -
Last year I imported my Lightroom Catalog with 350,000 files from Lightroom to a Cap 12 Catalog. All images (6.5 TB) live on a 10TB G-Tech USB Drive in folders separated by year. It took 3 day to import from the Lightroom Cat. All Metadata (IPTC,keywoord,etc), White Balance, exp, etc and ALL of my collections. As expected Capture does take a performance hit and it's not DAM software. But no software is perfect.
1 -
@Brian Very useful datapoint. Can you mention any tips about migrating large catalogs?
0 -
So after all of your very useful tips, I have decided to do nothing. I had a very bad experience with referenced files many years ago with Aperture, so I do not want to store my original raw files in one location, even with the multiple backups I use. Disk space is cheap so I do not mind saving multiple copies of raw files. I find that I may rework files once I move them to my final images catalog, and I know the raw files in an early generation file they were originally downloaded to may be different, but I can live with that. Even if the combined catalog was not slowed down by its size, the though of moving all of my folders, key word and smart folders is to much work.
0 -
Hi all!
My experience with C1 (beginning with V8) catalogues were not overwhelming. They often broke at around 30k images or I lost connection of images and I was not happy building new catalogues. I currently use independent sessions with about 1000 images and here I am happy! At this size sessions are still acceptable in speed C1-20 opens a session and needs to do some housekeeping to show the thumbnails (slower on a NAS)
Sessions are nicely compatible to other software such as Luminar or ACDSee. The latter I use as asset manager and it can cope with the simple session structures of multiple sessions. Luminar can be simply guided to the output folder of a session for enhancing single images.
In parallel, I maintain an independent archive with all my sorted images by year/month in a redundant way. For this purpose I scrub over all my sessions to copy a copy into the pile. This is to have a failsafe image backup archive. I have not checked how fast it would be to wrap around a catalog for each year but this is planned.
0
投稿コメントは受け付けていません。
コメント
11件のコメント