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. ⚠️

Catalogue Size

Permanently deleted user

Hi C1 community - I'm trying to create a catalogue made up of multiple sessions contained across multiple folders so that I can have an overview of all the work I created in 2020.  There are 10,000 individual image files.  Problem is, when I import these into the catalogue, even when I select for the original image files to remain in place, I end up with a folder that takes hours to create, is absolutely massive in size & extremely slow to load.  Am I doing something wrong?  I would have thought that if the files remain in their original folders, then the only thing the catalogue is really importing is the previews & sidecar files relating to adjustments I've made to the files.  If I can't reduce the size of the catalogue, but still maintain the ability to make adjustments to the images then it's unfeasible to vcreate a catalogue in the first place.  Is a catalogue really only useful if you have less than 1000 images?  Any advice?

0

Comments

3 comments

Date Votes
  • Permanently deleted user

    The catalogue store the previews of the picts + all of your settings.

    It is on the previews that you work, not on the original file.

    So a size of several GB for the catalogue is definitely common when you have several 1000 pictures.
    For example, I have +/- 21.000 pictures, and my catalogue is +/- 34 GB.

    1
  • SFA

    Craig,

    To a large extent it depends what size you have chosen to use when getting C1 to generate its previews.

    If you have a large dimension screen and have followed the recommendation to set the preview size near or at the native screen size then the previews may be quite large.

    On the plus side C1 can probably do most of the editing you want to do with having to refer back to and recalculate from the original source files when the view size increases. 

    Change the preview to a smaller size and you get a smaller catalog file but it may mean C1 feels the need to go back and re-calc from the base file more often when editing or, possibly, browsing if you have a large pixel capacity screen. 

    Assuming the above is in fact the case, if you want the large preview file but only when in the editing Session before loading the catalog you could simply recalculate the previews loaded into the catalog.

    What is best for you may depend on a lot of background and operational information about your setup and needs that we have not yet seen so I it is not really useful to start to suggest much in the way of more specific guidance at this time. 

    I would be happy to offer further thoughts if you want to consider them but we need to have some idea of how you want to operate and fit things to that or suggest alternatives.

    1
  • Permanently deleted user

    Thanks Claude & SFA.  I guess it will come down to assessing whether each catalogue is worth the size it generates on a case by case basis.  In some circumstances it definitely is, considering the ability to edit files without having to go back to their original folder.

    Craig

    0

Post is closed for comments.