Advanced Rename Settings

Additional advanced setting can be applied via the gear button at the upper right of the rename token editor panel . If the gear button is preceded by a grey circle, there are no advanced settings currently enabled. If the gear button is preceded by a green circle, there are current advanced settings enabled.

Note that if any setting on the advanced settings panel is enabled, the default space handling as defined in Settings - Rename - Settings - Space handling, is not performed.

The following advanced settings are available:

Replace characters invalid in Windows with underscores

The following characters will be replaced with underscores: \ * ? " < > |

Trim Leading

You can specify that spaces and/or underscores are to be removed from the start of a rename component. The trimming is done in a single pass ensuring that all characters are removed. Yate always removed leading periods as they are used to denote hidden files.

Trim Trailing

You can specify that any combination of spaces, underscores and periods are to be removed from the end of a rename component. Windows and some readers of m3u files do not like periods at the end of path components. The trimming is done in a single pass ensuring that all characters are removed.

Compress / Replace With...

You can specify that any combination of spaces and/or underscores should be compressed to a single character. The sequences can be replaced by a single space, underscore or the first character in the sequence. When set to First Character, single spaces and underscores are preserved as is. space-underscore-space would become a space and underscore-space would become an underscore.

Apply transformations for IfDup

See below.

Note that the functions are applied in the following order: Windows, Leading, Compress, Trailing.

The displayed settings can be saved as the default values for new rename templates by clicking on the Set as New Template Defaults button.

Apply transformations for IfDup

When IfDup tokens result in text being appended, the above transformations can be somewhat muddled. For example: assume the following:

• There are two mp3 files with Title fields of Test? and Test*
• The rename template is: ❨Title❩❨IfDup❩·(❨Dup #❩)
• Replace characters invalid in Windows with underscores is enabled
• Trim Trailing Underscores is enabled

The files would be renamed: Test.mp3 and Test_ (2).mp3

This is because all rename transformations are applied on the final text in a filename. In Test_ (2) the _ character is not at the end.

The Apply transformations for IfDup setting applies various transformations on all text immediately before the first IfDup token which is true. ie. the IfDup is being processed.

If the setting was enabled, the two files would be renamed to Test.mp3 and Test (2).mp3 as the transformations would be applied on Test_ before inserting the ·(❨Dup #❩) text.

The Apply transformations for IfDup setting applies the following transformations if they are enabled:

• replacements
• spaces to underscores
• encoding changes
• replace characters invalid in Windows with underscores
• all advanced period, space and underscore settings

Note that the full set of applicable rename transformations is always performed after the entire name has been constructed.

Rename Template Editor