Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Max catalog size an issue moving from LR6 to C1

Comments

8 comments

  • cdc
    My opinion is that Lightroom is better for very large catalogs and Capture One is better for individual jobs (sessions) & tethered shooting. For me this translates to professional work being primarily done with Capture One, each job has its own session. And my personal work, a catalog sprawled across several hard drives spanning back a decade or so, is managed in a very large Lightroom catalog. Each program has its strong points so there is some cross over from time to time.

    Truth be told though I haven't spent much time with catalogs in Capture One but from most things I've read it doesn't look to promising if you want 420k images in one catalog.
    0
  • Eric Valk
    This would be a good question to send to Capture One support.

    I think the answer will depend in part on the capability of your Mac - processor speed, number of cores, ram, videocard.

    I have a late 2015 iMac with 4GHz i7, 24GB of RAM. My images and catalogs are stored on an external SSD drive.
    (I had a much more difficult time with my late 2009 iMac with 2.7GHz i5)

    I start to see some slow down above 10k images. Currently I am funding CO 11 useable at 16K images, I've spoken to others who have 35K images and 100k images and are OK with the performance.

    I find that the Filter tool can really slow things down if most images contain some unique value in one of the IPTC metadata fields, like the original file name, and there are more than 10K images in the current folder. I have moved the filter tool to it's own tool tab, so that most of the time it is not active.

    The CO search tool however works quite well with large numbers of images.

    I think that one difference is that CO user base has quite a number of professionals that will setup a separate session or catalog for each job, and from this they will identify a small percentage of the images which are the best. Then they may have one catalog for all of their best images, but this doesn't contain the images which didn't make the cut.
    0
  • RobbieAB
    and there are more than 10K images in the current folder.


    That sounds suspiciously like an OS level problem, as that number comes up a lot in issues with "My filesystem is slow".
    0
  • Eric Valk
    [quote="RobbieAB" wrote:
    and there are more than 10K images in the current folder.


    That sounds suspiciously like an OS level problem, as that number comes up a lot in issues with "My filesystem is slow".

    Hi Robbie
    Can you add more detail to your reference to issues with "My filesystem is slow"

    Do you mean just Capture One problems or problems with other apps? Within the CO forums, or elsewhere?

    I don't think I have a slow filesystem problem, my other applications work pretty fast. But always worth checking into I guess.

    One curious thing I have noticed about Capture One is that if one opens the log files inside COlog.zip, the package generated by Capture One for their support team, inside the com.phaseone.captureoneXX.log (where XX may be 9, 10 or 11) you will always find this line: Limit number of open files set to: 10000

    By the way, what kind of performance do you get from you largest catalog, and how many images in it?
    0
  • Philip Ryan
    I'm running a 2014 iMac 27" Retina with 32GB RAM. I've got it running Mohave (yes, I know it's not yet supported by C1) with Capture One 11.3 Build 11.3.0.26. My catalog has 59540 images. It takes about 35 seconds to open. Once open, depending on the collection size, I find it quite responsive with it being slowest at opening "All Images" at around 6 seconds. Most of my collections are 2000-4000 images. I'm not seeing any performance issues, although when I have multiple layers and a lot of edits on a particular image going there's a noticeable but not unreasonable slowdown working that image. I use referenced catalogs with the Master catalog being on the iMac fusion drive (SSD performance) and the images being on a 4 TB USB 3 disk.

    With High Sierra initial opening was slower, but once open performance was fine. When traveling I use a 2016 15" MacBook Pro with 16 GB RAM and normally create a catalog on it which is later imported into my Master catalog. Opening the Master catalog from a G- Drive USB C SSD takes 53 seconds with High Sierra 10.13.6. Again, once open performance is fine though I seldom work in the full catalog from the laptop.
    0
  • Eric Valk
    Further to my previous posts, my system is also a 27†iMac. I have two external SSDs connected via USB3.1, one SSD holds the Catalogs, the other holds all the image files. The catalogs hold only referenced images.

    I don’t mind the time to open the main catalog, as I do this only once or twice a day. My main concern is 1) time to respond to a key stroke or mouse click (which can be very slow with Filter tool active in All Images) 2) the time taken to search for variants in All Images. As well, some AppleScript commands (like select)take minutes longer to execute when the catalog size is large.
    0
  • Nancy Goodenough
    I appreciate the responses. You all let me know that C1's DAM is inappropriate for my use. If I could have Photo Mechanic as a front end in some way, that would be of interest.
    0
  • Eric Valk
    [quote="NNN636439695515887459" wrote:
    I appreciate the responses. You all let me know that C1's DAM is inappropriate for my use. If I could have Photo Mechanic as a front end in some way, that would be of interest.

    I think some are doing that, scan the forum for "Mechanic". A CaptureOne Session might be a good interface to Photo Mechanic (or other DAM Tool) - have Photo mechninic send image files to Capture One via the CO Session's Capture folder, edit the files in the Session, and if Photo Mechanic has a hot folder perhaps use that to export the files from CO back to Phto Mechanic.
    0

Post is closed for comments.