Dianemo S: UpdateMedia und Umlauts

[murcel]

This is an issue i had long time ago with linuxmce.
It seems not to be fixed in dianemo.

So if i have utf-8,16 or iso tagged mp3 with an Umlaut in the title or performer, than dianemo will convert it to a different unreadable character.

so how should i tag my files, to have them right in to dianemo?

(don't know, how many times i re-tagged them outside of dianemo)

Marc

[Marie.O]

See if http://svn.linuxmce.org/trac.cgi/ticket/1485 fixes your issues.

[murcel]

After making those changes, the restart of mysql brings up following error message:


120624 11:24:12 [ERROR] COLLATION 'utf8_general_ci' is not valid for CHARACTER SET 'latin1'
120624 11:24:12 [ERROR] Aborting
120624 11:24:12 [Note] mysqld: Shutdown complete

[Marie.O]

- I guess you should go back to your original my.cnf. maybe someone else has another fix. Dianemo seems to be a bit different in this regards from LinuxMCE

[murcel]

did that already.
thx anyway

[murcel]

Andrew,

can you take a look at that issue please?

Marc

[totallymaxed]

Andrew,

can you take a look at that issue please?

Marc

Well I suspect that the changes 'recommended' in that ticket have broken something... we'll look into it asap.

All the best

Andrew

[murcel]

Andrew,

the "recommdation" didn't broke anything, i removed it again and system is running as expected.
BUT, the umlaut problem was never working since i am using dianemo. Long time ago we fixed it in linuxmce.

So again:
i am tagging my mp3 - because of the hughiness - outside of dianemo.
In Germany and some other european countries we got some characters, like the german umlaut or french accents etc. If the UpdateMedia finds such a file, it is imported, but the ä ö ü is converted to some other character.

surely it is about the character set. The encoding of the mp3 tags in the files it utf-8 or utf-16.

Furthermore, sometimes after updating tags outside of dianemo (and linuxmce), when e.g. the album title was changed (from bla bla to blabla extended edition), updatemedia seems to save both of the albumtitels to the mp3 (or database), same for performer, and titel.

I know that isn't always a bug, but wanted, in case there are various performer, but in case of album titel and titel, it doesn' make sense at all for me.

[totallymaxed]

Andrew,

the "recommdation" didn't broke anything, i removed it again and system is running as expected.
BUT, the umlaut problem was never working since i am using dianemo. Long time ago we fixed it in linuxmce.

So again:
i am tagging my mp3 - because of the hughiness - outside of dianemo.
In Germany and some other european countries we got some characters, like the german umlaut or french accents etc. If the UpdateMedia finds such a file, it is imported, but the ä ö ü is converted to some other character.

surely it is about the character set. The encoding of the mp3 tags in the files it utf-8 or utf-16.

Furthermore, sometimes after updating tags outside of dianemo (and linuxmce), when e.g. the album title was changed (from bla bla to blabla extended edition), updatemedia seems to save both of the albumtitels to the mp3 (or database), same for performer, and titel.

I know that isn't always a bug, but wanted, in case there are various performer, but in case of album titel and titel, it doesn' make sense at all for me.

Well its good you could back out of the changes cleanly.

One possibility to explain why the suggested fix in 1485 did not seem to work is that you will need to restart the MySQL server (or reboot) after applying it. You could re-apply the fix and restart MySQL server.

Let me know if that fixes the issue.

All the best

Andrew

[uplink]

My idea, after reading the thread, is that LinuxMCE changed the database collations at some point, while Dianemo didn't. I get this impression from reading the conflict you get once you make those changes to my.cnf. In my opinion, you shouldn't even need to do that if the collations were right (and if that was what was really causing the problems). I'd have to play with some funny filenames to see what's going on. I've seen it before, with French é characters - I was getting "file not found" on playback because of them. But I didn't really have the time to look into it.

I'm also not totally clear as to what the problem is: do you get "file not found" or is it a display problem, where you get squares where the accented characters are?

[Marie.O]

LinuxMCE changed the collation to UTF-8 a few years ago (that sounds soo old)... Since we did do that change, we haven't seen Umlaut problems until very recently.

[murcel]

I'm also not totally clear as to what the problem is: do you get "file not found" or is it a display problem, where you get squares where the accented characters are?

Most of the times its only a mater of display. Doesn't look nice.
Secondly is, that sometimes because of that albums are broken into 2 or more "albums" e.g. "Bäst of", "B|st of " etc.

like possy said before, we did that a long time ago in linuxmce and changed the database.

[murcel]

One possibility to explain why the suggested fix in 1485 did not seem to work is that you will need to restart the MySQL server (or reboot) after applying it. You could re-apply the fix and restart MySQL server.

Andrew, of course i did a restart - or better said, i tried to. After that i got the error message posted above.
Even a reboot doesn't fixed it. mysql will not start up causing system not to work right (everything which is related to mysql)

[totallymaxed]

Andrew, of course i did a restart - or better said, i tried to. After that i got the error message posted above.
Even a reboot doesn't fixed it. mysql will not start up causing system not to work right (everything which is related to mysql

Ok understood. Well it looks like we will have to do a database wide conversation/update for UTF-8 to fix this issue. We're looking into how we approach this and will release an update when we have completed it. It will be at least several weeks away however as we already have a number of other updates scheduled or in development.

All the best

Andrew

[murcel]

Ok understood. Well it looks like we will have to do a database wide conversation/update for UTF-8 to fix this issue. We're looking into how we approach this and will release an update when we have completed it. It will be at least several weeks away however as we already have a number of other updates scheduled or in development.

I digged into it, and it seems that dianemo uses MySql 5.5 something.
Therefor the wiki instructions are not working at all.

http://wiki.linuxmce.org/index.php/Translate_the_GUI_into_another_language

If you follow this to change the database to utf8, you have to take out the "default-character-set=utf8;" in the mysqld section of my.cnf.

Then it will work.
I will change the wiki