ACTIONS that mimics a WYSIWYG to Change File Extension or File Name and Extension (2022-2023)

[wneclass2018]

1. UNIVERSAL File Extension (%_extension%) CHANGER by wneclass2018 (October 12th 2022) (Updated 12-29-2022).mta
   UNIVERSAL File Extension (%_extension%) CHANGER by wneclass2018 (October 12th 2022) (Updated 12-29-2022).mta (953 Bytes)

   Crucial Information: New field required: NEW_FILE_EXTENSION
   BRIEF Explanation: This allows you to change the file extension in a WYSIWYG, and you only have to create a new field NEW_FILE_EXTENSION or use an existing field, but make sure you replace the placeholder, %NEW_FILE_EXTENSION%, with yours. Moreover, in the 12-29-2022 update, from the field "NEW_FILE_EXTENSION", no periods will be allowed entry into the field, since one is automatically included, and if the "NEW_FILE_EXTENSION" field contains ONLY white spaces and tabs, it will revert to the original file extension "%_extension%". This action is also case sensitive, and I omitted excess spaces, since extensions, typically, don't contain spaces.

2. Change BOTH File Name (%_filename%) and File Extension (%_extension%) by wneclass2018 (December 29th 2022).mta
   Change BOTH File Name (%_filename%) and File Extension (%_extension%) by wneclass2018 (December 29th 2022).mta (1.0 KB)

   Crucial Information: TWO new fields required: NEW_FILE_EXTENSION and NEW_FILENAME
   BRIEF Explanation: See "1)" for brief explanation of "NEW_FILE_EXTENSION". Nonetheless, for the field, "NEW_FILENAME", I removed excess spaces from the beginning (i.e. "^") and the end (i.e. "$"). In addition, for both fields, NEW_FILE_EXTENSION and NEW_FILENAME, if either one or both fields contain no entries (i.e. BLANK, only white spaces and tabs, etc), the action for that empty field will fail and revert back to its original file extension and original file name, which I backed up using the placeholders "%preserve_original_filename%" and %preserve_original_extension%.

3. CONVERT File Extension (%_extension%) to Lowercase by wneclass2018 (February 20th 2023).mta
   CONVERT File Extension (%_extension%) to Lowercase by wneclass2018 (February 20th 2023).mta (759 Bytes)

   This will convert ALL uppercase file extensions to lowercase. No need to create any new fields.

══════➤ ACCESS to ACTIONS (.mta) (AppData) Folder: %AppData%\Mp3tag\data\actions or C:\Users%username%\AppData\Roaming\Mp3tag\data\actions

[ohrenkino]

@wneclass2018

ACCESS to ACTIONS (.mta) (AppData) Folder: %AppData%\Mp3tag\data\actions or C:\Users%username%\AppData\Roaming\Mp3tag\data\actions

Please note that the actions folder may appear in various locations, depending on the way MP3tag was installed, be it the standard or the portable way.
The easiest method to open the correct configuration folder would be to use the function in the File menu: Open configuration folder.

[ohrenkino]

@wneclass2018

Change BOTH File Name (%_filename%) and File Extension (%_extension%) by wneclass2018 (December 29th 2022).mta

Somehow that action does not make any difference: upper case stays upper case, mixed case stays mixed case .. Do I really have to type in the new filename and the extension and then run the action? Wouldn't it then be much easier to do that in the file explorer which saves me the effort to create fields, write them, start the action and then delete them?
And even though you claim to have a

@wneclass2018

WYSIWYG

way - it is not: if I enter e.g. mP3 as new file extension, the extension becomes lower case.
Why doesn't the action create the fields it needs when all it does is to convert to lower case only any way?
Where is the benefit that I have to create user-definded fields first, then apply the action, then delete these fields again?
While a simple "Replace with regular expression" would serve the same purpose much quicker, see

Change file extension to lowercase - Regular expression

Seems like the regular expression thread is locked Previously found some nice examples there, why was it closed? Not an overly complex one but couldn't find it so posting here in case it's useful to someone else: Had a number of uppercase file extensions and was looking to convert them all to lowercase; there doesn't seem to be such a thing as the '"file extension" field so here's my take on it: Field : _FILENAME Regular expression : \.(.*)$ Replace with : .$lower($1) Cheers,

It could still be that I have simply not grasped what this should be all about.

[LyricsLover]

@ohrenkino

It could still be that I have simply not grasped what this should be all about.

I also do not see the problem. We can change the filename and/or extension with a regular expression, as already mentioned here.

To illustrate it:

Action "Replace with regular expression" to change only the extension to lowercase:
Field : _FILENAME
Regular expression: \.(.*)$
Replace matches with: .$lower($1)

Action "Replace with regular expression" to change the filename including the extension to lowercase:
Field : _FILENAME
Regular expression: (.*)
Replace matches with: $lower($1)

Update 22.02.2023, 08.45:
As @wneclass2018 stated later in this thread, there is a problem with the above regular expressions, if the filenames include (multiple) dots. Please use the updated versions in this answer.

[wneclass2018]

@ohrenkino

way - it is not: if I enter e.g. mP3 as new file extension, the extension becomes lower case.
Why doesn't the action create the fields it needs when all it does is to convert to lower case only any way?
Where is the benefit that I have to create user-definded fields first, then apply the action, then delete these fields again?
While a simple "Replace with regular expression" would serve the same purpose much quicker, see

WYSIWYG only applies to the first 2 actions. It doesn't apply to the "CONVERT File Extension (%_extension%) to Lowercase by wneclass2018 (February 20th 2023).mta" since that .mta file was created convert uppercase extensions to lowercase.
If you truly want a WYSIWYG with no restrictions (i.e. can add spaces as a extension), then you can use this string, without quotations, "%preserve_original_filename%.$if2(%NEW_FILE_EXTENSION%,%preserve_original_extension%)". Likewise, on a different mp3tag community forum, I explained it more in detail here: Not possible to change filename w/ extension via file view - #6 by wneclass2018

[wneclass2018]

@LyricsLover

We can change the filename and/or extension with a regular expression, as already mentioned here.

Yes, you can change it using your method, but my .mta allows you to freely type the extension that you desire into the required field "NEW_FILE_EXTENSION", and once you run the action, it will change the extension. I believed that I explained it thoroughly in this post: Not possible to change filename w/ extension via file view - #5 by ptrk.mj , and the only difference is that I changed the string, from the excerpt, [#3], on the December.

[LyricsLover]

@wneclass2018

but my .mta allows you to freely type the extension that you desire into the required field "NEW_FILE_EXTENSION", and once you run the action, it will change the extension.

You can freely type every extension you desire in every thinkable combination in the above regular expression. Just use
Field : _FILENAME
Regular expression: \.(.*)$
Replace matches with: .xYZ <- type whatever you want to have as new extension

[wneclass2018]

@LyricsLover

You can freely type every extension you desire in every thinkable combination in the above regular expression. Just use
Field : _FILENAME
Regular expression: \.(.*)$
Replace matches with: .xYZ <- type whatever you want to have as new extension

True, but compared to mine, you can use a placeholder (i.e. format string, %NEW_FILE_EXTENSION%) to add different extensions, while your method, which I found a flaw, cuts texts if the filename has multiple periods, while mine doesn't do that. Likewise, I did manage to modify your regex to include multiple periods within the filename, and it's also useful when I want to change extension from mks to mka or mkv since, even though I can add it within the list of extension Mp3Tag can read, it cannot write tags into it. Nonetheless, here is a .gif(s) of mine, compared to yours, and I wonder how I can tag @ohrenkino since I replied to you, instead of him.

1A) WNEClass2018 Method 01_ Change BOTH Filename and Extension (using Filename and Extension MTA file)_ 20230221_161201
Add different entries (i.e. change to .mp4, .mkv, .mks, etc as well including filename) into the placeholder displayed, compared to "2)" below.
You can change either BOTH filename and extension or just filename or just extension, but you have to make sure that either field(s) %NEW_FILENAME% or %NEW_FILE_EXTENSION% are the same as the current %_filename% or %extension%, or the %NEW...% fields are empty.

1-B) WNEClass2018 Method 01-B_ Change ONLY Extension (using Change Filename and Extension MTA file)_ 20230221_211757
Deleted the entry in the field, NEW_FILENAME, allowing me to only change the file extension without changing the filename. Likewise, this example mimics "2)" multiple periods, and changes the file extension, as intended, properly.

2) LyricsLover's Regexp METHOD_ Changing File Extension (FAILS at MULTIPLE Periods)_ 20230221_162014
Works, but changes the extension at "Patho." instead of at "Patho.physiology", and the same applies to "Drug Treat." to "Drug Treat.ment".

3) LyricsLover's MODIFIED (by WNEClass2018) Regexp METHOD_ Changing File Extension (SUCCESS at MULTIPLE Periods)_ 20230221_162945
Regex used, without quotations, "^(.*)[.](.*)$", and replace with "$1.ext". Corrects the multiple periods issue of "2)".
Regex OPTION II (using a positive look-behind & comprehensive list of Mp3Tag's readable/non-readable extensions) (without quotations): "(?<=[.])((?:a(?:ac|[ai]f[cf]?|sf|p[el]|vi)|dsf|f(?:l[a]?c)|m(?:4[abvr]|k[avs]|ov|p[c1-4+])|o(?:f[rs]|g[ag]|pus)|spx|t(?:ak|ta|s)|w(?:[a]?v|ebm|ma)){1})$" and replace with "ext of choice" or "$lower($1)". Likewise, it also corrects the multiple periods issue of "2)".

4) WNEClass2018 Method 02_ Change ONLY Extension (using ONLY Extension MTA file)_ 20230221_164625
This .MTA will ONLY change the file extension, WITHOUT any restrictions. This is WYSIWYG, but WITHOUT safe guards, compared to the ones I uploaded. I uploaded this version, from the same link I provided above, here: UNIVERSAL File Extension CHANGER by wneclass2018 (October 12th 2022) (UNRESTRICTED ENTRY).mta

[ohrenkino]

@wneclass2018

when I want to change extension from mks to mka or mkv since, even though I can add it within the list of extension Mp3Tag can read, it cannot write tags into it.

Please have a look at the supported file formats:

Supported Audio Formats

• Advanced Audio Coding (aac)
• Apple Lossless Audio Codec (alac)
• Audio Interchange File Format (aif / aifc / aiff)
• Direct Stream Digital Audio (dsf)
• Free Lossless Audio Codec (flac)
• Matroska (mka / mkv)
• Monkey's Audio (ape)
• Mpeg Layer 3 (mp3)
• MPEG-4 (mp4 / m4a / m4b / m4v / iTunes)
• Musepack (mpc)
• Ogg Vorbis (ogg)
• IETF Opus (opus)
• OptimFROG (ofr / ofs)
• Speex (spx)
• Tom's Audio Kompressor (tak)
• True Audio (tta)
• Windows Media Audio (wma)
• WavPack (wv)
• WAV (wav)
• WebM (webm)
  to be found on

Mp3tag - the universal Tag Editor (ID3v2, MP4, OGG, FLAC, ...)

which means that tags can be written to mkv files.

[LyricsLover]

@wneclass2018

cuts texts if the filename has multiple periods

Thanks for letting me know the problem with multiple dots in filenames.
I would solve it this way:

To change only the listed extensions of selected filenames to lowercase:
Action "Replace with regular expression"
Field: _FILENAME
Regular expression: ^(.*)(\.(mp3|m4a|flac|mp4|aac))$
Replace matches with: $1$lower($2)
(All not listed extensions will be ignored - you can adjust the list as you like)

To change ALL extensions in the selected files to lowercase:
Field: _FILENAME
Regular expression: ^(.*)(\.(.*))$
Replace matches with: $1$lower($2)

You could also replace the existing extension for all selected files to a fixed new extension
like .aBC with
Replace matches with: $1.aBC

To change only the filename in all selected files to lowercase, but let the extension untouched:
Field: _FILENAME
Regular expression: ^(.*)(\.(.*))$
Replace matches with: $lower($1)$2

To change the entire filename - including the extension - for all selected files to lowercase:
Field: _FILENAME
Regular expression: (.*)
Replace matches with: $lower($1)

If I would like to rename files individually per track as you suggest with your MTA's, I would use a specialized File Rename software with all the whistle and bells.