2. Preferences

All tabs have similar format. At the bottom of the window are three buttons

2.1. General

2.1.1. Appearance

Select the Language used in the Jaikoz: about fifteen languages are currently supported.

Jaikoz provides two different Appearances. By default Jaikoz runs as you would expect on the operating system you are using. But if you use Jaikoz on more than one computer (For example an Apple Mac and a Windows PC).there is a generic Appearance which makes Jaikoz look the same on all operating systems (Windows,Linux,Mac OS X) called Cross Platform If you change this option changes will not take place until you restart Jaikoz.

Specifies the Music Player used to process from the Play Song option.

Jaikoz will try to find and use the Default Browser but this is not always possible. Browser Path allows you to specify the path of the browser that you would like to use and overrides any browser Jaikoz finds automatically.

If Save preferences automatically without prompting is selected, any changes made by you in the Preferences will automatically be saved this is the default. If you uncheck this option you will be prompted when you exit to save any unchanged preferences if you would like to

If Show Information Popups is selected then a pop-up is shown at the end of running a task summarizing what was changed, if you disable it then the information is just added to the console.

If Play sound when task completes is enabled there is a beep on task completion to alert you

2.1.2. Toolbar

Configure the toolbar with the most important actions for you, over ninety tasks can be added to the toolbar.

2.1.3. Base Folder

The list of Base Folders means that any folders containing one of these base folder as a root will have their folder path split so that the first part of the path is put into the Base Folder field and the rest into the Sub Folder field, only the Sub Folder field is replaced if later on you use Correct Sub Folder from Metadata. This list is added to automatically whenever you load a new folder in Jaikoz, but you can manually modify the list for when Jaikoz makes incorrect decision about how to split a folder path into base folder and sub folder components.

The Default Read Folder specifies the location Jaikoz will look in by default. You can either type in a folder or use the Select Folder button to open a file browser to find the folder you require. If Include Sub Folders when searching for Songs is selected Songs within the sub folders will also be loaded.

If Load from this Folder on Startup is selected when Jaikoz starts it will automatically load songs from this folder

2.1.4. Proxy Server

In some environments you many need to use a proxy server to access the Internet from Jaikoz. If so select Use Web Proxy and enter the Proxy Server and Proxy Port. Some proxies additionally require you to enter an username and password

2.1.5. Database

The Jaikoz database caches details of the songs you load into Jaikoz, and release lookups from MusicBrainz and Discogs, so it can get very large, you can specify the location of the Jaikoz database in the Database Folder field, this will take effect when you restart Jaikoz. It is not recommended to store the database in a network location because this will slowdown Jaikoz. The database cannot be used by multiple installations of Jaikoz it is only intended for use by a single installation of Jaikoz, however if you have installed a second copy of Jaikoz you could copy the database to the new installation so that it could make use of data already cached from MusicBrainz.

2.2. Table

This allows you to set how the data tables look and work

2.2.1. Columns

From here you can decide which columns are displayed, the order they are displayed in and the width of the column

To change the order of a field select it and then drag it to the new location. (A field will still be saved to a tag whether it is visible or not)

To hide a field or display a hidden field select it and then double-click on the Visible checkbox

To adjust the width of a field select , then double-click on the Width field and enter the new width, this is measured in pixels

2.2.2. Audio Columns

Sets the columns displayed in the Audio Tab

2.2.3. ID3 Columns

Sets the columns displayed in the ID3 Tabs as used by MP3 files

2.2.4. Display

Fields have different colour based on their status, you can modify the colours here. Select the 'Select Colour' button to choose the new colour

2.2.5. Synchronisation

You can change the synchronisation settings here by selecting/deselecting the relevant checkbox.

the meaning of these is explained here

2.3. Save

2.3.1. ID3Tag V1

ID3v1 is the original tagging system used with Mp3 files.

Specifies the default tag versions to save. What tags you save depends upon how you use the songs. ID3v1 is supported by most Audio applications however it is a very limited system, most applications now support ID3v2 tags in some form so there is a strong case for removing your ID3v1 tags from your file so you do not have two datasets to maintain. If your application supports ID3v2.4 you should save your tags to this version as it is the latest and greatest version, however many applications only support ID3v2.3 and ID3v2.2 so you need to take this into account when making a decision.

For ID3v1 tags you can elect to remove them, always write them or to keep if already exist.

2.3.2. ID3Tag V2

ID3v2 is the newer tagging system used with Mp3, Wav and Aif files. ID3v23 is more widely supported than ID3v22 or ID3v24.

