PDA

View Full Version : MusicIP and accented characters in 7.5.1



treble
2010-04-28, 21:16
I am still having problems with MusicIP mixes and songs with accented/international characters in the filename. I can create a mix fine with a song with an or other characters, but the songs with international characters don't show up in the playlist, incl. the seed song if it has some.

There is something with the encoding that is different on initiating the mix and getting it back from MusicIP.

Example: creating mix, in the log it will say:
[10-04-28 20:48:23.5593] Slim::Plugin::MusicMagic::Plugin::getMix (940) Creating mix for: song using: E:\Music\All Music\Music\' A B C D E\Angelique Kidjo\1991 - Logozo\04 - W-W.mp3 as seed.
[10-04-28 20:48:23.5602] Slim::Plugin::MusicMagic::Plugin::getMix (951) Request http://localhost:8082/api/mix?song=E%3A%5CMusic%5CAll%20Music%5CMusic%5C'%20 A%20B%20C%20D%20E%5CAngelique%20Kidjo%5C1991%20-%20Logozo%5C04%20-%20W%E9-W%E9.mp3&variety=2&rejectsize=0&mixgenre=0&style=15&sizetype=tracks&size=50

But then when it tries to play it:
[10-04-28 20:52:14.2621] Slim::Formats::readTags (157) File missing: E:\Music\All Music\Music\' A B C D E\Angelique Kidjo\1991 - Logozo\04 - Wé-Wé.mp3
[10-04-28 20:52:14.2630] Slim::Schema::objectForUrl (816) Error: Null track request! Returning undef.

See how the character encoding is very different of the W-W title... The seed song actually doesn't even show up as the first song as it should, and playing the MusicIP list it will say when it plays the first song of the mix number 2 of 50.

I don't think it is a MusicIP problem, because when I paste the url of the mix request (see above line starting with [10-04-28 20:48:23.5602]) it returns a nice mix with 50 songs having international characters.

I would love to see this fixed and don't mind further troubleshooting this. Or am I the only one seeing this. I miss my 'international' songs... This started somewhere in 7.4.? and still happens in 7.5.0 and 7.5.1

My setup:
Version: 7.5.1 - r30688 @ Sat Apr 24 01:08:05 PDT 2010
Operating system: Windows XP - EN - cp1252
Platform Architecture: 586
Perl Version: 5.10.0 - MSWin32-x86-multi-thread
MySQL Version: 5.0.22-community-nt

Thanks,

slartibartfast
2010-04-29, 01:04
You certainly are not the only person seeing this. One way around it is to rename all the affected files to remove the accented characters not forgetting upside down question marks. You can leave the tags alone so track names are still displayed correctly. It is a pain to do but it works!

treble
2010-05-01, 09:09
Thanks for your reply. I guess I have to give up hope that this will ever be fixed.

So I give in... Does any one have a script to covert accented/international characters in filenames to normal ones? I am on Windows XP but have cygwin installed so have access to perl, etc...

Thanks,

Siduhe
2010-05-01, 09:38
MusicIP has worked like this for a long time - yes it's a pain and now that development of MIP has stopped, unlikely to change.

Pretty sure that EasyTag has an option to replace characters which you can use to replace the accented chars. Only semi automatic as you still need to tell it which chars to replace, but a lot easier than doing it manually!

