Suggestions: More Tokens for output, capture naming / folder
We work with a product photographer who, for their storage purpose, requires the output folder structure to be the same as the capture folder structure. Tethered, h2 with a p45+. However, the hierarchy of the capture folder ends up looking something like:
/Capture/StyleName/Color/Material/StyleName_Color_Material_####.tif
Generally, we'll manually type it into the "NEXT CAPTURE NAMING" field. Would it be difficult to add a grandparent folder, greatgrandparent folder, etc. tokens? I'm imagining it as a dropdown to the Folder Name token, similar to the dropdown for the number token.
Stretching that out even further, could we have the ability to output to a sub-subfolder named via a token and "/"?
For example:
/OUTPUT/TIFF/[capture folder's grandparent folder]/[capture folder's parent folder]/[capture folder]/[image name].tif
(where TIFF is the subfolder I've created). Right now "/" is an invalid option for output file naming, and I'd assume there's a reason why outputting a file can't create a folder structure to put it in.
Right now we're:
-Shooting to the aforementioned folder structure (which we've created manually in finder)
-Processing the files to JPG and TIFF subfolders (over lunch, over night)
-Using an AppleScript workflow to duplicate the capture folder structure
-Copying that empty folder hierarchy to both JPG and TIFF subfolders
-Manually moving the output files into their respective folders.
Thanks!
/Capture/StyleName/Color/Material/StyleName_Color_Material_####.tif
Generally, we'll manually type it into the "NEXT CAPTURE NAMING" field. Would it be difficult to add a grandparent folder, greatgrandparent folder, etc. tokens? I'm imagining it as a dropdown to the Folder Name token, similar to the dropdown for the number token.
Stretching that out even further, could we have the ability to output to a sub-subfolder named via a token and "/"?
For example:
/OUTPUT/TIFF/[capture folder's grandparent folder]/[capture folder's parent folder]/[capture folder]/[image name].tif
(where TIFF is the subfolder I've created). Right now "/" is an invalid option for output file naming, and I'd assume there's a reason why outputting a file can't create a folder structure to put it in.
Right now we're:
-Shooting to the aforementioned folder structure (which we've created manually in finder)
-Processing the files to JPG and TIFF subfolders (over lunch, over night)
-Using an AppleScript workflow to duplicate the capture folder structure
-Copying that empty folder hierarchy to both JPG and TIFF subfolders
-Manually moving the output files into their respective folders.
Thanks!
0
-
Hi....
Quote:
"Right now "/" is an invalid option for output file naming, and I'd assume there's a reason why outputting a file can't create a folder structure to put it in."
This is only true on Mac, the windows version of Capture One accepts "" in output file naming. I have also be trying to get this to work on Mac, but with out luck.
On windows I use this with success: "[Image Year (yyyy)]-[Image Month (MM)]-[Image Day (dd)]\[Image Name]"
Result: A folder named "2012-01-24" containing processed images.
If you process images with different creation dates, it will automatically create the right folders.
Hope Phase One makes the output more flexible and power full....
Aki0 -
I'm pretty sure this is possible through a applescript running in background of C1. Email me if you are still after a solution. 0
Post is closed for comments.
Comments
2 comments