For ID3v2 tags you can elect to always write a particular tag version or to keep the existing tag version and provide a default if the tag does not exist.

For ID3v2 you can select the text encoding to use. Most of the time the IS08859 encoding can be used but if you have values that use special characters or that are written in a language other than English one of the UTF encodings will sometimes have to be used instead. The difference is that IS08859 uses one byte per character, UTF16 uses two bytes per character so that it can store a wider range of characters - but requires more space. UTF8 uses one byte where it can, but two bytes otherwise.

The Default Text Encoding ... options are what Jaikoz will use when creating any new fields if it can, if you have also selected the Save existing fields using this encoding option then Jaikoz will use this text encoding for any existing fields if it can. When you have text that cannot be encoded in IS08859 ID3v23 will automatically use UTF16 there is no offer choice, but for ID3v24 you can choose between UTF16, UTF16BE and UTF8 with Text Encoding to use when need to write Unicode ID3v24 tags, if you have already set Default Text Encoding to use when writing ID3v24 tags to anything other than ISO8859 then this option will have no effect because UTF will be used anyway.

2.3.3. General

Pad Numbers with zero Track and Disc Nos are always padded in Jaikoz for readability but the ID3, OggVorbis and Flac formats allow you to specify if you want to store the zeroes in the files themselves

If enabled Delete empty folders on save automatically deletes folders that are now empty because the songs that were in there previously have been renamed or moved. This is powerful way of housekeeping you filesystem but may not always be desired so it is disabled by default.

With Move files marked for deletion to the deletions folder instead of actually deleting them is enabled you can specify a folder that deleted files are moved to instead of them being removed from your computer completely. It is like having a Recycle Bin or Trash Can just for Jaikoz. Specify the folder to use in the Deletion Folder field.

If you move your songs to another folder Jaikoz also move other files found in the same folder as they may be artwork , liner notes or other files linked to the songs , but you can disable this default behaviour by unchecking Move associated files

If using the Save and Move task within the Autocorrecter you need to specify where the songs should be moved to in the Move Folder field.

2.3.4. Compatibility

The compatibility tab allows you to make adjustments to your preferences so that your files work best with different players, by default this tab is configured so that your files work best with iTunes.

If the Do not unsynchronise ID3 tags option is enabled the tags will not be unsynchronised. Unsynchronisation is required when there is Metadata which could be misinterpreted as the start of the actual audio data, extra bytes are inserted so no misinterpretation will happen. But if you are using an application that does not understand unsynchronisation then the Metadata can be misinterpreted instead, this problem is most likely to occur if you have added cover art, the end result will be an image that does not display properly in some applications. Enabling this option will not usually cause problems with the audio because most players will correctly identify the start of the audio even there is Metadata which could be misinterpreted as the start of the actual audio data.

Usually Genres selected from a the Genres list are stored internally as a number but if the Save genres in an iTunes-friendly Format option is enabled than Jaikoz will ensure that when genres are saved they will store the genre as a String if it is one of the additional genres defined by Winamp to ensure that iTunes recognises it.

The Always write Mp4 Genres as text option means that for Mp4s we never used the internal ID3 genres keys, we always write the text for maximum compatibility.

Unfortunately different Music Players use different internal values to represent ratings, so a particular value that might denotes 5 stars in iTunes would only denote 2 stars in Windows Explorer. To solve this issue Jaikoz lets you specify how to interpret the values when they are loaded using the Upload and Save ratings so compatible with option, this will interpret the ratings as they are loaded and save the ratings using that format. You can also use it to convert ratings, for example if you load songs that have ratings stored in Windows Media format and you want to use them in iTunes set the option to Windows Media Player, load the files into Jaikoz, change the option to iTunes and save your changes.

To further complicate things, many players do not actually store their ratings in the songs themselves instead they store therm in their own internal database, Jaikoz provides a solution for this problem if you are using iTunes. If Jaikoz is configured to update changes to iTunes and you have changed the rating field then on save this field is used to update the rating within the iTunes database, giving you a way to modify your iTunes ratings outside of iTunes itself. If you make further changes to the files in Jaikoz but do not modify the ratings field then on save it will not overwrite the rating within iTunes (unless you do Force Save), this means you can make subsequent changes to the ratings within iTunes without being concerned that Jaikoz will replace the values. Remember that iTunes does not store it's ratings in the files themselves, and ratings stored in the iTunes database are not read by Jaikoz