aubuti
2010-05-01, 17:10
So I give in... Does any one have a script to covert accented/international characters in filenames to normal ones? I am on Windows XP but have cygwin installed so have access to perl, etc...
A script would be the good way to do it, but I've done this using mp3tag's "actions". mp3tag is excellent Windows freeware from www.mp3tag.de (be sure to get the one from the .de site, as there is another program with the same name that is not as good.

In mp3tag use
Convert >
Actions >
New Action >
give the action a name >
New >
Replace >
Field _FILENAME >
Original [accented character]
Replace with [unaccented character]
select Case-sensitive comparison
click OK

Repeat those last few steps for all of the relevant letters with acute accents, grave accents, umlauts, circumflexes, and yes, upside down question marks. It's a little tedious to set this up, but less tedious than doing the files one-by-one. Then highlight a file and run the action on it. Do it with just a few files at first to make sure it is doing what you expected.

When you're done with the filenames, do it for the directory names too if necessary.

treble
2010-05-03, 15:09
Thanks for the MP3Tag tips. That's a neat trick. I also found a little Perl script to get rid of all those pesky characters posted by tom permutt four years ago:

http://forums.slimdevices.com/showthread.php?t=22069

aubuti
2010-05-03, 18:18
Thanks for the link. I knew this was a perfect job for Perl, but beyond my very limited skills in that department.

treble
2010-05-12, 20:38
Unfortunately the Perl script didn't work with my cygwin installation on Windows XP. It could find the accented characters but didn't replace them with their 'equal' part, like to e.

So I converted my characters in filenames and folders from UTF to ASCII with MP3Tag using the 'action' feature. For people who want to try as well, I have attached the 'mta' file (International Character Conversion.mta) so you don't have to recode it yourself. Drop it in the folder: C:\Documents and Settings\YOUR_LOGIN_NAME\Application Data\Mp3tag\data\actions. I now know more then I ever wanted to know about character sets!

There is still some manual clicking needed since 'do with all' or something like that, doesn't really seem to work. Also, the folder above the folder with mp3 files doesn't get fixed. So if you have something like: "Music\Man\Man - 2008 - Arde El Cielo\01 - Dejame Entrar.mp3", the first Man doesn't get converted to Mana, but the one in the Album name does. You can easily find those with the Perl script using cygwin.

The result re: MusicIP? It fixed the problem!!! I can now create mixes with SqueezeCenter in which songs with accented characters appear and they even play without complaining!

So in short, if you want to use MusicIP you can not have 'international' characters in the filename or folder, but you can in the ID tags.

tamanaco
2010-05-13, 05:45
Hmmm, I did not noticed, until I saw this thread, that this accented character issue with MusicIP was back. I guess it came back with 7.5 as it was working fine for me with previous releases of SBS. My library has tons of World music and I have used accented characters in the tags, path, and files names. I'm not about to rename them as I feel that it takes away an aesthetic aspect of my library.

I have not been using the "M" in the Web UI to generate MusicIP frequently enough to notice that it was not picking up accented characters. I have been using SpiceFly SugarCube and this plugin uses MusicIP to create its dynamic playlists. As far as I can tell, SugarCube has no issues retrieving tracks from MusicIP that have accented characters. I guess there is something that SugarCube is doing to handle these MusicIP exceptions. I can use a seed track with foreign characters in its path, file name, and tag and SugarCube retrieves the next track. It even retrieves next tracks with accented characters in them. "Maybe"... just maybe... some method could be added to the MusicIP plugin or SBS so that it can retrieve the MusicIP generated tracks in a similar way that SugarCube does. Having to rename all my existing files and having to edit tracks that are automatically named "correctly" as I rip them with dBpowerAMP is not an option for me. I also want to maintain the integrity (The correct names of Artists, Albums and Tracks) in my library as I don't use it exclusively with SBS and in the future a better player/mixer might come up that has no issues with these characters.

Edit: There are also some foreign words that without the correct accent(s) have a totally different meaning or no meaning whatsoever.

treble
2010-05-13, 11:53
SqueezeCenter can create mixes with accented characters in the filename, however it won't play them since it can't find them because of the wrong character encoding (the error will show up in the log). Do yours actually play?

This character encoding has been an issue with many versions of SqueezeCenter/Slimserver. Very frustrating. I resisted 'fixing' my filenames as well, but now I gave in, and changed my library.

See also bugs I filed earlier (which probably will never be fixed since it is under the 7.4.* version):
http://bugs.slimdevices.com/show_bug.cgi?id=15486
http://bugs.slimdevices.com/show_bug.cgi?id=15701

tamanaco
2010-05-13, 13:14
SqueezeCenter can create mixes with accented characters in the filename, however it won't play them since it can't find them because of the wrong character encoding (the error will show up in the log). Do yours actually play?

This character encoding has been an issue with many versions of SqueezeCenter/Slimserver. Very frustrating. I resisted 'fixing' my filenames as well, but now I gave in, and changed my library.

See also bugs I filed earlier (which probably will never be fixed since it is under the 7.4.* version):
http://bugs.slimdevices.com/show_bug.cgi?id=15486
http://bugs.slimdevices.com/show_bug.cgi?id=15701

I my case SC creates mixes, but only with tracks that have no accented characters. If I select a track with accented characters as the seed SC will generate a mix, but the accented seed track won't be in the playlist. Also, none of the other tracks added to the playlist have accented characters. I have set the number of tracks for playlists to 25... The generated playlist are of a shorter lenght... say 20 tracks... but I get no errors in the log. But this might be because I have the logging for the MusicIP plugin to display errors only. If warnings are being generated they might not make it to the log.

With SugarCube I can use a track with accented characters as the seed and this track plus subsequent dynamically added tracks to playlist... play without a problem. This includes dynamically added tracks with accented characters in their tags, path and files names.