Bug 1548 - Artist, Album and Genre should be case insenstive
: Artist, Album and Genre should be case insenstive
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Database
: unspecified
: All All
: P2 enhancement with 5 votes (vote)
: ---
Assigned To: Vidur Apparao
:
Depends on:
Blocks: 1549
  Show dependency treegraph
 
Reported: 2005-05-17 05:38 UTC by Jim McAtee
Modified: 2011-05-07 17:45 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2005-05-17 05:38:09 UTC
For the purpose of determining distinct artist, album and genre names, strings 
should be treated as case insenstive.  This is more intuitive from a user 
perspective and makes the cataloging of the library less sensitive to 
unintended case variations in tags.  Use the mixed case variation of these 
strings stored in the database for display purposes only.
Comment 1 Dan Sully 2005-06-02 22:27:17 UTC
Jim - I've fixed this in subversion change 3335. Artists (contributors) are now stored in a case-insensitive 
manner. This was already true for Genres & Albums.
Comment 2 Chris Owens 2008-03-11 11:28:16 UTC
This bug was marked resolved in Slimserver 6.1, which is several versions ago.  If you're still seeing this bug, please re-open it.  Thanks!
Comment 3 Brian S 2011-05-07 16:27:34 UTC
There appears to be a regression in this behavior in the 7.6 nightlies. I believe that it may have been behaving this way in 7.5.x as well.

Examples:
LCD SoundSystem and LCD Soundsystem appear as different artists
Late Of The Pier and Late of the Pier also appear as different artists

On a separate note - trailing whitespace has also been an issue with creating "unique" artists. Yes, my tags are a mess but nearly all of my other media players handle this fine. Winamp, Foobar, Amarok, etc.

I don't know why anybody would not want this to be the default behavior, but if that is the case it could always be made a configurable option. I'd re-open this tag but it seems I don't have permissions to do so.
Comment 4 Jim McAtee 2011-05-07 17:45:47 UTC
It was intentionally changed in 7.6. See the discussion in bug 10324. I don't think 7.5.x is affected.

Trailing whitespace problems would be a different (new) bug. It's mentioned in bug 16956.