2.4. MusicBrainz

Here we specify preferences to be used with MusicBrainz, a full understanding of these sections can be found here

2.5. Remote Correct

Preferences that apply to remote correct and are not specific to Musicbrainz which has its own preferences section.

2.5.1. Match

The options are explained at Match Settings

2.5.2. Discogs

The options are explained at Discogs Options

2.5.3. Correct Genres

This list genres that should be treated as genres, other values a re ignored, this list is used when getting genres from MusicBrainz and Discogs

2.5.4. Fix Songs Classical Options

Options specifically for Classical releases because the tagging requirements for Classical music are typically different then for other music genres.

2.5.4.1. Identify Classical releases

Jaikoz uses various way to identify Classical tracks, if a song does appear to be a Classical piece then the IsClassical field is set. Usually it is best to let Jaikoz to decide if a release is classical by keeping the option enabled. But some releases are difficult to assess, if all you consider none of the releases to be Classical then you can set this option to None, no releases treated as Classical to force Jaikoz to treat all the songs to none classical, clearing any values previously set for the IsClassical field

2.5.4.2. Add Composers to start of Album Title

Classical music albums often contains the composer name as a part of the album title but not always. Different composers often named their works simply such as Symphony No 1 so without the composer name it can be difficult to distinguish one album from another. With this option enabled Jaikoz will add the composer(s) surnames to the start of the album title if the composer is not in the current title to help with easier album identification.

2.5.4.3. Remove Composer from Album Artist

The Album Artist usually reflects what is written on the spine of the physical release, it usually consists of the Composer(s) of the Classical music on the release, and the principal performers and choir, orchestra or other ensembles involved, the Album Artist helps to distinguish one release from another.

But if you additionally use the Album Artist to identify only the main performers you can use this option to remove the Composer from this field, since they are not a actually a performer. Using the Album Artist instead of the Track Artist to identify performers allows you to concentrate on the main performers of the release as a whole without catching a performer that may only have performed on a single track on the release.

2.5.4.4. Shorten Song Title to the Movement

Classical Music often comprises a series of works, with each individual piece a movement within a work. When Jaikoz detects that a release contains multiple movements from a work it adds information to the Work, Movement, Movement No and Movement Total fields, often an album contains multiple works so adding this information allows songs to be organized by work rather than by album. Whenever a movement is linked to a work within MusicBrainz data then the MusicBrainz Composition and MusicBrainz Work fields are completed, but the Work and Movement fields are only used when movement is part of a multi movement work on the album. If the album is simply a compilation of extracts of different classical works and only contains single movements of works then these fields will not be added for those tracks.

The Shorten Song Title to the Movement option can be used to shorten the Title field to the movement because typically the title comprises both the work and the movement and such a title can become long and unwieldy, currently the Movement field is not well supported so most players would use the Title field for all songs and ignore the Movement field.

Options provide are:

  • No

  • Yes

  • All formats except ones recognised by iTunes

However since iTunes 12.5.3 iTunes natively supports the Work, Movement, Movement No and Movement Total fields so there is no real need to shorten the Title field if you only use the iTunes player. If you have Jaikoz configured to update iTunes it will transfer these fields to iTunes but you do need to tell iTunes to use these fields instead of Title and Album as follows:

  • Select all songs that have movement/work set

  • Select Get Info

  • Enable the Use Work and Movement check box

2.5.4.5. Copy Work to Grouping field

The original metadata format was ID3 and this defined a field called Grouping that was intended to be used to store the work for Classical music, but it also had other uses, it was defined as

