In2Photos wrote in post #3140907
Batch processing can be done several ways.
Thanks for saving me a ton of typing!
With my processing (as above) I run a series of actions that have final outputs in mind. If i am saving for web, they resize, add copyright info, watermark, sharpen and save with a certain colour space to a folder in jpeg with a number of other options. I have many duplicates of actions for different outputs.
I have an action folder called "batchprocessing" and using the posted batch methods I can press a button and have everything done for me. Once finished I do a quick scour of the processed images to see anthing anomolous and I clone/fix/correct the few needing attention.
As the machine is doing this I walk away and stow gear, eat ravioli or whatever I need to do. I come back and it's done.
This was especially helpful for me when I worked in the Caribbean. I would do a shoot, come back to the computer and download/process. I would turn right around and go back shooting. I'd come back and everything would be ready for preview. I could have people picking shots before dinner.
Quick turnaround, correct colour, excellent sharpening and dead on exposure with little input from me. It was a real chose to have to sell, shoot and present all at the same time. I couldn't afford to sit and process 100 images from a small shoot for 2 hours. CS2/CS3 has saved me hundreds of man hours that Lightroom, DPP, or anything else can't do.
Screw the "droplet" argument, you still need CS to run. Why not just do it all in CS and save some money on software!?