why does C1 have to load ALL images before it can be used?
I'm using C1 v11. I have ~30k images in my catalog. When I start C1 it always starts in "All Images" in the Library folder. Then I have to wait 10 min. or so to do any searching while it loads all 30k images. I can watch the filter bar at the top of the Browser window as it slowly counts through the images. I can select other folders but then I go through the same thing - I have to wait to do any searching until the filter bar stops counting images. If I do any search or use the filters in the Library tab before the selected group of photos is loaded, the search may fail depending on whether the images I'm searching for have been loaded yet or not.
another side-effect of this behavior is that it is so busy loading images and updating the viewer that, if I select an image, I can't navigate away from it so I can't really work on any files until it's done loading all images.
Is there a way around this? Do I just have to wait and wait and wait until all images in the group are loaded before I can search?
Does anyone have an explanation (or even conjecture) as to why is this? Why does it have to load all ~30k images first? That takes a looong time. Why can't it just search the database as soon as I select a folder or "All Images" instead of making me wait for everything to load first?
-
Highlight a different folder with less content before you close C1. This will drastically speed up the start up next time you open C1.
Just one of the many idiosyncrasies of C1.
0 -
Timothy,
When you close your catalogue do you use the "Close Window" option?
The next time you open the same catalogue do you use the "Open recent" option?
The reason for what it does seems to be to establish that all of the known images are present and available for full editing (or off-line editing if not),check for anything new that may have appeared in folders (or disappeared) due to external influences - likewise metadata updates if enabled - check the filters for count values (see, inter alia, external metadata adjustments) and so on. Report on apparent inconsistency if referenced images in external folder have been moved. Create any thumbnails and preview files that may have gone missing for some reason.
Then load a selection, usually based on how that catalogue was set last time it was used so that the user gets back to where they were before, of images into memory trying to optimise memory usage for the most likely images to be called up based on previous activities, load the thumbnail and the Preview and apply the edits to the view along with, for example, "output" proofing if active, watermarks, etc.
Some activities - filter counts for example and Smart Albums - are always based on search criteria in a "live" situation and so always have to be re-assessed. Apparently reducing the number od selected filter fields can speed things up. Presumably the visible fields presented in the filter tool are always set up during catalogue opening and others may be processed in the background after control is passed to the user.
It's the same, more or less, for Sessions - except that a typical session for most users probably does not exceed a few thousand images. (I know there are some exceptions but getting to 30k or more would be a little rare I think.)
So a Session - even a large one - will open somewhat faster in typical use and you avoid have the carry the processing baggage of images that in most cases will have been edited and finalised months or year. ago.
I tend not to shut things down until I need to and even then I will often hibernate C1 most times.
As Christopher said, selecting a folder with few images will tend to allow you to take control or the C1 processes quite quickly if that helps your objectives. Similarly I think maybe selecting a filter that has no or few matching images before closing the catalogue may help - C1 certainly responds to that in a session using Windows so I would expect the same from a catalogue. I don't think I have a catalogue large enough to test the effect. And of course there is always the possibility that Mac and Windows offer different performance.
0
Post is closed for comments.
Comments
2 comments