Stacking PSD files with their original RAW File
Hey Community,
I've been an avid user of Capture One for my RAW file processing and I must say, the software does a fantastic job in terms of color and processing.
However, I've noticed a particular file management issue that is increasingly being discussed on social media. Now that Photoshop has AI and Generative Fill, I find myself editings many more RAW files in Photoshop for the final touch than I used to. Consequently, I end up with both RAW and PSD files for a single image. However, Capture One treats these PSD files as separate entities rather than stacking them with their corresponding RAW files, unlike what we've seen in Lightroom.
I would love to see a feature in Capture One that allows for more nuanced file management. Specifically, I'm looking for a way to export all 5-Star (or otherwise marked) photos in such a way that if both a RAW and a PSD file exist for an image, only the PSD is exported. To me, a retouched file is simply a new variant of the RAW file. It is the same photo, just processed differently.
My biggest issue is that when not all files have been through Photoshop, I manually have to select the PSDs and then find all the other RAW files that I also want to export but did not need Photoshopping.
Does anyone have any workarounds for this? Is this a planned feature?
Thanks so much,
Phil
-
Hi Phil,
My need is similar and I've used hierarchical keywords to provide a workaround. It's the best method I could identify in lieu of native Stack/Grouping/Derivation functionality in C1.
I start by processing RAW files. These are often cycled through third-party tools such as Nik Silver Effects, Affinity Photo, Helicon focus etc. For me, this results in TIF files which I wish to associate to the parent RAW file so that I always maintain a record of derivation. This becomes important when multiple RAW files may result in a single TIF file - e.g. a focus or exposure stack. My workflow also often creates new files for specific output types - e.g. print - and again I wish to record their parent/child derivation.
To achieve this I have a set of DAM hierarchical keywords and I tag each child or derived file such that it can always be associated to its parent of the same file name. To illustrate, a single branch of my derivation tree is: AGP-DAM | Grouping | DerivationTree | D0-Root | D1 | D1.1 | D1.1.1. This allows me to tag the parent RAW file with D0-Root and its first child with D1; Then if I derive a new file from D1 I can label it with D1.1 etc. I use DerivationTree to label the derivations but have other branches which use the same approach for ExposureStack and FocusStack. This gives me the flexibility I need to always be sure of the parent lineage of any file.
As file associations are keywords its possible to use C1 Smart folders / Search functionality to access the files required.
This may not be the best solution, I'll admit it's a bit cumbersome, but it works for me and I feel something similar could address the problem you have.
Kind Regards,
Andy
0 -
Thank you, Andy, I will definitely give it a try. It's a smart way to go about it.
Currently, my workaround involves using a specific color to mark all my export candidates. It doesn't necessarily link to the original image in a clever way, as your solution does, but it's manageably quick.
If I haven't exported any images yet, they all have the export status set to "No"; except for the ones I generated PSDs/TIFFs for. I select all images with edits and give them a color flag. I do the same for all PSDs. Then, I filter by 'Has Edits' and 'Was Exported'—these are usually the ones that also have PSDs. It's not the most elegant solution, but it's fairly effective.
0 -
Whatever works Phil! :-)
I've been trying to reply for days using my account but am suffering from the problem of a login to the forum redirecting to the main C1 website and never actually logging into the forum. It's an endless loop. Grr. Like others I have just created a second - hence it's new - account which seems to bypass the problem.
All the best,
Andy
0
投稿コメントは受け付けていません。
コメント
3件のコメント