Client: Windows 7 Pro 64bit
File Server: Debian Buster/Sid with Logitech Media Server (LMS)
I know this is a question that's been answered before
, but I am am looking for some more detail on the answer.
I recently had a problem with my music server (LMS) not scanning all my music files, and after some digging it turned out that non-ASCII characters (i.e. Latin1 or Unicode) in pathnames for files like -
(that's a "smart apostrophe" in Unicode) were the cause.
The answer given in the above thread says-
From the MediaMonkey Readme.txt
b) .ini file customization
MediaMonkey saves configuration information on a per-user basis to an .ini file stored in:
C:\Documents and Settings\USERX\My Documents\My Music\MediaMonkey\MediaMonkey.ini
Advanced users can edit the MediaMonkey.ini file to change several settings. If you
plan on making such changes, it's prudent to back up your .ini file beforehand. Also
make certain to close MediaMonkey before making such changes so that it doesn't
overwrite any of the changes you've made.
ii) To eliminate illegal characters when auto creating file names from tags, there is a section
[FilenameMappings] in the .ini file, where hexadecimal values define mappings between characters.
For example E1=61 means that "/" is mapped to "a". You can modify these settings if you're
adventurous. You can find hexadecimal values of characters in the "Character map" application
included with Windows. Note that unicode is not supported in this feature.
Question- What does "unicode is not supported" actually mean? What happens if a Unicode character is encountered in a tag, and you want to use this feature?
Case in point-
You wouldn't think of Joe Walsh as a source of "international character" problems, but his album
causes problems at two levels-
- If you leave the Unicode chars in the filename (two smart quotes and the single "..." ellipsis character) it will choke LMS
- If you set MM to use only ASCII values in tags (a) You are losing information from the tag; and (b) A Linux server won't allow you to write a filename containing plain ASCII quotes.
So. somehow I want to configure around this without losing the ability to use auto-organise, which is a crucial feature for me.
I have also seen the $Replace() function referred to in auto-organise masks. I wonder if this is an option...