10|23
2013

Capture One Workflow

I’ve been asked several times to share my Capture One workflow. Everyone has their way of working and mine is by no means a fit for all. Grab your pillow, this subject might just put you to sleep.

I use a tethered session rather than a catalog. The new session is named with the date, job number, and client name. In this case, the session name is Date-Job#-Client. The default location of the Session in Capture One is set in the Pictures folder but I locate the Sessions on the Desktop for quick access and organization. Capture One recommends locating all Sessions in the Shared folder to prevent any problems with permissions. I’ve yet to experience any issues locating files on the Desktop. Hopefully, I didn’t just jinx myself.

New_Session

My workflow normally requires one computer for capturing and another for organizing and processing. This way I don’t have to wait for my assistant to finish naming and organizing before I can continue to the next shot. The most efficient way to move files between computers is to capture images as an EIP file. This is done in the Capture One Preferences, click the check box “Pack as EIP when capturing.” An EIP (Enhanced Image Package) file format bundles the original Raw file with the image settings like Color Tag, Rating, ICC profile, White Balance, Crop and other metadata. Transferring these EIP files from computer to computer will keep the settings intact and allows them to travel with the image.

Image

Before shooting, I setup the appropriate naming convention. Other settings I use are Copy from Last in the “ICC Profile” and Copy from Clipboard in the “All Other” dialog boxes.

Date-Job_-Client.cosessiondb

After the first image is captured, I apply my presets for metadata, sharpening, white balance, etc. I copy the image settings to the Clipboard. In the “Adjustment Clipboard” I select everything I want to copy. Now all the information will automatically transfer to the following captures. Each time I make a change as I’m shooting I will copy everything to the clipboard again so all further captures will reflect the new changes.

Date-Job_-Client.cosessiondb

The next step is to process the files. Capture One has basic recipes but you can create your own according to your needs. Lifestyle shoots often have significantly higher shot count than a product shoot so I include quickly viewable jpgs to accompany the hi-res tifs in a secondary folder. This way, the client can view and select the jpgs and reference the corresponding tifs when they are ready. The Default setting outputs processed files to the root Output folder created at the beginning of the session. This can be customized so that the output files are designated to specific locations. My Recipes include subfolders within the Output folder. Subfolders are a great way to automatically separate the file types like tifs and jpgs or other ways the processed files are best differentiated. Congratulations you made it this far, I stopped for a donut break halfway through.

Date-Job_-Client.cosessiondb

  • Tony Roslund

    Thanks Peter. Looking forward to Part II – Aperture Integration.

  • http://www.irakli.se/ Irakli Nemsadze

    Thanks for sharing!