Preview Cache: Time and Size
I use C1 as a hobby. Pictures consist mostly of my kids. I used C1 for a year and quit since my wife could not drag-and-drop picture onto Internet Explorer (to download – print)… which meant I have to “develop†*ALL* the pictures to JPG anyway for her to look at (what a pain)… I used the quickproofs but that was not good enough to print so was useless in this case. I have found no other software package (not even Photoshop CS2) that is as easy to use as C1 and find myself forced back 😊.
What I loved 😂 : One click DELETE, one click White Balance and Exposure compensation. No “Load Picture, Image-> Adjust Levels, correct, save picture as. Blah blah blahâ€.
What I hated 🤬 :
1) Waiting for the pictures to load (painfully slow).
2) LE’s limitation of the number of batched develops.
3) No easy way to develop all (better than quickproofs)
I have version C13.7.1 LE running on a dual P4 3GHz machine with 1.5GB ram.
I still have the same dreads. Have any of my concerns gotten better? Or are there tricks I can use I don’t know about? Any help/pointers would be appreciated.
Thanks
-Ed
What I loved 😂 : One click DELETE, one click White Balance and Exposure compensation. No “Load Picture, Image-> Adjust Levels, correct, save picture as. Blah blah blahâ€.
What I hated 🤬 :
1) Waiting for the pictures to load (painfully slow).
2) LE’s limitation of the number of batched develops.
3) No easy way to develop all (better than quickproofs)
I have version C13.7.1 LE running on a dual P4 3GHz machine with 1.5GB ram.
I still have the same dreads. Have any of my concerns gotten better? Or are there tricks I can use I don’t know about? Any help/pointers would be appreciated.
Thanks
-Ed
0
-
[quote="elandau" wrote:
What I hated 🤬 :
1) Waiting for the pictures to load (painfully slow).
2) LE’s limitation of the number of batched develops.
3) No easy way to develop all (better than quickproofs)
1. Not much way around that. This is where Capture One gets its speed in adjustments, by shifting the computer work to the start of the job. I just add the collection on which I'm going to work, and then leave the computer. Go make tea/coffee, or read a couple chapters out of a book. I don't just sit there waiting for the computer to finish--a watched clock never moves.
2. I've never run into this limit. I don't think I've ever batched up more than a hundred or so images at one time, but still I didn't think there was a limit at all. Or do you mean the 1 vs. 3 pre-defined batches? I thought that was going to bother me after I demoed the Pro but settled on buying the LE. Truthfully, I never notice it anymore. I just make use of the "Include 3 digits for duplicated filenames" preference and name all the photos from one shoot the same way. So I get one developed image that has no number and then the rest are sequential. I rename that first one "...-000.jpg" and then they all sort properly.
3. What's wrong with Ctrl+A, Insert? That'll select all the images (or as I prefer Alt+T to select the tagged images) in the collection and add them to the batch queue and start processing. Then while the queue is running you can go read another chapter.
Edit: Let me just add two comments to my above thoughts. In 1. and 3. I say I go and do something else while the computer is processing. There is no real reason to do this in Capture One, other than it seems to finish faster if left to do one task. Capture One does allow one to start making adjustments as soon as a collection is added. It will even process the preview files out of order if you click on any thumbnail. And when processing the batch there is also no reason that another collection can't be opened and the next bit of work started.0
Post is closed for comments.
Comments
1 comment