Request a new feature, or support for a camera/lens that you would like to use in Capture One.
It would be helpful if Capture One added a set of tokens that would return the original digital file image name and number in both the Tethered Next Capture Naming Format AND the Import Naming Format tools. The tokens should include;
Original Filename (The 8 character file name w/o extension)
Full Original Filename (The file name with the extension)
Original File Number (The 4 digit numeric portion of the DCF file name)
Currently, there is a token for the Original Filename only when importing images from a card.
In many environments, it's important to maintain consistency between images shot tethered and those imported from a card. This is especially critical when those images may be shared outside the Capture on Environment.
Provide Original Filename token in tethered capture.
Provide Original File Number token for both tethered and import.
In accordance with the Design rule for Camera File Systems (DCF) specifications, digital camera file names consist of eight characters followed by the file type designation. The eight-character file name is divided into two parts: the first four characters are alphanumeric, and the last four are numeric.
The last four numeric values are a counter that commonly defaults to a sequential count from 0000 to 9999. For this request I'm calling these numeric values the Original File Number.
When using Lightroom, there is a token that can be used with the Filename Template Editor. This token is called “Filename Number Suffix”, and it returns the last four numeric values in the original file name.
Capture One provides many tokens for naming files. The Original Filename is available, but only when importing from a card. The file naming tokens should be consistent with both imported and tethered files.
FR-I-1411
FR-I-1495
FR-I-1711
FR-I-1590
Thank You!
Current workaround
Capture One has several counter options, but they seem to focus on either the Camera count (which can’t be reset) or the Capture count (which can be reset). However, no token will return the numeric portion of the DCF file name. The currently available tokens do provide a robust file naming system, but without giving the original file name, and or number, the system becomes problematic in many collaborative environments. In some environments, there is no suitable workaround. |