The Presets are shared with the Process recipe feature. ( I have no idea where they are stored though).

However there are some options in the Process recipe tokens which cannot be available in the Batch Rename.

For example I have a preset for output naming that simply uses (File name section of recipe) Sub Name_File Name. (Note: The file name before output which will of course be different if attempting the rename an already output file!)

When batch renaming there is no Sub Name option so the token is not available and the Preset definition is invalid for batch renaming.

I have 5 presets defined for output file naming in the process recipe section, 2 of which are not valid for batch renaming and so are greyed out.

The main shortcoming seems to be that when in batch rename mode there is no way to see the definition of the preset (so far as I have found using Windows). If there was (or if the reason for exclusion was indicated) the logic would be easier to follow.

HTH.

I would be interested to know if this analysis matches what you discover with your preset definitions.

this is an old thread, so most of you may have figured it out. But, just in case:

I ran into a problem where I was trying to set up the capture preset naming convention to my fav methodology when I noticed that, even after re building the preset, it would still show up greyed out when I wanted to set it.

So, here is what I ended up doing:

1. Build your favorite naming convention using the tokens and save it as a user preset. Mine is named Capture Standard Naming mine is my name_[current year xxxx][current month][current day]_[current hour][current second] this was based off an old Peter Krough lecture. He recommends using other metadata when doing image searches, so the file name is just there to avoid accidentally over writing files by using date and time. 2. Save the preset3. At this point, when I go to change to that preset, all of the user naming presets are greyed out.4. Click in the "next file naming" panel in the Format field. Clear all data from the field.5. Click on the [...] and your presets should be there.

I hope that helps someone!

btw, I built another preset for importing that uses the [image time] token in place of [current year... etc]This works great for slower shooting and for ingesting from 2 different cameras synched up chronologically. However, I haven't figured out the work around for burst shooting. That may need to go to a difffernt counter system.

matt mckee wrote:this is an old thread, so most of you may have figured it out. But, just in case:

I ran into a problem where I was trying to set up the capture preset naming convention to my fav methodology when I noticed that, even after re building the preset, it would still show up greyed out when I wanted to set it.

So, here is what I ended up doing:

1. Build your favorite naming convention using the tokens and save it as a user preset. Mine is named Capture Standard Naming mine is my name_[current year xxxx][current month][current day]_[current hour][current second] this was based off an old Peter Krough lecture. He recommends using other metadata when doing image searches, so the file name is just there to avoid accidentally over writing files by using date and time. 2. Save the preset3. At this point, when I go to change to that preset, all of the user naming presets are greyed out.4. Click in the "next file naming" panel in the Format field. Clear all data from the field.5. Click on the [...] and your presets should be there.

I hope that helps someone!

btw, I built another preset for importing that uses the [image time] token in place of [current year... etc]This works great for slower shooting and for ingesting from 2 different cameras synched up chronologically. However, I haven't figured out the work around for burst shooting. That may need to go to a difffernt counter system.