February 2021 // The Post-Production Edition

Now, 7 minutes may not seem like a ton of time, but let’s take our wedding photography studio for example and do the math. If our studio processes approximately 120,000 images a year after culling, and we are saving 3.5 minutes per 100 images:

120,000 images / 100 images = 1,200

1,200 x 3.5 = 4,200 minutes

4,200 / 60 = 70 hours per year

Now, if you are employing people, this is a significant savings per year, but you are probably editing much of this work yourself, so having 70 more hours to spend on marketing per year than editing is 70 times more likely to earn you more money.

But that’s not the only place Capture One helps you save time.

Capture One now builds JPEG previews similar to Photo Mechanic and Lightroom, so culling is quick and easy. I have found that on less-optimized machines, such as laptops or entry-level desktops, Capture One performs much better than Lightroom. Capture One has a unique feature called Sessions, which allows you to set up a folder structure and keep the “catalog” consistent for each independent job. In Lightroom, because we have a high-volume studio, I have always kept separate catalogs per job, so Sessions is a much more intuitive way to do that. Sessions allows you to set up a folder structure template, and upon import you are able to automatically organize your images. I set up the session folder wherever I plan to store images on my hard drive. From there, I 1-star images that I plan to keep, filter all of the images by what I starred, select all, and press Command (or Control) + J to automatically move all of the images into the “Selects” folder that I set up. Next, I select all the non-starred images and press delete to move them to the trash folder. (Don’t worry, this does not actually delete the images. Just think of the trash folder as a non-selected RAWs folder.) This makes it easy to delete the trash folder once an album is delivered, which is our current workflow. This is by far the best workflow that I have ever used for jobs we edit internally and it was not factored into my speed test.

Powered by