batch processing in 4.0
I can't figure out how to do batch processing of images in vers. 4.0. It was obvious in 3.7x but now I am baffled. When I select all of my raw images for processing only the first of them ever gets processed.
0
-
Naturally... you just select all and hit control-shift-D could it be more obvious 🙄
I searched on "batch" in the manual and it made no mention of this... fortunately another user set me straight. Why the hell would anyone select a whole bunch of images, hit the process button and only want to process ONE??? I for the life of me can not think of a good reason.
Cheers, Joe0 -
[quote="shewhorn" wrote:
Naturally... you just select all and hit control-shift-D could it be more obvious 🙄
I searched on "batch" in the manual and it made no mention of this... fortunately another user set me straight. Why the hell would anyone select a whole bunch of images, hit the process button and only want to process ONE??? I for the life of me can not think of a good reason.
Cheers, Joe
Great but that not the way I work (and I suspect I'm not alone)
In 3.7 I use the mouse wheel to move from image to image (a feature removed) Each image has a couple of adjustments automatically made based on my preferences (another feature removed) then I decide if the image makes the cut or not. If it does I make final adjustments and add the image to the queue. (Yet another feature removed) Once I've gone through the batch and only the good images are added to the queue, I hit process and move onto to other thing while C1 processes in the background. Its extremely efficient. Efficiency that has been removed in v4
Note: NOT ALL IMAGES ARE PROCESSED. So selecting all and then pressing a key command is useless.
Rob0 -
[quote="rkircher" wrote:
In 3.7 I use the mouse wheel to move from image to image (a feature removed) Each image has a couple of adjustments automatically made based on my preferences (another feature removed) then I decide if the image makes the cut or not. If it does I make final adjustments and add the image to the queue. (Yet another feature removed) Once I've gone through the batch and only the good images are added to the queue, I hit process and move onto to other thing while C1 processes in the background. Its extremely efficient. Efficiency that has been removed in v4
Note: NOT ALL IMAGES ARE PROCESSED. So selecting all and then pressing a key command is useless.
Rob
The odd thing is Rob, that in the User Guide (p71) it says that the mouse scrolling should work!
On the processing front, why don't you just click on the process icon (or ctrl-d) when you're finished with each image to send it to the batch queue and get on with the next one?0 -
[quote="imacken" wrote:
[quote="rkircher" wrote:
In 3.7 I use the mouse wheel to move from image to image (a feature removed) Each image has a couple of adjustments automatically made based on my preferences (another feature removed) then I decide if the image makes the cut or not. If it does I make final adjustments and add the image to the queue. (Yet another feature removed) Once I've gone through the batch and only the good images are added to the queue, I hit process and move onto to other thing while C1 processes in the background. Its extremely efficient. Efficiency that has been removed in v4
Note: NOT ALL IMAGES ARE PROCESSED. So selecting all and then pressing a key command is useless.
Rob
The odd thing is Rob, that in the User Guide (p71) it says that the mouse scrolling should work!
On the processing front, why don't you just click on the process icon (or ctrl-d) when you're finished with each image to send it to the batch queue and get on with the next one?
The scroll wheel scrolls the entire thumbnail window ONLY when that window has focus meaning I've clicked on it. It doesn't scroll from image to image. If used when the main viewer has focus the image in the view zooms. I NEVER USE ZOOM. In 3.x no mater what you’ve clicked on rolling the scroll wheel moves you to the next or previous image. This is a HUGE productivity boost when processing hundreds of images.
The problem with just hitting process is it starts processing right away which can often slow down everything else even on my P 3.2 with 4 gigs of ram. I'd rather just add all the images to the queue and then hit process and go get a cup of coffee or shoot a few more photos. This way I can be more productive with other things while C1 is churning out my photos.
Rob0 -
[quote="rkircher" wrote:
The problem with just hitting process is it starts processing right away which can often slow down everything else even on my P 3.2 with 4 gigs of ram. I'd rather just add all the images to the queue and then hit process and go get a cup of coffee or shoot a few more photos. This way I can be more productive with other things while C1 is churning out my photos.
Rob
Fair enough Rob, but it has absolutely no slow-down effect on my system I'm pleased to say. In fact processing my 5D files takes around 3 seconds, so by the time I move to the next image, the previous one has been processed.0 -
Eisence: To process a batch of photos, try this:
In "Output" tab - on the RHS of the "Process Summary" section you'll notice a small triangle - click on that, and you'll see two process possiblities:
"Process Primary Variant" and "Process Selected Variants".
Clicking on "Process Primary Variant" processes just one photo
Clicking on "Process Selected Variants" processess all selected photos.
BTW "How Do I Create A Batch" is on page 68 of the Help Manual, but it really isn't 100% clear
Hope this helps.0 -
[quote="imacken" wrote:
[quote="rkircher" wrote:
The problem with just hitting process is it starts processing right away which can often slow down everything else even on my P 3.2 with 4 gigs of ram. I'd rather just add all the images to the queue and then hit process and go get a cup of coffee or shoot a few more photos. This way I can be more productive with other things while C1 is churning out my photos.
Rob
Fair enough Rob, but it has absolutely no slow-down effect on my system I'm pleased to say. In fact processing my 5D files takes around 3 seconds, so by the time I move to the next image, the previous one has been processed.
Well the jury is still out on this. I have a xmas show to do that was shot primarily with a 1DMark III and a 20D. A few hundred images. I was planning on using this shoot as a production test of C1 v4. First I have to work out some of the individual settings such as sharpening and saturation and then I’ll process the full series. We’ll see but I’m very skeptical that my overall production time will be the same or go down. Physical CPU processing may be handled better in the new software but the other hoops I’ll have to go though will increase the overall processing time.
Rob0 -
Another way to do it if you really don't want the batch to run while you're still working. At the bottom right of the batch tab is a button labeled "start" or "stop". If it is "start", then click and it will become "stop". Now the batch won't run until the button is clicked again. Images can still be added as you work them (ctrl D). 0 -
[quote="bodog" wrote:
Another way to do it if you really don't want the batch to run while you're still working. At the bottom right of the batch tab is a button labeled "start" or "stop". If it is "start", then click and it will become "stop". Now the batch won't run until the button is clicked again. Images can still be added as you work them (ctrl D).
Just one more click that I didn't need to do in the past. Add that to all the rest of the newly added clicks and choices I'm forced to make and my productivity time just went down exponentially.
Rob0 -
I have the same probem. However, it also won't do a "batch" rotate either. When I select a series of images that all have the same rotation then try rotate either direction it just rotates the first image not the entire selection. It worked fine in v3.x What the heck!
I am seriously thinking about dumping Capture one and just using photoshop by it's self!0 -
[quote="gernerttl" wrote:
I have the same probem. However, it also won't do a "batch" rotate either. When I select a series of images that all have the same rotation then try rotate either direction it just rotates the first image not the entire selection.
Have you held shift down first? Shift is pretty necessary for any 'batch' process, so shift then click on process does multiple images to batch, and shift-rotate does multiple rotates.0 -
yes. it only rotates or processes the first image! 0 -
Here's one way to do a batch:
Make adjustments to a set of images
Select one and click the Process icon in upper right
Continue selecting and initiating processing
All the images appear in the Queue list, and process one after another
CaptureOne4 seems to lack an Add control and a list of images-to-be-processed, which you then send for processing.
Instead, you just send image for processing, and they form a queue if you process a number in quick succession.
I with I knew a way to to make output go to a subdirectory of the current image directory. I'm used to the way C1 version 37 did this, it's something I prefer to ACR.
Once I understand variants better, this may change...0 -
[quote="TomW" wrote:
...I with I knew a way to to make output go to a subdirectory of the current image directory. I'm used to the way C1 version 37 did this, it's something I prefer to ACR.
...
You have to set it up manually each time... create the new target subfolder and designate it as the Output folder. Another great leap forward in efficiency. ☹️
Nill
~~
www.toulme.net0 -
that just gives me another reason to not stick with C1...who designed this version...the three stooges??? 0 -
[quote="gernerttl" wrote:
that just gives me another reason to not stick with C1...who designed this version...the three stooges???
Folks who obviously have never converted large quantity of images with the old version and therefore know just how efficient it was/is.
Rob0 -
One really does have to wonder whether the designers of v4 had ever used v3.x seriously.
Nill
~~
www.toulme.net0 -
> it only rotates or processes the first image!
The batch processing routine I decided on for myself: click the "batch" icon in the toolbar to open the queue panel (empty at first). Click "STOP" at the bottom of the screen as I don't want processing to start when each image is added (the button then changes to "START"). When I'm done with all images, select the ones to be processed via Control+click or Shift+click in the browser. Press Shift+Control+D to add them to the queue. Unfortunately, images can't be dragged from the edit window into the queue panel (kind of an obvious use of a GUI...oh, well). When I'm ready to start, click the queue's START button.
Or if I want to add an image just after its edits are completed: with that image in the editing window, press Control+D to add it to the queue (why Control+D and not INS? Go figure.)
A "gotcha" is that you can add the very same image more than once (I don't mean an image plus some variant, but the identical image). Why this is considered a useful feature, I don't know.
One of my complaints during the beta-testing was: no remove-individual-image-from-queue control. I was wrong about that. The DEL key removes images that are selected within the queue. They can be "Shift-selected" or "Control-selected," as in the browser panel. This use of the DEL key is undocumented. (Of course. Who would ever need such a feature? :-)
Even though you hold down SHIFT to perform some operations on multiple images, within the queue you can press only DEL; if more than one image is selected, then all selected are removed from the queue. You can add SHIFT but it isn't required. The documentation mentions that removal or deletion of certain objects is done with either DEL or BACKSPACE. But BACKSPACE doesn't work within the queue. Go figure.
I agree with others here that it's nonsensical to require SHIFT to perform the same action on multiple selections. I don't remember ever using a program with "apply to multiples" capability that forced you to use the additional keystroke. These kinds of problems suggest that the software has not been designed by people who make heavy use of it. If it had been, guaranteed they would have become quickly fed up with "nuisance keystrokes" and would have designed at least a user-selectable option not to use SHIFT for multiple operations. Or, there could be a dialog asking you to confirm that you want the change applied to all selected images.
It just now occurs to me to test: if an edit is applied to multiple images but it's a mistake, can it be undone to all selected images immediately afterward?
W.r.t. the mouse wheel not being used to change images -- it's the kind of control that should be made a user option, along with quite a bit else for which there aren't any options right now. (Such as the endlessly-appearing dialog box warning you when the queue is in "STOP" mode. Please, one warning per session is enough...talk about a nuisance. A 'don't show this warning again' checkbox is called for there -- and that would call for a 'reset warning dialogs' option in Preferences.)
But at least when the focus isn't on an editable text field or a slider, pressing the left- or right-arrow key moves from image to image. ... well, sometimes. Sometimes it just stops working! Then I have to click an image within the browser before the arrow keys will work again for "previous" or "next". Just another bug, I guess.0 -
I don't really understand why they did that. Do they have some reason ?
It has been asked by the beta testers not to do that.0 -
[quote="gernerttl" wrote:
yes. it only rotates or processes the first image!
You must be doing something wrong then. If you select as many images as you want by ctrl-click then hold down shift while clicking on rotate, then they all should rotate. Same for 'process'.0 -
[quote="rkircher" wrote:
Great but that not the way I work (and I suspect I'm not alone)
In 3.7 I use the mouse wheel to move from image to image (a feature removed) Each image has a couple of adjustments automatically made based on my preferences (another feature removed) then I decide if the image makes the cut or not. If it does I make final adjustments and add the image to the queue. (Yet another feature removed) Once I've gone through the batch and only the good images are added to the queue, I hit process and move onto to other thing while C1 processes in the background. Its extremely efficient. Efficiency that has been removed in v4
Note: NOT ALL IMAGES ARE PROCESSED. So selecting all and then pressing a key command is useless.
Rob
Rob, it appears to me that they jumped the gun on releasing version 4. To me, it makes more sense to replace the pro version, then remove "key features" and release the "new LE" version. But, what do we know. We obviously weren't asked for our input on the new version. I take that back. I guess we were, they just didn't listen. They did what they wanted to do.0 -
What about keystrokes for exposre corrections (contr.+/- (exp), alt. +/- (contr.), shift+contr (color). from versions 3.x??
I also miss the folder constructions from earlier versions, the "process to folder inside actual session folder" option. This is a big issue.
I used to open up 30 folders in a row, (I usually take 10-15 sessions pro day), made some adjustments to all of the images (with the short cuts), selected numer of pictures from each folder, tagged them, and selected the tagged ones, and then sent them to process. Where inside of each folder CO 3.x made a "developed folder" with the processed images.
The computer was then sweating with the process for 4-5 ours during the night but kept everything organised within each session folder.
Another thing is batch rename of the raw files? it was realy easy with older wersions but seems to be gone in CO4
Am I´ wrong in some parts here? I´ve been waiting for faster CO4 than CO3.x with more productiveness, simplier and smarter but, all we got is nicer look on the windows, with nothing better inside the program. And most of the shortcuts are gone.!!
Gunnar Leifur0 -
Why would they hide the que process in the process summary? (process selected variants) Put it in the open on the output page as a selection. Name it "ADD selected images to que" Perfectly clear. The variants are allready selected elsewhere. Change the "little tiny Process window" to START/STOP and have it change color green/red.
Interfaces need to be "kissed".0 -
Just went through and setup 48 1DS MarkIII images and then batch processed them.
Sorry PhaseOne, I'm back to DPP. It may not have quite all the bells and whistles, BUT the output quality is noticably better IMO.
Maybe later in 4.2 or 4.3 it might be OK. and the interface might be worked out better also.0 -
Possible to keep the queue if computer is shutdown?
If I need to exit the program and turn the computer off in the middle of a batch, is it possible to restart the batch queue next time computer is up and running?0 -
[quote="dan74" wrote:
Possible to keep the queue if computer is shutdown?
If I need to exit the program and turn the computer off in the middle of a batch, is it possible to restart the batch queue next time computer is up and running?
Yes, this is possible and it is very easy at the same time.
During batch processing, you can stop the processing at any time from the Batch tool (button below). Now you can close the program and shutdown the computer. The next time you start the program, you are reminded of images in the batch queue and asked whether you want to start processing them (or not).
The queue is retained and you can start it where you left it.0 -
Excellent! Thank you for quick respons. 😄 0 -
My computer is a little bit slow?
Today I started batch processing of 407 images. Estimated time was 80 minutes. After 80 minutes had elapsed, I still had 190 images left in the que (that is 46% to go). It seems like my computer is almost half as quick as the Capture One estimation?!
How is the estimation done, does it assume some kind of minimum or average computer capacity that is beyond my level of performance?
(I only have AMD 1,8GHz processor and 2GB of RAM, mabye it is way to slow)?0 -
The processing time estimate is not accurate. In the first place estimated time is based on processing the image, not on saving the output to disk, which adds approximately the same amount of time.
Next, though not tested, a few more details like upsizing and rotation add to the amount of processing time and I suspect that is not taken into account as well. I also suspect that if I start with 10 files of different size (i.e. amount of megapixels) that is not calculated as well. The last two notes are assumptions so don't take it for granted.
To cut a long story short, as long as you are happy with your computers performance, enjoy it and don't be mislead by estimates of CO4. 2GB RAM is sufficient for CO4. If you open a lot of images at the same time in Photoshop or equivalent, then it could become a bottleneck. You can use Task Manager to see if you run out of memory.0
Post is closed for comments.
Comments
29 comments