V4 Batch needs work
The folks at Capture One need to rework (or restore) the batch workflow to be more intuitive!
First off Control+D (or Shift+ Control+D) processes the images immediately. This is not how I and a lot of other people understand *batch*. I perceive batch (like v3.7.7) as a queue to be initiated when I click a ‘go’ button. An average machine, p4 2.8Ghz with 1GB of RAM, would be crippled by 20 images in the batch.
Second having to click the Stop button to add to the queue without processing things is confusing and counterintuitive. A queue should be such that, a queue, until I tell the program to do something with it.
Third double clicking any images in the queue should take you back to that image to make further adjustments until final process. As far I can tell in v4 nothing can be done once it’s added to the queue. Well… there is removing and re-add. Again very counterintuitive.
Am I alone in my assessments?
First off Control+D (or Shift+ Control+D) processes the images immediately. This is not how I and a lot of other people understand *batch*. I perceive batch (like v3.7.7) as a queue to be initiated when I click a ‘go’ button. An average machine, p4 2.8Ghz with 1GB of RAM, would be crippled by 20 images in the batch.
Second having to click the Stop button to add to the queue without processing things is confusing and counterintuitive. A queue should be such that, a queue, until I tell the program to do something with it.
Third double clicking any images in the queue should take you back to that image to make further adjustments until final process. As far I can tell in v4 nothing can be done once it’s added to the queue. Well… there is removing and re-add. Again very counterintuitive.
Am I alone in my assessments?
0
-
RawShooter also worked this way -- processing would begin the moment the file was added to the queue, unless you'd first clicked the Stop button. One difference here is that adding files to the queue with 'stop' in effect now produces a 'do you want to start processing right away?' query every time. There doesn't appear to be a way of turning it off. One occurrence -- no big deal. The fact that it happens a lot and can't be switched off becomes irritating.
It's possible to add the same image (with identical settings -- not meaning a variant) to the queue multiple times. The image will be processed that many times, with its name changed to avoid overwrites. This should at least be a user setting -- an option to prevent this when the multiple images really are identical.
There should be a context menu available for each image in the queue. At the very least it should contain 'remove from queue' and 'update this image' selections. If you'd edited a shot already in the queue, the 'update this image' selection could enable after-the-fact edits without your having to remove the image from the queue, then add it again.
I get the feeling that these kinds of comments don't get much traction unless we start support "tickets" with the subject-line "Feature Request"...0
投稿コメントは受け付けていません。
コメント
1件のコメント