Bug 4619 - Problem with Turkish songs (unicode issues?)
: Problem with Turkish songs (unicode issues?)
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Audio
: 6.5.0
: PC Debian Linux
: P2 normal (vote)
: ---
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-26 13:40 UTC by Martin Fowler
Modified: 2007-10-26 09:19 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Fowler 2006-12-26 13:40:35 UTC
The slims have been having problems playing songs from an Album of Turkish Jazz that I have. I have a mixed setup of early slims and more recent squeezeboxes. These songs crash the old boxes and have display problems on the new ones. This bug may be connected with an earlier bug 2404 which surfaced on the same songs.

Details follow

My Squeeze setup
================

My configuration: Server is Celeron P4 with 512 MB memory running Debain stable. Slimserver is 6.5.0. Players are 2 slimp3s, a squeezebox 1, and a squeezebox 2. Both slimp3 are wired (of course) the others are wireless. I stream mp3s. Slimp3s are firmware 2.3. Library size ~10K songs.  Slimserver usually sits at less than 3% of CPU and 15% of memory. Not much other load on server machine.

Details of Problem
============

If I try to play certain songs from this album I get bad things that happen. Sometimes I've seen the server crash. At other times I've seen the slimp3s go dark, but the SB2 continue playing, but with an incorrect display (not advancing the progress bar, or showing the previous song's title). I haven't tried every song on the album but a quick test showed that a song that contains a turkish letter which looks like an 'i' without a dot causes the problem, but another song on the album without this character played fine. This character was the same character that caused bug 2404.

Although I can't see the attachment on bug 2404 I'm pretty sure the song is called Sar? K?z (notice they aren't quite i's). I've confirmed this song causes me the problems I describe as does at least one other song that has this character in it. If you fancy you can get the whole album from emusic <http://www.emusic.com/album/10919/10919498.html>. If you need any more information on this, let me know.
Comment 1 KDF 2006-12-27 20:01:15 UTC
you noted 6.5.0 in the version. Have you tried the latest nightly build of 6.5.1 as instructed on the main page of bugzilla?
Comment 2 KDF 2006-12-27 20:13:55 UTC
also, please contact support@slimdevices.com in order to properly diagnose the problem as you have mentioned several symptoms that may or may not be a bug as opposed to system-dependant problems.  support can help you work out the initial steps.
Comment 3 Martin Fowler 2006-12-27 21:54:57 UTC
My apologies for doing the wrong thing here. I'll take it up with support. (For the record the server crashes on the nightly too.)
Comment 4 KDF 2006-12-31 11:58:53 UTC
not really wrong, just that it is a much better start to have it narrowed down on the exact natur of the problem, one to one rather than going through all the steps here just to confirm that this is in fact a bug. There is just so much clutter in bugzilla already and everyone using it from the development side appreciates the taking of steps to keep things more specific.
Comment 5 y360 2007-03-02 01:42:46 UTC
Yes, that's the Turkish "i" problem

See http://www.i18nguy.com/unicode/turkish-i18n.html

Somewhere in the code, a lower case "i" is expected to match an upper case "I"
which is an assumption that fails in Turkish
Comment 6 y360 2007-03-02 01:44:44 UTC
Pertains to Java but clarifies the issue further
http://java.sys-con.com/read/46241.htm
Comment 7 Chris Owens 2007-10-23 09:37:56 UTC
Is it possible you could attach a sample file which demonstrates this behavior?  We haven't been able to reproduce.
Comment 8 Blackketter Dean 2007-10-26 09:19:01 UTC
Unable to reproduce.  Martin: if you can attach a reproduceable case, please reopen the bug.