Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Output naming tokens for variants

The EL

Working on a new workflow for somethings and noticed something. I have an image with 2 variants (3 images total.)  Different crop ratios on each variant. 

When I try to change the output file naming to [Image Name]_[Dimensions] using the given tokens it outputs all images with the parent variants dimensions instead of each variants dimensions. 

Is there a way to get each variants dimensions to work for the [Dimensions] token? Even better if there is a way to get the crop ratio rather than the dimensions. 

 

 

 

0

Kommentare

6 Kommentare

Datum Stimmen
  • SFA

    I don't think that is possible.

    The only option I can think of would be to use an otherwise unused IPTC text field that has a token available and enter the ratio for each variant there.

    I tend to use different recipes and use the recipe names but for you purposes that would mean running 3 separate output processes.

    In some situations, especially where size of output is significant for the final output (not just the crop ratio), running separate recipes probably makes the most sense. In which case the recipe could be named for crop ration and output size intentions and then the Recipe Name token would work for the output naming.

    0
  • Permanently deleted user
    • Bearbeitet

    I can't help, but I do agree that additional, variant-based tokens would be a plus.

    Even the ability to name it as "V1", "V2", etc would be some help.

    Time to put in a request to C1 Support.

     

     

    0
  • The EL

    Ah well. A boy can dream. 

    0
  • Permanently deleted user

    Put in a request at support.captureone.com! I just did. :-)

    I can't imagine they're going to suspend work on V.21/14 to implement it, but if enough users put in a request, it may well happen in future.

     

    0
  • SFA

    I think the challenge here is that the edit information for each variant contains the vectors for the gradient but there is no form of 'name' or original base dimension from which the crop was initiated.

    So there is nothing obvious on which to base a token.

    0
  • Jan van der Meulen

    Is there found a solution for this issue?

    We have this issue on a daily base. sometimes 10 times a day.

    regards Jan

    0

Post ist für Kommentare geschlossen.