Batch queue window stays empty when I select images
Is it just me just me? I am using version 14.2. I selected a bunch of images to export/process. According to the c1 21 manual, "The Batch tool displays the queue that will automatically start when the Process button is pressed." The manual does not specifically address how one is supposed to put images in the batch queue window.
The batch queue does display when the Process button is pressed, but until then, nothing is shown the Batch Queue window. This makes the batch window useless. Am I doing something wrong or is the batch queue window no longer functional?
-
In 14.2 (and earlier) you didn't add images to the batch queue window directly. But if, for example, you selected 50 images to be processed (in the browser) then hit the process button, they appeared in the batch window and as each one was done, it would disappear from the list. So you could see how the task was progressing, and if you wanted you could pause the batch, and do things like remove images from the list, or move them up to the top so they got done first.
(Note that in the newest version, 14.3, there is a new Export feature, and it doesn't have a batch queue.)
Ian
0 -
The batch window is not useless but you might have a specific workflow in mind which I don't understand. Fact is that you can select one or several images (variants to be precise) and until you don't tell C1 what to do with them, of course nothing will happen. It is just a list of selected variants, and one of them always being the primary one.
Now, if you want them to appear in the output batch queue you can do the following (n 14.2 and earlier):
Stop the batch queue if you don't like them being processed immediately. Then take your time to select and put variants to the batch queue via the process button/icon. Gather them all and delete the unwanted ones before you process them. Process the remaining ones. Pause and resume if you like.
I never worked like this, if I want them to ouput altogether only after I have finished deciding which ones I'd rather select the ones in the browser and start processing them all together, or I tag them with a color or keyword and filter them all in the browser, or put them to a static album before I output them, then I have no need to delete some from the queue. But most of the time want to ouput them individually after or intermediately during I edit them.
0 -
Thanks Ian and Beo. I understand how it works, but don't understand how the manual says it works. Most of this revolves around pausing the batch queue and editing its contents. This is the entire paragraph at the bottom of page 69 [my comments in brackets]:
"The Batch tool displays the queue that will automatically start when the Process button is pressed [but by implication, not before]. Control the queue [how would you do this if the queue only appears after pushing the Process button and the queue entries disappear after each is processed] for processing and check which images have been processed previously in the Batch tool. Press backspace to delete images from the queue or drag-and- drop the listed image files into a preferred arrangement to change the process order [this would require a way to do this before Processing begins, but after the queue had been populated]. It is also possible to reprocess files from the history tab."
I don't much need to be able to do exactly what the manual says I can, so admittedly, I am curious about how to do exactly what the manual says, which would involve populating the cue, editing it, and then pushing the Process button as described in the manual.
If either of you could describe this, that would solve the mystery. Otherwise, it seems something was lost in translation or the manual is just not helpful on this point.
0 -
Jerry,
You pause ("Stop", via the Batch Tool) the queue so that the output processing does not start at the point you send your selection for output. You can also pause (Using Stop again) it when it is running if you wish to make changes to the queue.
As far as I know the default setting for the queue is Stopped but if you are already using it in an open session and have started it it will be running.
If it is stopped I see an advisory message to that effect if I send some images to the queue.
0 -
1. In the batch queue, if the button on the bottom says "Stop", then click on it. If it says "Start", then do nothing.
2. Select your images, click on the process icon. Repeat this step if you like for other images.
3. Rearrange the order in the queue via drag-drop with the queue.
And yes, manuals are not always perfect. And most verbal or written sentences are often ambigious.
cheers
EDIT: SFA, we submitted at the same second...:-)
0 -
Part of the trouble is that if you only have a few images to process, they're done, and the batch queue is empty again before you get to try to pause it or restart it! I can't now take a screen shot to demonstrate because I am now on 14.3, but as far as I recall it wasn't too difficult to master. Once you had selected a large number of images to be processed, and pressed the process button (or Cmd-D) Capture One worked its way down the list. There was a button to pause it, and if you had paused it, there was a button to restart it.
Ian
0 -
OK. I got it, now. Thanks to BeO, Ian and SFA. So simple, once you understand it. I rarely process more than a few dozen images from my catalog at a time and have always used the Export method rather than the Process method, so your help really clarified things.
To summarize:
1. Open the batch queue. The button should say Start. If it says Stop, processing will begin as soon as CMD D is pressed.
3. Select variants.
4. Click on CMD D (this was the part I was missing)
5. Delete or rearrange order as needed and press Start to start processing.
I have written software manuals and I understand how hard it is when you know the program intimately to understand how hard it can be for users to need clear concrete instructions.
Having figured this out, now it's all different in version 14.3. I am waiting for the engineers to make good on their promise to fix 14.3 processing before I move to the next version.
0 -
There is really no need for Step 1 unless it is important to you to change the order of the the processing. I nearly always just select the ones I want in the browser, hit Cmd-D and let it do its thing. When they're done, they're done.
Ian
0 -
Jerry,
For many users, after a few short minutes of discovery and contemplation, the new Export tool with the Output Process built in may well seem quite familiar and perfectly usable. For some, as we can see in the forum and other places, it seems to be highly disruptive.
It might have been better to call it the Output Processing tool with Export built-in but that would probably go against the convention of several decades of products dominant in the marketplace. (Probably none of which offer the power of the Output Processing as it used to exist let alone now exists.)
If you really do need to select images and then manipulate the order of processing for some reason then sure, the new arrangement eliminates that possibility (or, to look at it another way, that chore ... ;) )
But, in effect, the Processing process is very simple and always has been.
I too, at times, wrote user documentation - ground-up stuff to start with, edit previously existing later, proof reading the work of technical writers even later. It was certainly tricky to feel confident that one had produced work that all likely user types would be able to concentrate on and understand. Fortunately the average user never read them anyway and, in the end, the IT and implementation staff gave up issuing them. Even in PDF form once the forests had been saved.
I recall working with a group of BackOffice people from one company training them on how a system worked to replicate and enhance their existing admin processes. One young, enthusiastic and clearly intelligent young lady was entirely baffled by what was a very simple process.
Talking to her one on one after we completed the day it suddenly clicked with me that she was very new to the company and the job. In fact probably very new to work in general. No one had taken any time to explain the purpose of the session or even what her job was about. Having assured her that her frustration that everything seemed so strange and scary could easily be eliminated, I spoke to the project manager and asked her to ensure that people took a little time to provide some guidance.
I doubt they used our days and weeks of User Guide creation, production, printing and binding. Most of the multiple sets they had asked for remain stacked in a cupboard for the entire time of my involvement with the project. (By which time they were probably mostly obsolete ...)
A few weeks later one could observe that the young lady was extremely confident about what she was doing and was, by then, helping her more experienced and older colleagues. Around a year later she was running the department. All it needed was a little time with someone to set the scene for her.
I think that is where the onscreen tips can come in. Make specific information available at the immediate point of need. V21 seems to do that quite well, on the whole.
That said, Jerry, when I first started with C1 I totally assumed I knew all about the concept of "Sessions" and how I would use them. It was all very similar to the application I was already using. However, about 10 months in and with occasionally confusing things happening, I decided it was time to study sessions in a little more retail. About an hour later I had a lightbulb moment, realised I had been overlooking a lot of powerful options that my other application did not offer .... and then rarely looked back after I slightly changed the way I approached things.
A couple of versions later I did the same with Output Processing, taking to time to work out where and how it could be used to make my workflow more consistent and more productive. And more satisfying.
I like it when software makes quite complex activities seem simpler than they are "under the hood". I rarely appreciate using something that is extremely complex and takes intricate steps and a lot of time to produce results ... although I can appreciate the talent of people who can work with such tools and produce excellent results. It's just not something that grabs my everyday interest and tempts me to involve myself in a deep learning curve for which my enthusiasm is not well matched.
All of that is more or less a rather verbose version of what Ian Wilson wrote in the previous post ...
0 -
I have either clicked Export or Process and have never made use of the batch queue. Just to show how simple my process for getting an image into another form, I almost always use the Export function.I just stumbled into the batch queue while trying to figure out what I was missing by exporting, rather than processing. While reviewing the processing process I got stuck trying to figure out how to use something for which I had no particular use, the batch queue. It is neat to see each image being processed, but as Ian suggests, it is not a big bell or whistle.
0
投稿コメントは受け付けていません。
コメント
10件のコメント