Folders with Many Images = Windows Death Spiral
<Rant On>
Really! I'm not asking much am I, Capture One? I just want to open a folder of images that, let's see . . .
LightRoom opens fine (to import)
Photo Ninja opens fine
Even the very un(performance)stellar CNX opens fine
But Capture One just can't do it without crashing my whole system. Not every time. Sometimes the system will recover. Sometimes not. Many times I can't be bothered waiting around and pull the plug on C1.
Why oh why can't this be fixed??? My machine is low on specs. I admit it. But it is the same machine that the competition is using to access the folders of images too. Is it asking too much for a reasonable speed (and really, I'll take stability over speed; a slow C1 is infinitely better than a crashing Windows session)?
Yes, that's a rant.<Rant Off>
Sorry!
I would, however, hope for some suggestions in how to make C1 more stable, if not more speedy when accessing image folders.
TIA,
brntoki
Really! I'm not asking much am I, Capture One? I just want to open a folder of images that, let's see . . .
LightRoom opens fine (to import)
Photo Ninja opens fine
Even the very un(performance)stellar CNX opens fine
But Capture One just can't do it without crashing my whole system. Not every time. Sometimes the system will recover. Sometimes not. Many times I can't be bothered waiting around and pull the plug on C1.
Why oh why can't this be fixed??? My machine is low on specs. I admit it. But it is the same machine that the competition is using to access the folders of images too. Is it asking too much for a reasonable speed (and really, I'll take stability over speed; a slow C1 is infinitely better than a crashing Windows session)?
Yes, that's a rant.<Rant Off>
Sorry!
I would, however, hope for some suggestions in how to make C1 more stable, if not more speedy when accessing image folders.
TIA,
brntoki
0
-
Please contact our support team with this one. They can help you out. 0 -
Look at my thread about NAS problems (which is in fact not a NAS problem).
CO8 makes huge traffic to image opened folder every time You open that folder. System tools shows, that even hundreds files can be opened simultaneously (image files and an associated co-files created by CO8).
Opening huge sets of images makes my system freezing for long time, sometimes CO8 disappears (leaving some zombie processes that slows down computer for 10-20 minutes).
Make support case, I hope that they find solution.
Regards.0 -
I agree with the two posters. Opening C1 causes my hard drive fits for many minutes. Lightroom doesn't. If this is a problem that can be solved by tech support it ought to be widely publicized, not handled by a one-on-one support ticket for each user. 0 -
Are you using a Session or a Catalog?
I'm new to Capture One and have been trying to decide which is the best for me. One thing I have found though is that if you are using a Session and then browse to a folder outside you Session structure, Capture One will create a CaptureOne sub-folder which it populates with .cof and .cop files for every image in the folder (under CaptureOne\Cache\Proxies).
Depending on how many images you have in the folder this can take quite some time and cause your computer to slow down while it's generating these files. I shoot RAW + JPEG, and found if I browsed to a folder of mine which had 15GB of RAW and JPEG images Capture One would take about 25 minutes to generate 2.5GB of these .cof and .cop files! This is clearly a waste of disk space and processing, as I only want to edit a small fraction of my photos.
I just concluded that this is not the way to use Sessions. Instead of browsing to a folder outside the Session structure you should import the images you are going to edit into the Session (the Capture folder). This, however, does create a duplicate copy of the images you are importing.
So I've just gone back to using a Catalog and importing images I want to edit into the Catalog. This works much like Lightroom so you have any problems with using a Catalog in Capture One.0 -
I started with sesion on NAS server. In v7 I was working this way, on usb 2.0 drive.
When I opened folder, CO8 started to process files, just like V7. It took some time.
But when I revisited folder, program started to process all files again - and this is new "feature" of V8.
Then I tried to work with catalog - again, performance was terrible, including some problems with importing images.
Then I looked closer at the program activity, when session is stored on local disc, an I've discovered, that it reads lots of data, exactly like during working on NAS server.
I still prefer sessions. It fits better my needs.0 -
2eyesee,
I'm working with a general session; i.e., a session I have set so I can "freely" access any image on my system.
I've considered the session vs. catalog question and came to the conclusion that sessions are a better way to work for me.
Sorry I failed to inform everyone that this was a session I was referring to.0 -
[quote="NN635468391227852789UL" wrote:
I'm working with a general session; i.e., a session I have set so I can "freely" access any image on my system.
I've considered the session vs. catalog question and came to the conclusion that sessions are a better way to work for me.
I tried to make Sessions work too, as the idea of importing into a Catalog didn't appeal to me. But I think you're experiencing the same problem as I found - when using a Session, when you browse to a folder Capture One spends a long time building previews of every image in a CaptureOne sub-folder. That's overkill for me when I only want to edit a handful of files, so I'm back to using a Catalog.0 -
many images = how many? 0 -
I use sessions.
I mostly create a specific session for each shoot but do have a couple that are used as "open" sessions sometimes - although of course any session can be used "openly" if you feel like it.
Mostly I specifically import into a session directly form the memory card. Sometimes I will have saved images in folder in the field on a disk drive and so will import from the drive. When I do that it means the original images on the drive become a backup. Eventually I will backup the entire session folder structure and the originals become mostly redundant as they will be contained in the session backups.
However, that is because I usually import all images to the session.
An alternative to browsing to a folder or importing all is to make a selective import to the session using the import function to browse the images and select the one or several that are to be worked on. Doing that will leave all the originals where they were and just make copies of the files you want to work on. That could be in a "Capture One" folder within their parent folder for example but would most likely be easier to manage over all if it was part of the Session folder structure.
You could, of course, do something similar by pre-selecting the images you want to work on into a their own folder (using copy or move in Windows or another application entirely) and them pointing C1 at that folder.
If sessions appeal to you more than Catalogues (and they certainly do appeal more to me) then there are some quite simple and flexible ways to make them work with you and for you.
That said I would also observe that having a machine with a configuration that offers high end performance makes the entire experience much more joyful. It's a fact of our times - there is not really much we can do about it without giving up something somewhere else - choosing to work with smaller files for example.
HTH.
Grant0
Post is closed for comments.
Comments
9 comments