Bug 269399 - Amarok doesn't display cyrillic letters in streamed metadata
Summary: Amarok doesn't display cyrillic letters in streamed metadata
Status: RESOLVED DUPLICATE of bug 212099
Alias: None
Product: amarok
Classification: Applications
Component: Playback/Streams (show other bugs)
Version: 2.4.0
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: 2.4.1
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-25 16:49 UTC by Sergei
Modified: 2011-03-29 15:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Streams with cyrillic characters displayed (39.27 KB, image/png)
2011-03-29 08:04 UTC, Myriam Schweingruber
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergei 2011-03-25 16:49:52 UTC
Version:           2.4.0 (using KDE 4.5.5) 
OS:                FreeBSD

There is a screenshot:
http://simplest-image-hosting.net/jpg-0-plasma-desktopxq1711

Latin letters are displayed with no issues, but russian characters are messed up. The first radio on the screenshot streams data in OGG format, the others - mp3. Metadata displayed correctly while playing in mplayer from console. AFAIK ogg supports only unicode tags, but it's still not displayed in amarok. I've tried couple russian radiostations.

$ locale
LANG=ru_RU.UTF-8
LC_CTYPE="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_ALL=

Reproducible: Always
Comment 1 Myriam Schweingruber 2011-03-26 10:01:22 UTC
Could you give an example of streams?
Comment 2 Sergei 2011-03-27 12:25:08 UTC
Hi Myriam Schweingruber,
Here is some examples:

The ogg stream followed by mplayer's console output:
http://music.myradio.com.ua:8000/RusRock128.ogg

Name   : RusRock128.ogg
Genre  : Misc
Website: http://savonet.sf.net
Public : yes
Cache size set to 128 KBytes
Cache fill:  0.00% (0 bytes)   

libavformat file format detected.
[ogg @ 0x8072fc010] Estimating duration from bitrate, this may be inaccurate
[lavf] stream 0: audio (vorbis), -aid 0, Примавара [Русский Рок]


The aac stream followed by mplayer's console output:
http://91.214.237.245/1019

Name   : New channel 
Genre  : Misc
Website: http://www.onlinefm.com.ua/channel19
Public : yes
Bitrate: 24kbit/s
Cache size set to 128 KBytes
Cache fill:  6.25% (8192 bytes)   
ICY Info: StreamTitle='Браво - Любовь Не Горит на Russian Rock';

And this is the mp3 stream with probably cp1251 metadata encoding, I don't really care about this one, it's just an example:
http://stream.netradio.by:8000/100/mp3/128

Name   : NETradio100%
Genre  : BELARUS
Website: http://www.netradio,by/100
Public : no
Bitrate: 128kbit/s
Cache size set to 128 KBytes
Cache fill:  6.25% (8192 bytes)   
ICY Info: StreamTitle='����� ������i&�������� ����� - ������ ���� �i��� (NETradio100% | www.netradio.by/100 | 128kbps stereo)';

All outputs are taken from UTF-8 console. All streams above were present in playlist on the screenshot.
Comment 3 Myriam Schweingruber 2011-03-29 08:04:29 UTC
Created attachment 58420 [details]
Streams with cyrillic characters displayed

The first two examples display correctly here, the last one doesn't seem to send readable information. I didn't change my locale, but it is UTF-8 anyway, so the language doesn't matter much.
Comment 4 Myriam Schweingruber 2011-03-29 08:05:13 UTC
I should add that I use Linux here, not FreeBSD.
Comment 5 Sergei 2011-03-29 08:13:22 UTC
Yes, cyrillic characters are displayed correctly on your screenshot. Could it be OSS or Xine related on my desktop? And may I ask you for your locale output?
Comment 6 Sergei 2011-03-29 09:02:33 UTC
Okay, I've changed phonon's backend from Xine to Gstreamer and Amarok refused to play streams. After installing port gstreamer-plugins-soup streamed sources plays flawlessly again with correct encoding, so I think that it's indeed Xine's issue. Thanks, Myriam!

Should I to report this issue to xine's team?
Comment 7 Myriam Schweingruber 2011-03-29 15:18:29 UTC
This is already reported, thank you. See also bug 212099

*** This bug has been marked as a duplicate of bug 212099 ***