The 'Content group description' frame is used if the sound belongs to a larger category of sounds/music. For example, classical music is often sorted in different musical sections (e.g. "Piano Concerto","Weather - Hurricane”"

This definition is a bit open to interpretation so over the years the field has been used by different applications in different ways, both as a work and as a way to group multiple tracks in other ways. For example in Jaikoz it can be used to store genres as a list of values because iTunes Genre can only see the first value, a problem if you want to categorize a song with multiple genres.

So Jaikoz uses a separate Work field to store the work, but depending on what audio formats and what audio players you are using you may want to copy the contents of the Work field to the Grouping field. So for example iTunes uses the Grouping field to store the work for formats that use ID3 such as MP3 and AIF, but it has a separate Work field for MP4 and M4A files, and this is the same as the Work field that Jaikoz uses for this format.

If you are using Flac/Ogg your player may expect works to be stored in the Grouping field or the Work field or have no support at all for works

So we provide the following options for this option:

  • No

  • Yes

  • MP3 and AIF (iTunes)

  • All audio formats except MP4

2.5.4.6. Opera Work Format

Classical albums create extra compilations for metadata tagging. Most usually classical albums consist of a number of works, each containing a number of movements. Sometimes a work contains another work, most notably Opera usually consists of Works, Acts and Scenes. Jaikoz works well with both Roon and MinimServer but these two applications have different incompatible ways of dealing with multi-level works such as Opera. Roon uses Movement, Section and Work but MinimServer uses Movement, Work, Overall Work, this option lets Jaikoz switch between the two alternatives.

2.5.4.7. MusicBrainz Track Artist

In Pop/Rock there is usually a single performer or band who is credited. They are often the composer of the song as well but if they are not the details of the writer are not usually so important, the artist credits on the release itself make it clear who should be credited for each track.

In Classical music, usually various performers, an orchestra or choir, a conductor and a composer are all credited. This means we potentially have a long list of people credited for each track, and we don’t have an accepted order they should be added in. Previously the Composer was used for the Artist field, but as the Composer field is better supported in most players (such as iTunes) we usually we no longer need to add the composer to both the Artist and Composer field. In fact doesn't really make sense to add the Composer to the Artist field any longer for Classical music because often the music was composed many years ago and they were not involved in the actual recording in any way.

The default for Jaikoz is to store the , Performers, Ensemble/Choir/Orchestra and Conductor in that order, but we offer different masks for different uses.

If you have a particular interest in MusicBrainz, we also offer the option to use the MusicBrainz artist fields directly. For Classical music the MusicBrainz database typically stores the Composer in their MusicBrainz Track Artist Credit field and the performers and conductor in the MusicBrainz Recording Artist Credit field but this is not always applied consistently.

2.5.4.8. Never modify these fields

If song is categorised as Classical then any fields listed here will not be modified, this is in addition to any fields already added to Never modify these fields option on the Format tab

Classical/Jazz releases are not so well served by existing media players so sometimes novel approaches are sometimes used and Jaikoz can leave any fields alone just for your Classical recordings if you wish.

2.5.4.9. Only modify these fields if empty

If song is categorised as Classical then any fields listed here will only be modified if currently empty, this is in addition to any fields already added to the Only modify these fields if empty option on the Format tab

For example Classical releases often consist of a number of works on a single album and if you have manually used work numbering rather than album numbering you can protect this by setting this by adding Disc No, Disc Total, Track No and Track Total to this list.

2.6. Local Correct

The items in this sub menu allow you adjust the settings used when you run the associated local Correct task

2.6.1. Auto Match

Here we specify preferences to be used when matching tracks when local correcting the Artist, Album, Title, Genre, Composer or Comment fields. The meaning of these sections can be found here

2.6.2. Auto Format

Here we specify preferences to be used when formatting matches performed by the local correcter for the Artist, Album, Title, Genre, Composer or Comment fields. The meaning of these sections can be found here

2.6.3. Track Correct

2.6.4. Year Correct

The only setting you can change is to specify removal of undisplayable characters but running the Correcter will also validate the Recording Time Column and if it can not fix it will set it empty

2.6.5. Artwork Correct

Settings for Local Correct of the Artwork field, the options are explained in Correct Artwork

2.6.6. Delete Duplicates

Settings for Delete Duplicates are explained in Delete Duplicates

2.7. File And Folder Correct

2.7.1. Rename File from Metadata

The Rename maskdefines how files renamed based on their metadata, you can select from any of the defined masks using the drop-down. The list of available masks is the same in the Rename mask and compilation mask and file name masks drop-downs.

The Compilation rename maskdefines how files renamed based on their metadata if they have been matched to a compilation release, you can select from any of the defined masks using the drop-down.

Some characters may not be compatible with the file names on some file-systems so the Simplify non-standard characters option replaces such characters with their simpler equivalent (i.e. é -> e, ℮ ->e and ◀ -> <) if Simplify non-standard characters is enabled. Simplification of file names can ma ke managing your files easier and provide greater compatibility with other applications.

This option is similar to the Convert to ASCII option found in some applications but ASCII only supports a subset of the Latin character set , characters sets such as Chineses, Korean and Arabic cannot be converted to ASCII so we do not try, but we can simplify file names in four main ways.

  1. We simplify Latin charset by removing diacritics such as accents ad circumflexes (é -> e)

  2. Sometimes complex characters can be represented as a combined character (NFC) or two different characters (NFD) we always convert NFD to NFC

  3. We simplify unusual representations of letters and numbers such as subscript or superscript (℮ ->e)

  4. We replace symbols and graphic characters with simpler representations ( ◀ -> <)

If Replace 'From' Character with 'To' Character is enabled you can then specify pairs of from and to words to map to.

Filename masks are used to rename your files based upon the metadata in your music files. The Filename masks drop-down list all the masks currently available for renaming songs based on their metadata. You can modify an existing mask by selecting a mask from the drop-down and selecting the Edit button. You can delete an existing mask by selecting a mask from the drop-down and selecting the Delete button. You can create a new mask by selecting the Add button, you can make a copy of an existing mask as the basis of a new mask by selecting the Clone button

2.7.2. Add/Edit Mask

A rename mask consists of a name and the actual mask itself. The name is displayed in the drop down and can be anything you like. The mask uses the full JavaScript Expression language and this makes it incredibly powerful.

The Mask Field list shows all the metadata field that can be used in the mask

You can Add a new mask, Edit an existing mask or Clone a mask, clone makes a copy of an existing mask that you can use as the basis for a new mask, you can also Delete a mask

Decide how you want the file path to look with a given set of metadata, remembering that the mask does not replace the base folder, only the sub folder and file name.

i.e. for the file C:\\Music\U2\The Joshua Tree\With or Without You.mp3 the correct split should be:

  • Base Folder : C:\Music

  • Sub Folder: U2\The Joshua Tree

  • File name: With or Without You.mp3

These split between base folder and sub folder is decided when you select a folder to fix, if Jaikoz gets it wrong it can be modified on the Basic tab before the fixing process is started.

Use the Mask Fields to get the correct metadata.

Use '/' to indicate a folder separator. You can pass these fields to JavaScript functions such as the ifnotempty function, functions take an input and return an output.

The '+' character is used to concatenate the two results, for example 'Dog' + 'Fish' gives 'DogFish'

It is tedious to repeat the same JavaScript in multiple places so you can use any of the predefined JavaScript functions from the .JavaScript User Defined Functions list.

You can also create new functions and edit existing ones.

2.7.2.1. addCompilation Function

The addCompilation function outputs a subfolder called Compilation if the song is a compilation, this provides an easy way to separate compilations from non-compilations

2.7.2.2. addGreatestHits Function

The addGreatestHits function outputs a subfolder called GreatestHits if the song is a compilation, this provides an easy way to separate greatest hits releases from non greatest hits

2.7.2.3. addHD Function

The addHD function outputs a subfolder called HD if the song is a High Definition Audio, this provides an easy way to separate HD from non-HD

2.7.2.4. ifempty Function

The ifnotempty function takes two parameters, the first is the metadata field, the second is text to put after the field if the metadata for a particular song is not empty, if it is empty then nothing is output.

This is useful to prevent outputting values intended to separate metadata when we don’t actually have the metadata for a particular song.

2.7.2.5. ifempty2 Function

The ifnotempty2 function takes three parameters, the first is the metadata field, the second is an alternative metadata field to use if the first metadata field is empty, the third is text to put after the field if the either first or second metadata fields are not empty for a particular song, if both are empty then nothing is output.

This function is useful when you have alternative sources that can be used if the primary source is empty, such as Album Artist and Artist.

2.7.2.6. ifempty3 Function

The ifnotempty3 function takes four parameters, the first is the metadata field, the second is an alternative metadata field to use if the first metadata field is empty, the third is an alternative if the second metadata field is empty, the fourth is text to put after the field if any of the metadata fields are not empty for a particular song, if all are empty then nothing is output.

2.7.2.7. ifmultidisc Function

The ifmultidisc function takes a value to output if the song belongs to a multi-disc album, if it doesn’t then nothing is output.

2.7.2.8. padnumber Function

The padnumber function takes two parameters, the first is the number, the second is the desired length. For example if the first parameter is '1' and the second parameter is 2 it will output 01, if the second parameter was three it would output 001.

2.7.2.9. substring Function

The substring function takes two parameters, the first is the text, the second is the desired length. For example if the first parameter is frederick and the second parameter is 4 it will output fred. Unlike the standard substring function provided by JavaScript this one will not error if the required length is longer than the text

2.7.2.10. Add/Edit/Clone JavaScript Function

You can Add a new function, Edit an existing function or Clone a function, clone makes a copy of an existing function that you can use as the basis for a new function, you can also Delete a function. You can modify or create a single JavaScript function using the standard JavaScript Expression syntax.

2.7.3. Correct Metadata from Filename

Here we specify settings to be used by when AutoCorrecting metadata from filename, the meaning of these sections can be found here

2.8. Manipulators

2.8.1. AutoCorrecter

Jaikoz can perform a number of corrections automatically these can be batched up into the Auto Correcter task. Here we can specify which tasks to perform and in what order. Jaikoz comes with a default list that performs all local auto corrections, some corrections are performed twice this is because the output from one task can effect the input of another task. For example we do the following order:

Correct Artist
Tags From File
Correct Artist
Correct File from Metadata

Correct Artist will find matches between Artist fields, Tag from File will populate missing Artist fields if possible from the filename it will use the values currently in the Artist column to get as accurate a match as possible. We then run Correct Artist again to take into account of any new matches, we then write the updated Artist fields to the filename with Correct Artist from Metadata

The left hand side lists all the Available tasks, the right hand side your current Auto Correcter Tasks

To add tasks to your Auto Correcter Tasks select the task from Available Tasks you want to add then use either Add to or drag them over to the AutoCorrecter tasks.

To remove tasks from your Auto Correcter Tasks selecting an item(s) and select Remove.

To sort tasks in your Auto Correcter Tasks select the item you want to move and either use the Up and Down buttons to move it in the list or simply drag and drop it.

2.8.2. Word Remover

Word Removers are used by Auto Match, they ignore words listed in a word remover when comparing field values. From here we can specify one or more word remover lists and the words they contain. The Window is split horizontally, the top half specifies the Word remover lists (a default called 'Default ' is provided) when you select a list the bottom half of the window shows all the words that will removed. Use the Add,Rename and Delete buttons in the half to create, rename or delete new word lists. use the Add,Rename and Delete in the bottom half to create, rename or delete a value from the word list

You may wish to define multiple word removers for different columns or for different dataset. For example if you are dealing with songs in a different language you could define a word remover specifically for that language

2.8.3. Word Separator

Word Separators are used by Auto Match to identify when a word ends, words are separated by the values. From here we can specify one or more Word Separator lists and the Word Separators they contain. The Window is split horizontally the top half specifies the Word Separator lists (a default called 'Default ' is provided), when you select a list the bottom half of the window shows all the characters that are used to separate words. Use the Add,Rename and Delete buttons in the half to create, rename or delete new Word Separators. use the Add,Rename and Delete in the bottom half to create, rename or delete a value from the word list, only single characters are allowed.

You may wish to define multiple Word Separators for different columns or for a different dataset. For example two Default Word Separators are provided,one is used by the File Name to tag correcter to split a filename into separate components. In this case we do not want to include the ' ' character because this would break up song titles into different words whereas we want to keep the Title as a single word for this auto correction.

2.8.4. Word Replacer

Word Replacers are used by Auto Format to replace words with another word. From here we can specify one or more word replacer lists and the words replacers they contain. The Window is split horizontally the top half specifies the Word Replacers lists (a default called 'Default ' is provided) ,when you select a list the bottom half of the window shows all the words that will be replaced and by what they will be replaced by. Use the Add,Rename and Delete buttons in the half to create, rename or delete new word replacers. Use the Add,Rename and Delete in the bottom half to create, rename or delete a valuepair from the word list, you have to specify what the word is and what you want to replace it by.

You may wish to define multiple word replacers for different columns or for a different dataset. For example if you are dealing with songs in a different language you could define a word replacer specifically for that language.

2.8.5. Punctuation Remover

Punctuation Removers are used by Auto Format to remove characters we do not want. From here we can specify one or more Punctuation Removers lists and the Punctuation Removers they contain. The Window is split horizontally the top half specifies the Punctuation Removers lists (a default called 'Default ' is provided) , when you select a list the bottom half of the window shows all the punctuation that will be removed. Use the Add,Rename and Delete buttons in the half to create, rename or delete new punctuation removers. use the Add,Rename and Delete in the bottom half to create, rename or delete by a value from the list, only single character are allowed.

You may wish to define different punctuation removers for different columns or for a different dataset. For example if you are dealing with songs in a different language you could define a punctuation remover specifically for that language.

2.8.6. Capitalizer

In title case all words are capitalized except for the words listed here in the Usually keep lowercase in Title Case list

In title and sentence case only the first letter of each word is capitalised unless it is listed in the Capitalize all letters in Title and Sentence Case list