After much (cumbersome) testing, I figured out the WDTVLive “m3u” processor doesn’t support stressed characters in file names. It will display other names, but kick those out from list.
Strangely enough, stressed characters are perfectly supported for display and cause no harm whatsoever when directly playing the file (e.g. from integrated file browser). It really just seems to affect “m3u” processing, which incidently makes it tricky to find out .
In addition, and in if that would not be enough, “m3u” files are SUPPOSED to support ANSI encoding including stressed characters.
So I think you’d call it a BUG.
I’m having “Firmware 220.127.116.11” running, and language setting is french (you bet !)
If any WD engineer read this, I know you’re trying hard freeing customers from technical complexity, but it would be cool if you’d specify things like :
charset(s) to use for “m3u” encoding ?
max path length / file name lenght in “m3u” files ?
forbidden chars ?
Hope this will be patched soon in some firmware upgrade…
Except this (happens to be VEEERY important to me) WDTVLive is such a pleasure to use… - R