treble;622999 Wrote: > No, you're by far not the only one. I just gave up because the same > issue has come up for years... I have 'fixed' all the filenames so > that there are no more foreign characters in them and all works fine > now.
Re-tagging and renaming is not an option or a "fix" for me. My FLAC library is not used exclusively with my SBS. I transcode subsets of my FLAC library to other formats for use on several mobile players, with other servers and with remote SBS players like the Web UI, Squeezeplayer Moose and SqueezeCommander. None of these have issues handling foreign characters. The "only" issue is that the MusicIP plugin on the SBS is unable to generate mixes that include tracks with foreign characters in their filesystem path. Btw, it is not an issue of not wanting to rename my library... it is an issue of convenience and correctness. I have set dBpoweramp and other tools to rip my CDs and tag my music library automatically with little or no effort on my part during the ripping or trancoding processes. These tools also create the corresponding filesystem structure (folders and filenames) with their native language spelling and characters included. I still use an old Rio Karma player and a NEX II player that do not support tags, but support foreign characters in the filenames. Handling foreign characters, at all levels, is one of the "fundamental" function of any digital music player, music server or multimedia file handling tool that I use. I will give up asking for a fix to this issues if the fix is not within the code of the Web UI, MusicIP Plugin or the CLI. But... as far far as I know, no one has been able to pin-point where things are breaking up. As I said before. There are no issues creating MusicIP mixes with tracks with foreign characters in their path, filenames or tags while using the native MusicIP interface. Futhermore, the SugarCube plugin generates dynamic mixes from within the Web UI with the assistant of MusicIP without problems. I experienced some issues with foreign characters and Moose until one of the developers looked at the issue and found that foreign characters were being double encoded (I think by the CLI). Maybe a similar issue has been affecting MusicIP... but who knows? -- tamanaco ------------------------------------------------------------------------ tamanaco's Profile: http://forums.slimdevices.com/member.php?userid=4620 View this thread: http://forums.slimdevices.com/showthread.php?t=86355 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
