Where did subname go?

Calvin Powers

• 2021年07月22日 14:55

Ack! Just upgraded to 14.3.0.185 for windows and subname has been removed from all my process recipes and my naming presets. I even turned on advanced options and they appear to have gone away! Please tell me they've just been moved and not taken out of the product. I use these in every one of my seven recipes to help ensure file names are unique (regardless of output location) 

 

Calvin Powers 

0

• 

  Calvin Powers

  • 2021年07月22日 15:02

  Oh wait, now I get it. The entire naming scheme is now part of the recipe definition. This actually makes a lot more sense and is easier to manage. Just took me a few minutes to figure it out. 

  0
• 

  Class A

  • 2021年07月26日 13:41
  • 編集済み

  @Calvin Powers

  How do manually achieve influencing the output location on a per-export basis across all profiles?

  As far as I can see this is no longer possible.
  
  I'd like to be able to use a common root for all recipes, e.g., "C:\Exports\".
  This is supported.
  
  I'd like to be able to generate the output of different recipes to different output subfolders, e.g. "C:\Exports\...\JPEGs\" vs "C:\Exports\...\TIFFs\".
  This is also supported (via a respective token).
  
  I'd like to be able to influence the "..." part in the above paths on a per-export basis, e.g., "C:\Exports\ClientA\JPEGs\" vs "C:\Exports\ClientA\TIFFs\", by entering "ClientA" into a text field in the GUI.
  This does not seem to be supported anymore.
  
  If "ClientA" appears as a name (e.g., album name) that can be referenced via a token, then the desired outcome is still achievable (via the use of a respective token), but often I want to use different names in my output structure.
  
  Do you see any way what I want is still achievable?
  
  If not and you'd wish you could do something like the above, perhaps support my respective feature request.

  0

投稿コメントは受け付けていません。