Bug 16353 - Playback broken when album folder name contains non-latin character
: Playback broken when album folder name contains non-latin character
Status: RESOLVED DUPLICATE of bug 15460
Product: SB Controller
Classification: Unclassified
Component: Audio
: unspecified
: PC Windows XP
: -- major (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-09 08:42 UTC by Martin
Modified: 2010-07-12 01:33 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 2010-07-09 08:42:40 UTC
I (user: dutt) tried asking about this bug in forum thread

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

with no answer. The problem has persisted from SBS 7.4.1 all the way to 7.5.1, the last version I've tried. I generally play music (wav and mp3) by navigating and chosing albums directly from the 'my music/music folder/' tree, not through 'albums' etc.

Every album in my system has its own subfolder, named 'artist - year - album'. SB Server is instructed through advaced settings and reads tags perfectly fine out of these folder/file names.

If artist and/or album name of these folders contains non-latin characters, playback will not start when chosing any track inside the folder and pushing play (center button). Instead an empty 'current playlist' window with the simple message 'nothing' pops up.

The problem applies only to playing through SB Controller. There are no problems chosing and playing the very same albums through the SB Server web interface. SBC also shows names/titles, including non-latin characters, correctly. Playing through SBC's album view also works fine - this apply only to the music folder view.
Comment 1 Michael Herger 2010-07-12 01:33:44 UTC
Unfortunately there are quite a few outstanding issues with non-latin characters. bug 15460 comes close to this one. I'm sure there are more dupes to this...

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