When renaming files from the tags I've noticed that it ends up including characters that a that are unfriendly\Illegal when trying to import into programs. is there something I am doing wrong settings wise? Is there a way to prevent this from happening?
In your tags all characters are allowed.
But your operating system (and especially your file system) has some limitations.
You could have a look at the command $validate to replace such invalid characters.
If you show us your used format string, we can help you to apply this command.
But if only your 3rd party programs have a problem with "unfriendly" characters, you need to check what characters exactly cause a problem.
Then you could $replace specific "unfriendly" characters with other ones.
Thank you so much for the insight!
this is what I use mostly
%albumartist% - %album% - $num(%discnumber%,2) - $num(%track%,2) - %title%
%albumartist% - %album% - $num(%track%,2) - %title%
%album% - $num(%discnumber%,2) - $num(%track%,2) - %artist% - %title%
If you use these format strings to rename filenanes, illegal characters for the file system are simply dropped, i.e a question mark in the title won't appear in the filename.
You can control this to a certain extent, so that certain invalid characters in the title, album, etc. are not simply dropped but replaced with others of your choosing. This is done with the $validate() or $replace() functions.
Example:
Your format string for the filename is
%albumartist% - %album% - $num(%track%,2) - %title%
and if the tag contents contain, for example, a double quote you could use
$replace(%albumartist% - %album% - $num(%track%,2) - %title%,",')
to replace this character with a single quote.
Check out the syntax for $validate() and $replace() in the help.
However, what you mean by "unfriendly/illegal" for importing into other programs isn't clear from your explanations so far. You should explain which programs you're talking about and what "importing" means in this context.
Musicbrainz & Lidarr are the programs, and they are stored on NFS Share and are used by Linux machines as well
Which characters exactly are "unfriendly" or illegal for MusicBrainz, Lidarr or NFS?
From a quick search
You generally cannot use characters outside of the standard ASCII range (0-127) for filenames, you should avoid characters like those in the range 128-255, and reserved characters like <, >, :, ", /, \, |, ?, ''', '@', and *.
If you show us some screenshots of your situation and what exactly you want to change, we can maybe help you better.
Now please show us a screenshot from the song #1 if you press Alt + T on it.
Then we can see how the ALBUM field is filled.
Unfortunately not, no.
Your screenshot above ist from another software, but not from Mp3tag.
Please load the song #1 into Mp3tag.
Press Alt + T
Take a screenshot and post it in your answer.
As you can see the content of ALBUM in Mp3tag is
Degüello
The strange thing is now that in Mp3tag you can see your filename as
the same as in the properties of a still unknown software:
but not as in
So where exactly do you see this ü characters in Degüello?
In which software do you have renamed your ALBUM content Degüello into your current filename with Deguello?
If you rename your first track from the ZZ Top Album in Mp3tag with Convert Tag -> Filename and the Format string:
%ARTIST% - %ALBUM% - %TRACK% - %TITLE%
what do you get as result?
I manually changed the incorrect characters with "u" because just trying to clean up my collection as quickly as possible. what came out was exactly you see in the screenshot.
If the Mp3tag Convert Tag -> Filename function really writes
Deguello or Degüello
from you rexisting ALBUM content
Degüello
then I don't see how Mp3tag could automatically guess the correct values for your target file system.
The only way I see is to use the $replace scripting function and replace all "unfriendly" characters with "friendly" ones.
The Format string would be something like @poster already wrote in answer #4.
This is due to charset issues!
NFSv4 requires filenames in UTF-8 encoding, but your filenames were written by some Latin encoding, like ISO-8859-1 maybe?
Switch to SMB if possible, which has been my solution to this for ~15 years, for Linux use too!
Just do not share out the same folders/files as NFS & SMB!!
Could you also tell us the origin of each screenshot?
The right one looks like Windows while the other one looks like an old DOS program.