From keirangtp on December 29, 2010 11:51:05

Summary: artists in library should be case insensitive

From john.maguire on December 29, 2010 13:34:33

Labels: -Type-Defect -Priority-Medium Type-Enhancement Priority-Low Component-UI

From bengunnink on December 30, 2010 18:47:28

Clementine is not the only player that is case-sensitive w.r.t. artist grouping. The obvious question raised is this: if you have albums under "Wir sind Helden" and "Wir Sind Helden", which should they appear under? The former or the latter? Either the choice is arbitrary (whatever one appears first?) or it uses a set of logic that's more trouble than it's worth.

From bryan.tongminh on December 31, 2010 03:39:30

It doesn't really matter under which they appear, as long as they appear under the same heading. So I would take the one that takes the least amount of coding.

From himynameiszacHandiamapirate on December 31, 2010 09:53:34

Of course they should show up as different artists. This program is based primarily around proper tagging. Same artist under two entries? It takes mere seconds to select the offending tracks and mass-edit their artist tag (even faster since it should autocomplete using whichever one you want). I'd be much more annoyed if it was case-insensitive, as I like to keep all my tags as neat as possible. What scenario can you think of where you absolutely need them spelled differently and grouped the same?

From dooblempub on January 06, 2011 11:28:05

Some pointers of the same issue in amarok : http://mail.kde.org/pipermail/amarok/2007-September/026028.html https://bugs.kde.org/show_bug.cgi?id=131975 https://bugs.kde.org/show_bug.cgi?id=119723 Seems that Amarok developpers made it case sensitive intentionally.

I have no opinion on it.
I think there is 2 types of users :

• Users just dropping their music anywhere in their collection, who don't even want to fix their tags (because they don't care, or they want to keep the original files (bittorent share, ...)). Maybe songs could come from read only file sources you cannot fix.
• Users managing their collection more carefully

I would be very nice to have an option for that, but I understand that it's certainly a huge development (artist/album/title grouping + move/copy to library, songs organising feature in filesystem + ....?).

We could also have a feature looking for similar artists/albums/titles, helping to identify tags needing fixes (iTunes have such feature).

From dtverder on January 14, 2011 00:52:14

Totally DISAGREE with this suggestion! The fact that it is currently case-sensitive makes it much easier to detect duplicate entries.

From keirangtp on January 14, 2011 05:31:33

Comments against are also welcome here - if more people will disagree, we'll just close this one as Won'tFix.

From keirangtp on January 19, 2011 14:53:23

Issue 367 has been merged into this issue.

From xiong.chiamiov on February 17, 2011 11:43:41

Another vote for keeping it case-insensitive. It's a problem that should be fixed by the user, not worked around by the developers - that's the path towards applications like IE6.

From keirangtp on February 17, 2011 11:51:36

Because it would be very hard to change now + Clementine as Amarok by design decision were both made case sensitive, the things will stay this way.

Status: WontFix

From xaktyc on February 17, 2011 15:56:28

Ok, let's make case-sensitive search. It's so cool!
Hard to fix case-sensitive artists? Wait... oh shi

From davidsansome on May 10, 2011 12:41:51

Issue 1873 has been merged into this issue.

From unabledispute on August 15, 2011 12:50:18

There should definitely be an option to switch between case sensitive and insensitive library display (there already is an option for "advanced layouting", why not really offer a few more "advanced" features there). This is the number one issue I have with Linux audio players. I can see the merits of case sensitive sorting, but its practical for large collections (especially if you don't want to re-tag, f.e. because you do not want to break .sfv files)

From davidsansome on February 23, 2012 02:30:40

Issue 2739 has been merged into this issue.

From davidsansome on January 02, 2013 02:50:35

Issue 3398 has been merged into this issue.

From adampchapmam on January 02, 2013 06:06:11

I don't see why it needs to be one or the other. Surely a simple checkbox to let the user choose is all that is needed?

As already discussed, there doesn't need to be any complicated logic behind it. The first one the application finds can set precedent.

Mostly, this case issue is often found when the tagging follows not consistent rules for upper or lowercase prepositions. Unfortunately, it's not really a very trivial exercise to re-tag a collection with thousands of albums in it.

From arnaucarreras on May 30, 2013 09:50:41

I think it should be case insensitive too. It's very common to have tags of the same artist with different capitalization, and the "Edit track information" option is only available sometimes, so that would definitely be a great improvement of the program (or having both case sensitive and insensitive options for the library).