25 Minutes to Load 19342 Image Catalogue
I open Capture One and select Catalog Collections > All Images and then have to wait 25 minutes while the thumbnails load into the viewer. Before that time is up I cannot be sure that any search I do is searching the whole catalog. This is not a very satisfactory situation. My machine is not slow, it is a desktop with i7 and 32gig RAM running Windows 10. Looking at Task Manager during this time I see a lot of Disk activity with the individual RAW files on my hard disk apparently being read. Capture One seems only to be using one core during this time. Does anyone know what is happening? Is this situation normal?
0
-
Is the preview size correctly set? 0 -
If you choose Catalog Collections > All Images, CaptureOne reads all images. That takes time. The workaround is to create a user collection. Name it "All". Then (a last time) click Catalog Collections > All Images. If all images are loaded, select all (Strg+A) an drag them to the User collection "All". If you now select the selection, the pictures are there in no time. The only thing to do is, after importing new pictures, you have to click the "Recent Imports" and add the new images to the Collection "All". 0 -
There's no reason for CO to read the RAW files when displaying all images. That's what previews are for. 0 -
[quote="John Doe" wrote:
There's no reason for CO to read the RAW files when displaying all images. That's what previews are for.
Not unless the existing previews were created with different criteria set than is now the case.
Preview size for one thing but there are likely to be a few others.0 -
I think Christian from Phase One once explained what would prompt CO to regenerate previews. Can't remember off the top of my head, though. We would need to search the forum. 0 -
It's normally because it's Windows only BUG/Feature. Some Months ago I created a Ticket at Phase One and ...... they will try to create a fix 😊 0 -
I must say that even when it takes 25 minutes to generate 19.342 previews that's pretty fast.
Doesn't seem unlogical that you have to wait a 'bit', like 0.07 sec / photo.
(if I calculated right)
Maybe it's an idea to use smaller subcollections when you start and merge them later?0 -
Thanks to all who have replied to this thread. I have now discovered what the problem is. A week or so ago I recovered a batch of pictures from my archive and wanted to import them into Capture One. Now, they had originally been managed in Lightroom and, more importantly, key-worded in Lightroom so to transfer the keywords to Capture One I got Lightroom to export sidecar XMP files. I set Capture One to Auto Sync sidecar XMP : Load, imported the files and my keywords were imported into Capture One along with the RAW files. Great!! However all my recent troubles are due to my forgetting to reset Auto Sync sidecar XMP to None. What has been happening is that every time I open Capture One and select All Images Capture One went about Autoloading metadata from each RAW file and trying to find 19342 non-existent XMP files. 🤭
Loading time is till a little slow but at around a minute or so is something that I can live with.0 -
[quote="NN161456UL" wrote:
If you choose Catalog Collections > All Images, CaptureOne reads all images. That takes time. The workaround is to create a user collection. Name it "All". Then (a last time) click Catalog Collections > All Images. If all images are loaded, select all (Strg+A) an drag them to the User collection "All". If you now select the selection, the pictures are there in no time. The only thing to do is, after importing new pictures, you have to click the "Recent Imports" and add the new images to the Collection "All".
Thanks for that suggestion. Once I had sorted out my basic bit of finger trouble with metadata syncing I tried your suggestion but I'm afraid on my machine total boot time to all 19342 thumbnails loaded was 3min 50secs for the all image user collection as against 3min 25sec for the catalog All Images.0 -
Forgive me, but re reading every image every time on open is just plain poor implementation (I am a software guy that deals in such things). Even if you believe you actually need a handle on every image up front (BTW, you don't, or at least you shouldn't), put the initial access in a background thread (there are many offloadable ways to initialilze hash tables). Do lazy loading. Don't hold up the whole user experience because of a bad coding choice.
I'm sitting here, now going on over an hour for a 19K image catalog that was open yesterday (which took over an hour because I had to restore from backup because key wording corrupted the catalog and crashed C1!!!!!!). Once restored, I 'forgot' to select a collection before I closed. Having to select a smaller collection just to make this usable next time is absurd. I love C1 for its image editing capabilities. I really do. Its the only reason I've put up with this insanity, but my patience has been severely tested.
The problems with the catalog have been monumental (and well documented) and gotten worse with each release. I did start using sessions instead of one big catalog because of this. I can't believe that this problem hasn't been fixed for the years that it has been an issue (and actually gotten worse).0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare