I have noticed that lately, the command I created to change the filename to all Uppercase text and Lowercase extension is not working for all the files. It used to work perfectly a couple updates back (not sure what update number).
Could you show us the function (command) with which you rename the files?
Also, could you show us the original filename and the result that you expected and that you got?
Also, please tell us which filesystem you use.
Otherwise it is a little hard to see if there is an issue.
To me it looks ok.
The exceptions would be interesting.
It could also be that some of the files are write protected or that you are not the owner.
Or that you have entered a couple of characters to define the word borders.
Not sure what missing information you are looking for?
I use the action command to make the Filename all capitals. It shows that it did it in the Mp3Tag program, but when I go to the file folder where the files are, the file name did not change to all capital letters?
Thank you for the effort to create a video - but sorry, I cannot decipher anything that happens.
I can see that folders are opened and a file gets treated with an action, probably "Case conversion", then a message box appears telling that something has happened - just don't ask me what.
I just tried to rename a file
Action of the type "Case conversion"
Word starting after:
Filename before the conversion:
Ambient Diary.one _ 101 _ Babel _ The Return Of Babel.mp3
Filename after the conversion:
AMBIENT DIARY.ONE _ 101 _ BABEL _ THE RETURN OF BABEL,mp3
I would say that this worked as expected.
I copied the filenames from the explorer, so even that shows the files as intended.
The Drive is formatted as FAT32. Its been the same drive used for a few years and with MP3Tag for many years which used to preform the action using _FILENAME command with no issues.
As you saw in the video, some of the files in the folder did change when using the action with the _FILENAME command. I usually highlight all the tracks in the MP3Tag list and apply the action for the conversion. Just some change, and some do not change. Very weird.
Applying an action of the type "Case conversion" leads to:
BIG SEAN & METRO BOOMIN FT. KASH DOLL - SO GOOD.mp3
What about access rights? Read-only? Such things?
Does renaming on a different storage medium work?
I think the magic word here is "FAT32". Fat32 knows no access rights.
And FAT32 is case-insensitive, other than NTFS, wich is case-sensitive.
To my knowledge it is not possible to change the writing of a file on FAT32 from lower-case to upper-case or the other way round. To do so you have to change at least something else of the filename to make a change of the case happen.
When you execute an case-conversion action of FAT32-file with MP3Tag, MP3Tag shows the expected result and the conversion, because it obviously does not pay attention to the case-sensivity of the file-system.
If you then reread the files with MP3Tag it shows again in the former case.
If this is a bug of MP3Tag?
I don't know. Perhaps it should not show a wrong result of the action if in fact there were no changes possible because of a FAT32-Drive. To change this behaviour could be a bit tricky because is is only relevant for case-changes without renaming.
After the failed renaming and closing of Mp3tag, what are the contents of %APPDATA\Mp3tag\Mp3tagError.log
Are there any other programs accessing the file at the time of renaming?
You can check with Microsoft/SysInternals Process Explorer
Go to Find > Find Handle or DLL. In the Handle or DLL substring text box, type the path to the file (e.g. E:\path\to\file.mp3) and click Search. All processes which have an open handle to that file should be listed.
Before I wrote in this thread I tried it too and it did not work with MP3Tag.
Using an action format value or the converter Tag -> Filename or simply the case-conversion for the filename does not change anything if the filename stays the same inspite of case-conversion.