Thinking about a workflow

Post Reply
Nordlicht
Posts: 35
Joined: 29 Sep 06 19:32

Thinking about a workflow

Post by Nordlicht » 14 Dec 17 21:30

Hello,

I'm using CaptureOne to develop most of my RAW. Since a few days, I've an new camera, which is not supported by C1. I've to use another converter.

Now I'm not sure, how to handle things with PSU. Import all RAWs, sorting and assign keywords is the first.

Converting the RAWs with C1 and another converter the next step.

What's the best way to manage the converted files. Import a derivate file into PSU and catalog this file? What's the best way to mark the picture converted with C1 or another converter? PSU does not recognize the editing of C1 or LR or PS.

C1 and LR are another way to work. There is no need to export and catalog a kind of masterfile. I can find the image and export just in time for each usage.

Thanks for your input

User avatar
fbungarz
Posts: 3140
Joined: 08 Dec 06 5:03
Location: Galapagos, Ecuador

Re: Thinking about a workflow

Post by fbungarz » 21 Dec 17 0:54

What's the best way to manage the converted files. Import a derivate file into PSU and catalog this file?
I would use a file naming convention, to designate the files edited/modified by your raw converter (e.g., add "_C1" to the file name if your file was generated by C1) and then use PSU's versioning capacity to treat the file a version of your main, original image...

This would be rather simple:
1) In PSu select the raw file, open it in your editor, make the adjustments and generate the output file, save it in the original folder with the file naming convention, e.g., "whatever_name.nef" to "whatever_name_C1.jpg"
2) in PSu use "check folders for files" and the "detect versions" to keep the versions together...

Should work quite well and you can even configure PSu to have version placeholders fore the different files according to the file naming mask...

Post Reply