Different output location and name for each process recipe?
The tile says it all. I'm using Catalogs so I can pull in images from any location on my system. I'd like to set up different process recipes that have separate output locations and names.
For example, I'd like to have one output recipe that exports the image into my main LR images folder and opens it in Photoshop. I'd add a text token such as "C1 Master Edit". I'd also like to have one for color toning of PS images. In that case I'd like to have the text token be something like "C1 Color toning", and have the output file go into a "color toning" sub folder.
Right now I have to change the output location and text token each time since the process recipes seem to all use the same output fields.
Is there a work around for this, or maybe I'm just missing something. I'm still trying to get up to speed with integrating C1 into my normal workflow...
Thanks in advance 😊
On Mac OS X El Capitan, not that it matters...
For example, I'd like to have one output recipe that exports the image into my main LR images folder and opens it in Photoshop. I'd add a text token such as "C1 Master Edit". I'd also like to have one for color toning of PS images. In that case I'd like to have the text token be something like "C1 Color toning", and have the output file go into a "color toning" sub folder.
Right now I have to change the output location and text token each time since the process recipes seem to all use the same output fields.
Is there a work around for this, or maybe I'm just missing something. I'm still trying to get up to speed with integrating C1 into my normal workflow...
Thanks in advance 😊
On Mac OS X El Capitan, not that it matters...
0
-
You probably missed the File tab in your recipes : https://imagealchemist.net/capture-one-process-recipes/ 0 -
John Doe wrote:
You probably missed the File tab in your recipes : https://imagealchemist.net/capture-one-process-recipes/
Thanks! I had overlooked that. I does help with getting the images in the folder I want them in.
I still have a question of how to have different text tokens assigned to different process recipes. Is that possible at all?
Thanks!0 -
So I guess the ability to save different output name "text slugs" for each process recipe isn't supported? Anyone? 0 -
NNN636303894707373069 wrote:
So I guess the ability to save different output name "text slugs" for each process recipe isn't supported? Anyone?
If you are using free format text just type it in - between the tokens if necessary in the relevant fields. File naming, Sub-folders, or whatever.
Very simple, very flexible.
If that cannot do the job you need it to do I think you make need to provide some very specific examples so that people can begin to understand your perceived needs.
Grant0 -
NNN636303894707373069 wrote:
So I guess the ability to save different output name "text slugs" for each process recipe isn't supported? Anyone?
Check out the section about the Sub Name field in the link I provided: « Between the Root Folder and the Sub Folder fields you find the Sub Name field. The value or token you enter here will be filled in in the Output Naming tool when you use the Sub Name token in the definition. This way you can enter recipe specific information in the file name on output. »0 -
John Doe wrote:
NNN636303894707373069 wrote:
So I guess the ability to save different output name "text slugs" for each process recipe isn't supported? Anyone?
Check out the section about the Sub Name field in the link I provided: « Between the Root Folder and the Sub Folder fields you find the Sub Name field. The value or token you enter here will be filled in in the Output Naming tool when you use the Sub Name token in the definition. This way you can enter recipe specific information in the file name on output. »
Awesome, Thanks! That's exactly what I needed. Sorry I blew past that in your initial response. I didn't make the connection that there was a token for the text I entered in the Sub Name field. Very cool!
Thanks again - questions answered 😊0 -
Glad I could help! 😉 0
Post is closed for comments.
Comments
7 comments